Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reveal function #7

Open
xuanxs opened this issue Jun 1, 2023 · 5 comments
Open

Reveal function #7

xuanxs opened this issue Jun 1, 2023 · 5 comments

Comments

@xuanxs
Copy link

xuanxs commented Jun 1, 2023

Hey,jerry.

Is it possible to generate the transaction hash in advance (without broadcasting), get the inscription id and use this feature to make the reveal inscription

1.Make a raw transaction of reveal inscription and get inscription id. Reveal inscription is the current version of deploy inscription

  1. Deploy an initial inscription contain a reveal key point to the reveal inscription, and add a pre-reveal image to the deployment inscription, if the program does not detect the reveal inscription, the current image will be displayed, otherwise the display will be differentiated by the reveal inscription

  2. Mint inscriptions cannot reveal specific features, maybe replaced by numbers

  3. The NFT creator broadcasts the reveal inscription at a certain time as needed

Reference: https://bitcoin.stackexchange.com/questions/32765/how-do-i-calculate-the-txid-of-this-raw-transaction

Just an idea, not sure if it's feasible. if it is, it should be compatible with the current rules

@offerT
Copy link

offerT commented Jun 1, 2023

He should be called the respected Mr. Founder of ordiBots.

@russanto
Copy link

russanto commented Jun 3, 2023

The key problem for a reveal mechanism is to ensure that the collection creator is not aware of the reveal order, so he can not cheat on the distribution reserving the rarest for himself.

@xuanxs
Copy link
Author

xuanxs commented Jun 3, 2023

The key problem for a reveal mechanism is to ensure that the collection creator is not aware of the reveal order, so he can not cheat on the distribution reserving the rarest for himself.

In fact, the current mint way can not prevent this situation, we can only hope that the launch platform could automate the generation of inscription data(mint&deploy)

@jerryfane
Copy link
Owner

Hey,jerry.

Is it possible to generate the transaction hash in advance (without broadcasting), get the inscription id and use this feature to make the reveal inscription

1.Make a raw transaction of reveal inscription and get inscription id. Reveal inscription is the current version of deploy inscription

  1. Deploy an initial inscription contain a reveal key point to the reveal inscription, and add a pre-reveal image to the deployment inscription, if the program does not detect the reveal inscription, the current image will be displayed, otherwise the display will be differentiated by the reveal inscription
  2. Mint inscriptions cannot reveal specific features, maybe replaced by numbers
  3. The NFT creator broadcasts the reveal inscription at a certain time as needed

Reference: https://bitcoin.stackexchange.com/questions/32765/how-do-i-calculate-the-txid-of-this-raw-transaction

Just an idea, not sure if it's feasible. if it is, it should be compatible with the current rules

I think it may work, but that def need some testing.

So you'll need to:

  1. Prepare raw reveal tx of the deploy inscription and get the txid
    2 Make the attributes not human readable, we can encode and decode them with a key found in the deploy inscription for example.

That's a really interesting proposal. Allowing mints of not-revealed collection could bring much more attention to the standard. Feel free to explore this, I'll try to take a look as well on how to do step 1 and 2.

@russanto
Copy link

russanto commented Jun 3, 2023

About hiding, a simple symmetric encryption would do the job (AES256 or similar). But without a way to distribute collectibles fairly, the reveal mechanism would only provide more power to collection creators/teams. Yes, in this way they could protect themselves from any unfair behavior of the minting platform, but there is the possibility for the team to choose the collectibles to keep, as they can chose, while the buyer can not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants