Compressed NFT Standard #126

krigga · 2023-07-28T12:21:20Z

No description provided.

yungwine · 2023-07-29T10:57:50Z

Hey @krigga! I like the idea, but I think we should make a standard NFT compressed contract with Merkle proofs instead of Merkle trees. First of all, we should use TON possibilities and TON has a convenient proof verifying technology. Secondly, it should be much cheaper.

I started such development in my fork (currently there is no Merkle Updates implementation for updates, its just an example of how the proof can be verified). So if the community like the idea I can continue development.

I think wallet developers should support exotic cells sending in wallets, because that's a good technology that can find application in many developments. So maybe its better to wait for wallets to support this feature?

For the first time we can use proxy contracts for NFT claiming: User deploys a simple proxy contract and then sends an external message with proof to it which proxy sends to the collection contract. The cost of deployment is offset by the cheapness of proof verification with tvm built-in Merkle Proof validation.

Naltox · 2023-07-29T13:59:37Z

Hey, @yungwine
Absolutely agree on your take on exotic cells.
We actually have implementation of reference contracts using exotic cells, but as you mentioned no wallet currently supports them.
We made your best to make this standard implementation-agnostic, this means that standard does not cover how exactly poofs are implemented.
So there is no reason to change the standard itself, it could be adopted now. When the wallets will support exotic cells we will just change the reference implementation of contracts without changing the standard itself

purp1le · 2023-07-31T11:21:04Z

I don't really understand why it is necessary to put all this in a separate standard. As an implementation of NFT together with merkle tree it is very good, but as a standard it does not add anything new. On ethereum they have been doing token drops with merkle tree for a long time. I think that for a new standard it is necessary to add something conceptually new, and this is not worthy of a separate standard

Naltox · 2023-08-02T11:36:09Z

Hey, @purp1le!

In the world of technology, standards play a crucial role in bringing everyone together. It's not just about showcasing the novelty of ideas; rather, the primary objective is to foster consensus among all the players in the ecosystem. These standards serve as a unifying force, ensuring that we all rally behind a common technology that benefits everybody involved.

Hiyorimi · 2023-08-02T11:45:04Z

This is so long-awaited on TON

SamDavodi · 2023-08-03T19:16:06Z

Good

Change the format of the `items` request Add an optional limit to `count` of the `items` request

ThirawatChuaiklang · 2023-09-16T14:07:17Z

Good

ThirawatChuaiklang · 2023-09-20T11:55:02Z

kuzimage444

Это как

mr-tron · 2023-10-08T12:45:49Z

text/0000-compressed-nft-standard.md

