Skip to content

Latest commit

 

History

History
697 lines (385 loc) · 47.9 KB

CHANGELOG.md

File metadata and controls

697 lines (385 loc) · 47.9 KB

@thirdweb-dev/sdk

3.6.9

Patch Changes

3.6.8

Patch Changes

3.6.7

Patch Changes

3.6.6

Patch Changes

3.6.5

Patch Changes

  • #440 efc56fa Thanks @jnsdls! - [EVM] - providers are now re-used if the constructor options are identical leading to better batching, also introduced an additional max batch size param (250 by default)

3.6.4

Patch Changes

3.6.3

Patch Changes

3.6.2

Patch Changes

3.6.1

Patch Changes

3.6.0

Minor Changes

Patch Changes

  • #382 0ed77d2 Thanks @jnsdls! - Add constructorParams to ExtraPublishMetadataSchemaInput schema to support better deploys from releases.

  • #385 04a47e8 Thanks @adam-maj! - Add retroactive royalty and creator setting

3.5.2

Patch Changes

3.5.1

Patch Changes

3.5.0

Minor Changes

  • #329 5200d5d Thanks @adam-maj! - ### Breaking changes:

    1. claim conditions had some changes to support the new drop contracts:
    • maxClaimablePerTransaction is now named maxClaimablePerWallet
    • maxQuantity is now named maxClaimable
    1. signature minting now requires a to address to be set for security purposees

    Main Changes:

    • Support for new optimized Drop contracts
    • Support for new claim conditions with overrides
    • Don't allow zero address recipient on signature minting

Patch Changes

3.4.5

Patch Changes

3.4.4

3.4.3

Patch Changes

3.4.2

Patch Changes

3.4.1

Patch Changes

3.4.0

Patch Changes

3.3.1

Patch Changes

3.3.0

Minor Changes

  • #315 89ff921 Thanks @furqanrydhan! - fixing vite, multihash moved to non lazy load + cbor-x instead of cbor-web

  • #321 a57b4f0 Thanks @joaquim-verges! - [SDK] Implement sharded merkle trees for lightweight allowlist checks

    Behavior change

    We've made allowlists much more performant using sharded merkle trees. This allows us to process large allowlists (1M+) efficiently.

    To support those large allowlists, fetching claim conditions does not fetch the allowlist data by default anymore. Instead, you can pass an options object to additionally fetch the allowlist data along with the rest of the claim conditions data.

    This affects ClaimConditions.getActive() and ClaimConditions.getAll()

    Examples:

    const activeClaimCondition =
  await contract.erc721.claimConditions.getActive();
// `activeClaimCondition.snapshot` is undefined
const activeclaimConditionWithtAllowList =
  await contract.erc721.claimConditions.getActive({
    withAllowList: true,
  });
// `activeClaimCondition.snapshot` returns the allowlist data

Patch Changes

3.2.6

Patch Changes

3.2.5

Patch Changes

3.2.4

3.2.3

3.2.2

Patch Changes

3.2.1

3.2.0

Minor Changes

  • #247 caf9795 Thanks @furqanrydhan! - AppURI detection now enabled

  • #238 6647f70 Thanks @joaquim-verges! - Unify NFT return types for EVM and Solana

    NFT Types are now consistent accross EVM (both ERC721 and ERC1155) and Solana

    This is a transparent upgrade, except for one type change for ERC1155 NFTs

    • nft.id is now of type string instead of BigNumber
    • edition.supply is now of type number instead of BigNumber

    This should make it much easer to deal with in applications, instead of having to manipulate BigNumber objects.

    Most people convert BigNumber to strings, which is compatible with this upgrade.

Patch Changes

3.1.2

Patch Changes

3.1.1

Patch Changes

3.1.0

Minor Changes

Patch Changes

3.0.8

Patch Changes

3.0.7

Patch Changes

3.0.6

Patch Changes

3.0.5

Patch Changes

3.0.4

Patch Changes

3.0.3

Patch Changes

3.0.2

Patch Changes

3.0.1

Patch Changes

3.0.0

Major Changes

  • #19 82627ea Thanks @joaquim-verges! - 3.0.0 update

    MAJOR VERSION CHANGE

    • 85% reduction in package size!
    • Custom contracts are now first class citizens

    Full changelog

    Breaking changes:

    1. Getting contracts is now async. This allows dynamically importing contracts and reduces the weight of the SDK significantly.

    before:

    const token = sdk.getToken(...)
const nftDrop = sdk.getNFTDrop(...)

    after:

    const token = await sdk.getToken(...)
const nftDrop = await sdk.getNFTDrop(...)
    1. New Extension API for custom contracts

    When working with custom contracts using await sdk.getContract(...), we now expose all the convenient high level APIs for each ERC standard top level. Calling a function that is not supported in your contract will give you an error with instructions on how to unlock that functionality.

    before:

    const contract = await sdk.getContract(...)
// ERC721 contracts
const contract.nft?.drop?.claim?.to(...)
const contract.nft?.drop?.claim?.conditions.set(...)
// ERC1155 contracts
const contract.edition?.mint?.to(...)
// ERC20 contracts
const contract.token?.burn.tokens(...)

    after:

    const contract = await sdk.getContract(...)
// ERC721 contracts
const contract.erc721.claimTo(...)
const contract.erc721.claimConditions.set(...)
// ERC1155 contracts
const contract.erc1155.mintTo(...)
// ERC20 contracts
const contract.erc20.burn(...)

Patch Changes

2.4.9

Patch Changes

2.4.8

Patch Changes

2.4.7

Patch Changes

2.4.6

Patch Changes

2.4.5

Patch Changes

2.4.4

Patch Changes

2.4.3

Patch Changes

2.4.2

Patch Changes

2.4.1

Patch Changes

2.4.0

Minor Changes

  • 3abe26c: initialze monorepo packages

Patch Changes

2.3.43

Patch Changes

  • d4abb09: Add support for Binance chains (BSC)
  • 274afb5: make input/output versions of the release metadata schemas
  • 86e3b58: use storage helpers from @thirdweb-dev/storage
  • 0c78b16: Fix listening to a single contract event
  • Updated dependencies [86e3b58]