0xDEAFBEEF

This is a tool for computing the commit/reveal parameters based on the secret key engraved on the reverse of the sculpture.

WARNING: for security, you should only use this tool OFFLINE from an airgapped computer (right-click save the page as an HTML document to your local machine.) There is risk in entering your secret key in a web form on a machine connected to a network.

CLAIM: commit/reveal

Token ID:
Your hashmark token ID: 0 - 99.
ETH address:
The ETH address that will receive the hashmark digital token.
Secret Key:
32 byte hexidecimal code engraved on the back of your physical Hashmark.
Salt:
A password of your choice. Will be used in the Reveal step. WARNING: this password will become publicly visible after the Reveal transaction. Use a unique, one-time password for the salt, that is not used anywhere else.

Computing commit hash from provided information.. keccak256(token id, ETH address, H^11(secret key), salt)
=keccak256(, , , )
=keccak256()

Step 1: Commit

From the ETH address you specified, submit a 'commit(hash)' transaction to the HASHMARK smart contract. WARNING: do not submit your secret key as a paramter to the commit() function. Pass the following computed hash that encodes a proof of the inputs without revealing them:

    commit()

You can do this directly from Etherscan interface for the HASHMARKS smart contract. Click 'Connect to Web3' to connect your wallet, fill in the parameters for the 'commit' function and press 'write'.

Step 2: Reveal

After the commit stage, you will need to wait 48 hrs before performing the Reveal. The time buffer is required to reduce risk of a front running attack. If your reveal transaction were to get stuck in the mempool, the input parameters are publicly readable and an attacker may try to use them to perform their own commit. The 48 time buffer guards against the chance of an attacker completing a commit/reveal cycle within that time period.

From the same ETH address you specified, submit a 'reveal(tid,solution,salt)' transaction to the HASHMARK smart contract. Pass the following parameters:

  reveal(, , )

You can do this directly from Etherscan interface for the HASHMARKS smart contract. Click 'Connect to Web3' to connect your wallet, fill in the parameters for the 'reveal' function and press 'write'.

Step 3: Refresh

After a year, the token will begin to fade. You can perform a Refresh by submitting a 'refresh(tokenID, hash)' transaction to the HASHMARK smart contract. After 10 years of refreshing once a year, the hashchain will be expended and the token becomes immortal and will no longer fade. Here is a schedule of refresh transactions. Parameters are decending entries in the hashchain seeded by your secret key.

You can do this directly from Etherscan interface for the HASHMARKS smart contract. Click 'Connect to Web3' to connect your wallet, fill in the parameters for the 'refresh' function and press 'write'.