+```json
+{
+	"metadata": {
+		"owner": "UQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJKZ", // user-friendly url-safe address string


better to use raw address. it helps to avoid using not normalized address comparsion as a string

mr-tron · 2023-10-08T12:46:36Z

text/0000-compressed-nft-standard.md

+{
+	"metadata": {
+		"owner": "UQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJKZ", // user-friendly url-safe address string
+		"individual_content": "te6cckEBAQEAAgAAAEysuc0=" // base64 BoC serialized Cell


also here you use base64 url-unsafe

mr-tron · 2023-10-08T12:50:42Z

text/0000-compressed-nft-standard.md

+NFT Collection smart contract MUST implement:
+
+#### Get-methods
+1. `get_nft_api_info()` returns `(int version, cell uri)`. `version` is the version of the API that augments this contract. This standard covers API version 1, see below for description. `uri` is the API URI in `SnakeText` format **not including the version postfix**, and the final API URI must be formed as follows: `decoded-uri + '/v1'`.


wtf? what if decoded-uri is 'http://example.com/index.php?page=metadata'? author should switch urls naming scheme in project only for this feature?

mr-tron · 2023-10-08T12:54:13Z

text/0000-compressed-nft-standard.md

+
+## Augmenting API version 1
+
+Once a user has obtained and decoded the URI using the `get_api_info` get method, verified the version (this standard covers version 1 only) and added the `/v1` postfix, they can use the following methods:


get_api_info or get_nft_api_info?
or maybe it's two independent methods?

mr-tron · 2023-10-08T12:56:02Z

text/0000-compressed-nft-standard.md

+		"owner": "UQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJKZ", // user-friendly url-safe address string
+		"individual_content": "te6cckEBAQEAAgAAAEysuc0=" // base64 BoC serialized Cell
+	},
+	"index": 0


is index should always be integer? what if index is 256-bit long like in domains?

mr-tron · 2023-10-08T13:01:58Z

text/0000-compressed-nft-standard.md

+
+(`:arg` means an argument with name `arg`)
+
+##### 1. `/item/:index`


if you are writting REST style than /items/:index

mr-tron · 2023-10-08T13:08:02Z

text/0000-compressed-nft-standard.md

+```json
+{
+	"last_index": 0,
+	"address": "UQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJKZ"


same - better to use raw form for avoiding problems. for example nft collection it's 100% a smartcontract but in documentation you used non-bounce form

mr-tron · 2023-10-08T13:17:52Z

So what about indexes. like tonapi or getgems. should we index compressed collections? if yes it looks like very cheap attack to them. I can make easily collection with 100000 items, deploy it for 0.0001 TON and every index should save all items in db. but attacker even doesn't need to store all this items on his server and easily can generate it on-demand.
Looks like i attacker can stream /dev/urandom to my database.

krigga · 2023-10-24T15:57:06Z

So what about indexes. like tonapi or getgems. should we index compressed collections? if yes it looks like very cheap attack to them. I can make easily collection with 100000 items, deploy it for 0.0001 TON and every index should save all items in db. but attacker even doesn't need to store all this items on his server and easily can generate it on-demand. Looks like i attacker can stream /dev/urandom to my database.

All indexers supporting this standard should come up with their own ways of filtering out malicious compressed NFT collections (for example - whitelists/blacklists, any kind of heuristics, etc) - this standard does not concern itself with that aspect.

…d NFT standard

Godeanstreet · 2023-12-02T03:59:21Z

github-recovery-codes.txt

howardpen9 · 2023-12-03T07:14:45Z

Hey @krigga! I like the idea, but I think we should make a standard NFT compressed contract with Merkle proofs instead of Merkle trees. First of all, we should use TON possibilities and TON has a convenient proof verifying technology. Secondly, it should be much cheaper.

I started such development in my fork (currently there is no Merkle Updates implementation for updates, its just an example of how the proof can be verified). So if the community like the idea I can continue development.

I think wallet developers should support exotic cells sending in wallets, because that's a good technology that can find application in many developments. So maybe its better to wait for wallets to support this feature?

For the first time we can use proxy contracts for NFT claiming: User deploys a simple proxy contract and then sends an external message with proof to it which proxy sends to the collection contract. The cost of deployment is offset by the cheapness of proof verification with tvm built-in Merkle Proof validation.

nice

Osasv · 2023-12-23T09:20:43Z

Hey how can I update my address and details because I still haven’t gain

…

On Sun, Dec 3, 2023 at 2:15 AM Howard Peng ***@***.***> wrote: Hey @krigga <https://github.com/krigga>! I like the idea, but I think we should make a standard NFT compressed contract with Merkle proofs instead of Merkle trees. First of all, we should use TON possibilities and TON has a convenient proof verifying technology. Secondly, it should be much cheaper. I started such development in my fork <https://github.com/yungwine/compressed-nft-contract/blob/main/contracts/collection_mp.fc> (currently there is no Merkle Updates implementation for updates, its just an example of how the proof can be verified). So if the community like the idea I can continue development. I think wallet developers should support exotic cells sending in wallets, because that's a good technology that can find application in many developments. So maybe its better to wait for wallets to support this feature? For the first time we can use proxy contracts for NFT claiming: User deploys a simple proxy contract and then sends an external message with proof to it which proxy sends to the collection contract. The cost of deployment is offset by the cheapness of proof verification with tvm built-in Merkle Proof validation. nice — Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A73LUSSIRWRRMIWAGZ2SEC3YHQRHHAVCNFSM6AAAAAA23NSXUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGM4TENZZGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

agriel1313 · 2024-01-12T20:08:24Z

text/0000-compressed-nft-standard.md

@@ -108,10 +108,12 @@ Example:
 }
 ```

-##### 2. `/items/:offset/:count`


Ehsanbad · 2024-01-25T13:44:01Z

Ton Is" Power

Ehsanbad

🔥

tvorogme · 2024-01-28T10:45:38Z

All indexers supporting this standard should come up with their own ways of filtering out malicious compressed NFT collections

This means that this is not a standard, but a set of guidelines or an example, which in fact will be supported by tonapi&getgems only, because it has no transparent indexing method for new services.

Since the current solution involves paying for indexing to specific services - this is very bad.

If a new wallet enters the ecosystem, it wants to show all the NFTs of a user, but it won't show these, because no collection will carry money to a specific wallet, but there will be disgruntled users who will argue why tonkeeper shows everything and your service don't.

And this works for any new service that would want to support such a thing. When you have atomic payment choices to support a "STANDARD". - it's not good for the ecosystem.

RurikRomanov

👍🏼

Godeanstreet · 2024-05-30T15:10:51Z

🙌

dev4pear · 2024-06-24T14:23:52Z

cool project!

Compressed NFT Standard

91bd43e

Update Compressed NFT Standard

d39563e

Change the format of the `items` request Add an optional limit to `count` of the `items` request

ThirawatChuaiklang approved these changes Sep 20, 2023

View reviewed changes

kuzimage444 reviewed Sep 20, 2023

View reviewed changes

ThirawatChuaiklang approved these changes Sep 23, 2023

View reviewed changes

mr-tron reviewed Oct 8, 2023

View reviewed changes

fix: address and number formats, API URI procedure, typo in compresse…

6fe57a1

…d NFT standard

Mas7erm1nd approved these changes Nov 3, 2023

View reviewed changes

This comment was marked as spam.

Sign in to view

kuzimage444 approved these changes Nov 27, 2023

View reviewed changes

agriel1313 reviewed Jan 12, 2024

View reviewed changes

text/0000-compressed-nft-standard.md Outdated

@@ -108,10 +108,12 @@ Example:

}

```

