Topic: Sending Encrypted Text Messages via BlockChain - page 2. (Read 3491 times)
there you go again taking shots at my mom agian!
Either that or the transactions would have to be sent over a longer time period to ensure that they are confirmed in order.
Yeah, basically you'd have to cron job the block chain for confirmed transaction then send the next letter so the time would take (if your lucky) 10 minutes per letter :/You could however have one transaction represent multiple letters (maybe up to 5 letters) for example
with single letters(to show a comparison)
Quote
A(0.00000001 BTC)
-
Z(0.00000026 BTC)
-
Z(0.00000026 BTC)
Multiple letters
Quote
AA(0.00000027 BTC)
AB(0.00000028 BTC)
....
....
AZ(0.00000054 BTC)
....
....
BZ(0.00000080 BTC)
You get the point...AB(0.00000028 BTC)
....
....
AZ(0.00000054 BTC)
....
....
BZ(0.00000080 BTC)
do not needlessly pollute the blockchain
nah, you could just put 01,02,03... prefix or suffix to make sure correct order and send them all in one batch
Either that or the transactions would have to be sent over a longer time period to ensure that they are confirmed in order.
Great idea, but what if the network accepts the payments in a funny order? Certainly won't always be the case, but it might happen. Your message of "cheese" could turn into "echsee"
Hmm maybe there is a timestamp when they were "sent" to the nodes (instead of looking at the timestamps when they were mined into a block)
Great idea, but what if the network accepts the payments in a funny order? Certainly won't always be the case, but it might happen. Your message of "cheese" could turn into "echsee"
Hmmmm this could be made into a wevsite easily!!!
YOU TAKE THAT BACK ABOUT MY MOTHER!!!!
I thought of this last night, and not sure if this approached has been discussed before. The following is an example of how a rogue entity could send encrypted text messages back and forth to one another, and still keep the coins between themselves.
.011002
.011111
.01102
.0102
.0111
.01111
.0102
.011002
.01101
.01001
.011101
.011
.0102
.020101
.020002
.0211102
.021
.02101
.021
.02011
.020111
.0211
.02011
.02001
.021
The above that I devised is based on the simplest code readily available, but a more complex coding system, with each person having the key, can create a more complex one that would be a hell of a lot harder to crack. And it could all be done in the open for all to see.
In fact, a simple program could be built to create the sums on demand, ready to be hand-sent one-by-one or automatically, not all at once, but at a rate as if a human were inputting the amounts.
I started this post to bring awareness that this option exist and should be deeply considered.
Can you crack the code above?
~Bruno~
.011002
.011111
.01102
.0102
.0111
.01111
.0102
.011002
.01101
.01001
.011101
.011
.0102
.020101
.020002
.0211102
.021
.02101
.021
.02011
.020111
.0211
.02011
.02001
.021
The above that I devised is based on the simplest code readily available, but a more complex coding system, with each person having the key, can create a more complex one that would be a hell of a lot harder to crack. And it could all be done in the open for all to see.
In fact, a simple program could be built to create the sums on demand, ready to be hand-sent one-by-one or automatically, not all at once, but at a rate as if a human were inputting the amounts.
I started this post to bring awareness that this option exist and should be deeply considered.
Can you crack the code above?
~Bruno~
Jump to: