About FTC Pay Remarks, a very far function
-
Pay Remarks allows simple plaintext.People sending coins can insert arbitrary strings of their choosing into the blockchain.Remarks can be encrypted with the public key so only the owner of the private key can read them.
I think it would be a really nice user experience for people to send messages, even if private, with their payments like “here are your FTC I promised, thanks for the beers”. But for it to really work it would have to work on all wallets not just the QT client. I see the message could be useful to vendors as a cryptographic receipt system.
against spam and offensive links
There has to be a limit on the size of the message and the message should be included when working out the fee. I would suggest a much small payment level.If the length is less than 40 bytes,that would be 0.05 (FTC).If the length is less than 140 bytes,that would be 0.5 (FTC).
The disadvantage
there would be a message blockchain, if the miner wins they would have to extra work creating the message block chain. Also the extra network traffic, cost.
Also note that this would require a hard fork so that current clients would not be compatible with clients with messaging.
Add “tx-comment” in Blockchain, the code was easy . Your any ideas please let me know.Lets go ahead. :)
-
Sorry I missed this.
So, currently we can’t put a message with the transaction and have that message be encrypted end to end?
I agree with Lizhi that this would be a required feature for a coin in the real world.
By that I mean, if a coin is to live well into the future, I can see been able to have encrypted messages, been a required standard.
-
I wrote some of the most basic code.This is a good start. ;)
**FIFA world cup, **Code and football, exciting.
Off-Topic ARGENTINA !! Messi !!
-
I am testing the code, I encountered a problem. After starting the wallet, it automatically exits. :-[
How to output information to debug.log file ?
debug.log
2014-06-28 02:46:53 Feathercoin version v0.8.6.2-g463f61a-RTM (Wed, 16 Apr 2014 20:46:36 +0100)
2014-06-28 02:46:53 Using OpenSSL version OpenSSL 1.0.1h 5 Jun 2014
2014-06-28 02:46:53 Default data directory C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin
2014-06-28 02:46:53 Using data directory C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin
2014-06-28 02:46:53 Using at most 125 connections (2048 file descriptors available)
2014-06-28 02:46:53 Using 2 threads for script verification
2014-06-28 02:46:53 init message: Verifying wallet…
2014-06-28 02:46:53 dbenv.open LogDir=C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin\database ErrorFile=C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin\db.log
2014-06-28 02:46:53 Bound to [::]:9336
2014-06-28 02:46:53 Bound to 0.0.0.0:9336
2014-06-28 02:46:53 init message: Loading block index…
2014-06-28 02:46:53 Opening LevelDB in C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin\blocks\index
2014-06-28 02:46:53 Opened LevelDB successfully
2014-06-28 02:46:53 Opening LevelDB in C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin\chainstate
2014-06-28 02:46:53 Opened LevelDB successfully
2014-06-28 02:46:53 LoadBlockIndexDB(): last block file = 0
2014-06-28 02:46:53 LoadBlockIndexDB(): synchronized checkpoint 12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2
2014-06-28 02:46:53 LoadBlockIndexDB(): transaction index disabled
2014-06-28 02:46:53 Initializing databases…
2014-06-28 02:46:53 init message: Verifying blocks…
2014-06-28 02:46:53 block index 182ms
2014-06-28 02:46:53 init message: Loading wallet…
then feathercoin-qt.exe automatically quit. :(
