v1.4.23

This release enables registration of contracts which were deployed using providers others than Irys (e.g. Turbo/arbundles).

const { contractTxId } = await warp.register(txId, 'arweave');

When registering a contract, one needs to pass contract id and set arweave as a provider. Contract metadata is then queried from Arweave GQL and indexed in the gateway database. Gateway also verifies whether contract contains contract specific tags (e.g. Contract-Src, Init-State, App-Name and App-Version).

register method is dedicated to atomic assets so contract init state should be set in a tag and not in the data field of the contract, additionally - contract should contain Content-Type tag.

This change requires warp-contracts-plugin-deploy version >= 1.0.11.

Contracts deployed using Irys are still accepted (node1 or node2 should be passed as the second parameter depending on the Irys node to which contract has been deployed).

Full Changelog: v1.4.22...v1.4.23