Late Transaction Refunds & Multisig Verifier GUI

The æternity team is pleased to give you a quick update on refunds and contributions from multisig wallets.

We have managed to push forward two tasks related to the token distribution process:

Late Phase 1 and Phase 2 transactions

Campaign contributions from multisig wallets

Late Transactions

We’ve updated the script that generates a .CSV file of all contributions. You can find it on our GitHub. We’ve also added the ability to export late transactions (TXs) and multisig transactions (transactions that were made from BTC multisig addresses). We define late transactions as

Transactions that are received after the end of Phase 1 and before the start of Phase 2.

Transactions received later than 6 hours after Phase 2 cap was reached.

The script can be run locally and is available on our GitHub repository for testing. We’ll soon refund late transactions to the original sender’s address.

We have included all “spam TXs” with very little or no value attached, most of them were sent late for Phase 2. We define “spam TXs” as any transaction with value equal or below 0.05 CHF.

The CSV consists of all transactions late for Phase 1 and Phase 2, but not early transactions. (Those were mostly from the pre-published test addresses and were included in the token release).

Since this CSV does not filter late spam TXs, it is possible that the checksum of the TXs will change over time as more spam transactions are included.

A How-to has been added to the Readme file:

To generate a list of all transactions that are late (either after Phase 1 or after Phase 2 Cap Reached +6 Hours), use:

npm run csv-late

æternity Multisig Verifier GUI

We have also developed a tool to verify that you are the rightful owner of a contributor’s multisig transaction. This is necessary because our primary tool for translating does not work with multisig contribution addresses. We’ve added a way to generate a CSV file for all affected users here:

Multisig Transactions

To generate a list of all transactions that were made from BTC multisig addresses, use:

npm run csv-multisig

If you find you are an affected user (usually your wallet address starts with a “3”), you will need to use our Multisig Verifier Tool (MVT) in order to prove you are the rightful owner of a certain multisig wallet. You can do this by following these steps:

Go to the MVT address

Enter your contribution transaction hash

Enter your ETH address where you want your tokens to appear

Provide your signature of the ETH address using one of the multisig keys contained in the transaction

This tool does not require you to enter any secret information. All the signing happens inside your wallet. Only public information is entered into this form. At the end of the process, once you are verified, you will get a payload you can share with us. Please don’t share any private information with us.

Special note for Green Address users:

While supporting our first users, we’ve noticed a special behavior with Green Address wallets. We are pleased to report we were able to recover the Green Address key and sign the transaction. If you are using a Green Address wallet, please try this:

1. Go to https://iancoleman.github.io/bip39/ -> enter mnemonic -> hit BIP32 -> custom derivation path -> m/1

2. Use the MVT -> enter your contribution TX hash -> 2 addresses are shown

3. In the BIP39 tool -> search for a match with one of those addresses (usually it’s the first one)

4. Go to https://reinproject.org/static/bitcoin-signature-tool/index.html -> enter the private key found in step 3 and sign your ETH address

5. In the MVT -> enter your ETH address and the signature

We have also created a closed support channel on Slack. Please feel free to get in touch with [email protected] if you need support or would like to join our Slack.

Thank you!

Interested in æternity? Get in touch:

GitHub | Reddit | Telegram | Twitter | Facebook | Mail