Topic: How to make a crypto-testament? (Read 355 times)

This is one of those ideas which turns that lamp light on in my brain 

Two other solutions to this problem using the service "Chronos - Ethereum Alarm Clock DApp".
Manual:
https://lw.0xbt.net/
Gif image

There are new ideas?

Of course, we can make a project.
We have already done some small projects using a blockchain ...?
https://bitcointalksearch.org/topic/decentralized-token-4341911
But the blockchain is not interesting to anyone.
Everyone is interested in bounty. 
And the fact that our token has the main function of signing a transaction was
liked and discussed only by the community of Indonesia.

Going to read up with this.
Very interested. Think this is something we all should be doing.

Interesting project!
I believe a crypto testament is really needed. But what with the funds that are not on Ethereum?

Your title is crypto testament, but what you are creating is an Ethereum testament.

How to store all those password or passphrases safely for someone when something happens with you?
Will they understand all this?

Is there a project who is handling this?

Thank you for the explanation, this was very interesting indeed 

1. Alice sends Bob an address with a password for decryption, to which secret information has been sent.
Alice tells Bob that he should use this information after 1 year (this is an example).
But Bob can use this information earlier and Alice will not know about it.
2. Alice sends Bob an address with a password for decryption, to which secret information has been sent.
Alice tells Bob that he should use this information after 1 year (this is an example).
But to get this information, Bob must create 3-5-7 or 10 contracts.
At this address, Alice sets up @ traffic on Etherscan.
But Bob decided to use this information before. And he began to create contracts.
After the first contract created by Bob, Alice receives an @ Etherscan alert.
Alice sends coins to another address or changes the information.
Alice scolds Bob.  




Password - to be or not to be

I did something on smart contracts as well but i don't know that much, however i think i get what you wrote now.

As far as i understood ( bear with me ) if you create for example 6 smart contracts with a fresh address on the test net and then 6 on the main ethereum net, they will have the same addresses.

(I had no idea about this, this indeed open up interesting use cases )

Then when you are satisfied with a particular contract address, created on the test net, you send to it a token containing the coded info from the main net, the testament.

Could you please clarify these:

Wouldn't be the same if we send the token with the info directly to an ethereum address, instead of using a contract addresses?

Isn't the data in here https://rinkeby.etherscan.io/tx/0x1067fc99b589df974b75dc962cd1fa849e8327c0569d1a6b1584f8b75e9c0efe
sent to the smart contract that doesn't exist yet accessible even if we don't create for real that smart contract address? What is exactly the purpose of creating that particular smart contract address receiving the data?

As we see, there are no other ideas and solutions yet.

This is a very interesting problem, im going to read a bit more in detail about it when i'm more fresh in my mind 

At the moment i'm not understanding why we cannot do this just with one smart contract, in which we store the the crypted data.

In the russian-language branch, the 'kzv' user suggested solving this problem
in the bitcoin blockchain:
https://bitcointalk.org/index.php?topic=4997960.4997960.msg47146280#msg47146280

Continued...

Creating a final contract - 
https://rinkeby.etherscan.io/tx/0xc98bafdfb0990fa3b1ed8a75f7359a977472bddf085b5213d4244fd1b914c4ba
Go to the address of the contract - 
https://rinkeby.etherscan.io/address/0xc112b24c9a03ed200a741e875d4f24035a6f85fd
Go to - Erc Token Txns and see the transaction to this address, held a few days ago.
Go to the transaction 
https://rinkeby.etherscan.io/tx/0x1067fc99b589df974b75dc962cd1fa849e8327c0569d1a6b1584f8b75e9c0efe
click "Decode Input Data" 
we copy a line, insert into the WebCrypt service and we decode.
Password - "to be or not to be"
And we see the result.

Thus, we were able to see the message sent a few days ago.

How to make a crypto-testament?

This question was voiced in the Russian part of this forum:
https://bitcointalksearch.org/topic/--4997960
I tried to give an answer.
What other options can be offered?
Is it possible to solve this problem using bitcoin blockchain?


Solution of the problem using the Ethereum blockchain:

After reading this question, I began to think how to send a message in
future. I set Google search: Unconfirmed transactions ethereum, bitcoin.
And began to read. After a while I found an interesting link:
https://ethereum.stackexchange.com/a/761/3032  
( I highly recommend reading to make my actions clear. )
After thinking over what I read, I got the idea for a solution that
I and implemented.
I used the test network Ropsten and Rinkeby.

1. Created an account to which I transferred Ethereum.
https://ropsten.etherscan.io/address/0xfbe202d3a837dc07d375ebf227ee5bcab050fa37

Ropsten Etherscan does not work properly because:
Ropsten Etherscan does not work correctly:
Ropsten Etherscan does not work correctly because:

Notice: The Ropsten network is currently forked.
In fact, on balance MetaMask it is now 3,527 Eth.
Using Remix, I began to deploy contracts, one by one, as in the article I recommended reading above.
(use the simplest contract)

Ropsten
0xe4f586a5CAc3603900581b8Ad571326bFB3eB6B0 Nonce-1
0xf4b00679afb7b7fb221d5312568071ae4c54b1f9 Nonce-2
0x621751c275d01653683c9d8d53aa1507ac825c60 Nonce-3
0x53ffea7224d070e9a1c4202612cc5e9190e05dfe Nonce-4
0xf25714710e803ec772d9e2b12e90e6385e770b81 Nonce-5

2. Switched to the same account Rinkeby
https://rinkeby.etherscan.io/address/0xfbe202d3a837dc07d375ebf227ee5bcab050fa37
and began to deploy simple contracts with a light wallet.

3. By the third transaction I sent a message from this network to contract adress created in Ropsten
0xf25714710e803ec772d9e2b12e90e6385e770b81 Nonce-5 -
https://rinkeby.etherscan.io/tx/0x10583ccaf898279456a9a98f8da83b9a71f2af7fe2cc95b161970554fa332aa7
To create a message, I used a previously created contract -
https://rinkeby.etherscan.io/address/0xce7aa541c307d2946b7df8777d793a619120fbee
( How to use the capabilities of this contract and token, that is, how to send messages,
images, websites, etc to the blockchain, described in various projects of this contract
and video - https://bitcointalksearch.org/topic/decentralized-token-4341911 )
The message is encrypted using the Webcrypt service.
Password: "я пpишeл к тeбe c пpивeтoм paccкaзaть чтo coлнцe вcтaлo"
(This example was made for the Russian-speaking community.
The following example will be in English.)

Here I made a mistake: It was necessary to send this transaction from another account.
The fact is that the address to which the message was sent
(0xf25714710e803ec772d9e2b12e90e6385e770b81 Nonce-5) became visible in this account.
In the future, I will make a transaction to the address of the contract Nonce-6 from another account, but more on that later.

4. I continue to deploy contracts until I reach Nonce-5.
And you can see that the contracts created in Ropsten, Rinkeby, as well as in the main network will match each other.
That is, we will see the message sent off on Nonce-5.

5. Correcting my mistake.
I am sending a transaction with a message from another account of the Rinkeby network to the address of the new Nonce-6 contract of the Ropsten network.
Since Ropsten does not work correctly, you will not be able to see its Nonce-6.
The message has already been sent from another account and delivered to Rinkeby’s Nonce-6 address, which you can see tomorrow when I deploy the corresponding Nonce-6 contract on the Rinkeby network.
Let's wait until tomorrow.

Brief conclusions:
You give the address Ethereum a privat key to your future or current offspring, explaining to him what to do:
be deploy out 3-5-7 contracts to get your crypto-testament.
If anything is unclear, ask.
The end of the story tomorrow.