All - Activity - Richard - Algorand
Algorand co-chains
Mar 24, 2020
Really great. . This solves another big problem in the blockchain field, and Algorand is becoming infinite. Waiting for the coming upgrade. I am not sure whether a ‘layer-1 co-chain’ needs an additional full-node server or not. If no need, then it is easy for new users to join in at a low cost and bring …
A Proposal - Develop an incentive mechanism for Algorand
Mar 14, 2020
We do believe that an incentive mechanism will attract more participants and bring forward a higher price. To popularize Algorand, there are some possible solutions:
- Let’s build an independent algoPOW chain. The POW miners dig to get algoPOW, and then exchange for Algo at a rate of 1:1, or 1:…
Why KYC is required for the auction, is there any compulsory law
Jan 16, 2020
Maybe in the future the tokens will be sold by Algorand’s subsidiary? Algorand Cayman SEZC, a Cayman Islands subsidiary of Algorand, Inc., is the sole owner of all tokens held by any of Algorand, Inc. or its subsidiaries, as said in Algorand Transparency Report.
Why KYC is required for the auction, is there any compulsory law
Jan 8, 2020
Why is KYC required for the auction? Is there anything compulsory? Less buyers means less popularity. We do not know why it limits too much.
A suggestion for a light-client wallet (like the BTC SPV wallet with Merkle tree)
Dec 31, 2019
Now testing:
- Delete the file node.log and then reboot; the system generates node.log again, without node.log.archive which might be a backup of node.log.
- Backup the file agreement.cdv and agreement.cdv.archive; then delete them and reboot; the system generates agreement.cdv, without agreement…
A suggestion for a light-client wallet (like the BTC SPV wallet with Merkle tree)
Dec 31, 2019
The biggest files are agreement.cdv, agreement.cdv.archive,node.archive.log, node.log and they increase over time. I guess, if the *.log files are deleted, it does not affect the Algorand server. Not sure about agreement.cdv and agreement.cdv.archive; agreement.cdv.archive seems to be a backup of agreement…
A suggestion for a light-client wallet (like the BTC SPV wallet with Merkle tree)
Dec 31, 2019
/var/lib/algorand# ls -l
total 3082292
-rw-r--r-- 1 algorand algorand 935810534 Jan 1 11:17 agreement.cdv
-rw-r--r-- 1 algorand algorand 1073742650 Jan 1 10:00 agreement.cdv.archive
-rw------- 1 algorand algorand 0 Dec 17 09:06 algod.lock
-rw-r--r-- 1 algorand algorand 15 Dec 3…