EmelyanenkoK

@KarabutinAlex Standard does not cover logic of `get_nft_address_by_index`. In the case which you mentioned, obvious solution will be to store code of both nft versions as well as index `threshold`...

Standard update: * mandatory field `prev_owner` was added to OwnershipAssigned notification, thanks @KarabutinAlex * mandatory field `prev_editor` was added to EditorshipAssigned notification * Information about standard extensions **NFTBouncable** and **NFTUpgradable**...

> This version of the bridge has been improved - see comment below # Summary Bridge allows to transfer in decentralized way TON Coins between TON Network and Ethereum Network....

It is good idea indeed. Currently it is not that easy to install all prerequisites to compile and run Hello world smart-contract. However it will change later this month and...

@NoelJacob Considering cases when user need to be able to : - transfer NFT to himself (during rotation of wallets) - send NFT gift to the other user - use...

> Is royalty required both in smart contract and as seller_basis_fee in metadata ? I believe it is better to store royalty info in one place to avoid conflicts.

Probably it is a good idea to add additional opcodes: - GLOBALID (can be added to c7), this will allow to implement cross-chain replay protection - SETBOUNCEONACTIONPHASEFAIL - set/unset transaction...

@tvorogme I see three approaches. First one is the same as with `image` and `image_url`, when under `onchain` tag you have ability to either store object onchain, or store only...

[NoelJacob](https://github.com/NoelJacob) suggested to use combination of offchain content and onchain authenticated code (hash of the content). Probably it is candidate for `AuthenticatedOffchain` tag

@purp1le 1) `response_destination` is an arbitrary address which will receive excesses of TONs sent with message 2) why wallet-per-user, not ERC-20 (one big data-table), was chosen: check section "Why not...