##### 2. `/items/:offset/:count`

Copy link

agriel1313 Jan 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ehsanbad approved these changes Jan 27, 2024

View reviewed changes

RurikRomanov suggested changes May 15, 2024

View reviewed changes

Saberian1992 approved these changes Jun 6, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Compressed NFT Standard #126

Compressed NFT Standard #126

krigga commented Jul 28, 2023

yungwine commented Jul 29, 2023

Naltox commented Jul 29, 2023

purp1le commented Jul 31, 2023

Naltox commented Aug 2, 2023

Hiyorimi commented Aug 2, 2023

SamDavodi commented Aug 3, 2023

ThirawatChuaiklang commented Sep 16, 2023

ThirawatChuaiklang commented Sep 20, 2023

kuzimage444 left a comment

mr-tron Oct 8, 2023

mr-tron Oct 8, 2023

mr-tron Oct 8, 2023

mr-tron Oct 8, 2023

mr-tron Oct 8, 2023

mr-tron Oct 8, 2023

mr-tron Oct 8, 2023

mr-tron commented Oct 8, 2023

krigga commented Oct 24, 2023

This comment was marked as spam.

This comment was marked as spam.

Godeanstreet commented Dec 2, 2023

howardpen9 commented Dec 3, 2023

Osasv commented Dec 23, 2023 via email

agriel1313 Jan 12, 2024

Ehsanbad commented Jan 25, 2024

Ehsanbad left a comment

tvorogme commented Jan 28, 2024 •

edited

Loading

RurikRomanov left a comment

Godeanstreet commented May 30, 2024

dev4pear commented Jun 24, 2024


		## Augmenting API version 1

		Once a user has obtained and decoded the URI using the `get_api_info` get method, verified the version (this standard covers version 1 only) and added the `/v1` postfix, they can use the following methods:


		(`:arg` means an argument with name `arg`)

		##### 1. `/item/:index`

Compressed NFT Standard #126

Are you sure you want to change the base?

Compressed NFT Standard #126

Conversation

krigga commented Jul 28, 2023

yungwine commented Jul 29, 2023

Naltox commented Jul 29, 2023

purp1le commented Jul 31, 2023

Naltox commented Aug 2, 2023

Hiyorimi commented Aug 2, 2023

SamDavodi commented Aug 3, 2023

ThirawatChuaiklang commented Sep 16, 2023

ThirawatChuaiklang commented Sep 20, 2023

kuzimage444 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mr-tron commented Oct 8, 2023

krigga commented Oct 24, 2023

This comment was marked as spam.

This comment was marked as spam.

Godeanstreet commented Dec 2, 2023

howardpen9 commented Dec 3, 2023

Osasv commented Dec 23, 2023 via email

Choose a reason for hiding this comment

Ehsanbad commented Jan 25, 2024

Ehsanbad left a comment

Choose a reason for hiding this comment

tvorogme commented Jan 28, 2024 • edited Loading

RurikRomanov left a comment

Choose a reason for hiding this comment

Godeanstreet commented May 30, 2024

dev4pear commented Jun 24, 2024

tvorogme commented Jan 28, 2024 •

edited

Loading