-
38f0751: upgrade the generated contracts to rollups-contracts 3.0.0-alpha.9
- deployment addresses changed for every contract on every chain
ERCis now spelledErcin contract names since 3.0.0-alpha.7, so the generated ABI, address and hook identifiers follow:ISafeERC20TransferbecomesISafeErc20Transfer, and the portal deposit functions becomedepositErc20Tokens,depositErc721Token,depositSingleErc1155TokenanddepositBatchErc1155Token(erc20PortalAbiand friends keep their names)- the
DataAvailabilitylibrary was removed from rollups-contracts in 3.0.0-alpha.7, so its ABI is no longer generated;@cartesi/clientkeeps decoding the node'sdata_availabilityfield against a local copy of it, leaving theApplication.dataAvailabilityshape unchanged - the release artifacts are restricted to the contracts clients are expected to use, so
@cartesi/clientand@cartesi/reactno longer curate a list of contracts to generate and now cover the whole set:RefundOutputBuilder, deployed as a core contract, and the devnetTestFungibleToken,TestNonFungibleToken,TestMultiTokenandTestUsdctokens join the previously generated contracts - addresses now cover the local devnet (chain 31337) too, so the devnet-only contracts — the test tokens and
TestUsdWithdrawalOutputBuilder— carry an address, and the core contracts keep their single collapsed address, since the devnet deploys them at the same addresses as the livenets
- b4de9f1: bump dependencies
- f7c9d3b: first release of the codec package, with isomorphic utility functions to decode (and encode, for testing) data compliant with the rollups contracts
InputsandOutputsinterfaces, and portal deposit payloads packed-encoded by theInputEncodinglibrary
- cc25b1a: Support byte arrays alongside hex strings in all codec functions. Decode functions (
decodeInput,decodeOutput,decodeDepositand the portal deposit decoders) now also accept aUint8Array(including subclasses like the Node.jsBuffer), returning variable-size byte fields (payload,execLayerData,baseLayerData) as zero-copy subarrays of the input — no hex conversion or copying. Encode functions take an optionaltoparameter ("hex", the default, or"bytes") selecting the representation of the encoded data, and accept their byte fields in either representation. Hex in, hex out behavior is unchanged.