Topic: [ANN][EVM][Argon2id]💧Aquachain (AQUA)💧Programmable Money - page 15. (Read 23320 times)
no website, little information, typical shitcoin... plans to be listed on any exchange?
any chance we can get a discord group going? telegram's ok but demands a telephone number where discord just needs an email
For sure. Can you make it and post here?
discord server:
https://discord.gg/J7jBhZf
any chance we can get a discord group going? telegram's ok but demands a telephone number where discord just needs an email
For sure. Can you make it and post here?
any chance we can get a discord group going? telegram's ok but demands a telephone number where discord just needs an email
I want to support this project, and I think there is a lot of work still to be done.
Hey, thanks! I agree there is ton of work to be done!
there is chat group on telegram: https://t.me/AquaCrypto
any other people wanting to contribute stop on by or leave a pull request!
it's a pleasure to be involved. glad I was able to be a help today. And thanks for your help with my finally being able to send AQUA!
Anything else you need, let me know.
I want to support this project, and I think there is a lot of work still to be done.
Hey, thanks! I agree there is ton of work to be done!
there is chat group on telegram: https://t.me/AquaCrypto
any other people wanting to contribute stop on by or leave a pull request!
I want to support this project, and I think there is a lot of work still to be done.
Hi, what happen when there is hardfork but we didn't update the client? Is it necessary to always keep up to date to recent fork?
well yeah but i'd assume everyone would get plenty of notice
Hi, what happen when there is hardfork but we didn't update the client? Is it necessary to always keep up to date to recent fork?
ERROR[03-16|23:12:42]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14
400}
Number: 9476
Hash: 0xb79dd8b38155b63a59eb4843060134d6f1be55bcaa183b66ff88838ec5b5e6a5
Error: duplicate uncle
##############################
ERROR[03-16|23:12:51]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14
400}
Number: 9476
Hash: 0xb8daa7d69d0d23e3f9f08bc156293b6cbe2c386e71fa22324eb82d30fdf5a72a
Error: uncle is ancestor
##############################
ERROR[03-16|23:12:58]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14
400}
Number: 9476
Hash: 0x9f3ece22d3567d8f29c3e8a6f7d13ba78ac729d99f30d380e8d86e165afae138
Error: uncle's parent is not ancestor
##############################
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14
400}
Number: 9476
Hash: 0xb79dd8b38155b63a59eb4843060134d6f1be55bcaa183b66ff88838ec5b5e6a5
Error: duplicate uncle
##############################
ERROR[03-16|23:12:51]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14
400}
Number: 9476
Hash: 0xb8daa7d69d0d23e3f9f08bc156293b6cbe2c386e71fa22324eb82d30fdf5a72a
Error: uncle is ancestor
##############################
ERROR[03-16|23:12:58]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14
400}
Number: 9476
Hash: 0x9f3ece22d3567d8f29c3e8a6f7d13ba78ac729d99f30d380e8d86e165afae138
Error: uncle's parent is not ancestor
##############################
reserve Chinese translation
if i created 2 accounts, which one will mining go to? the most recently created, or the first one created?
edit: to answer my own question, it goes to the first address created. is there any way to specify to which account you mine to?
edit2: miner.setAquabase(aqua.accounts[1]) will set the the second address created as the one in use (index starts at 0)
edit: to answer my own question, it goes to the first address created. is there any way to specify to which account you mine to?
edit2: miner.setAquabase(aqua.accounts[1]) will set the the second address created as the one in use (index starts at 0)
Hi,
"Current hashing algo: ethash (will change HF3)"
What algo is HF3? Why start with ethash and then change the algo?
What will you do with the unclaimed coins after the algo change?
Good luck!
"Current hashing algo: ethash (will change HF3)"
What algo is HF3? Why start with ethash and then change the algo?
What will you do with the unclaimed coins after the algo change?
Good luck!
Scheduled HF, no claiming just update!
Hi,
"Current hashing algo: ethash (will change HF3)"
What algo is HF3? Why start with ethash and then change the algo?
What will you do with the unclaimed coins after the algo change?
Good luck!
"Current hashing algo: ethash (will change HF3)"
What algo is HF3? Why start with ethash and then change the algo?
What will you do with the unclaimed coins after the algo change?
Good luck!
it looks like it gave up on that block(?) and gave the message
WARN [03-16|09:30:34] Synchronisation failed, dropping peer peer=730c94a7227d2ef8 err="retrieved hash chain is invalid"
then it gave me the original error again, but itstead of #9134, it said #9136. but now it seems to be importing new chain segments... lol.... i have no clue whats going on... I'm gonna just go have a coffee and see whats up in like 30 mins..
WARN [03-16|09:30:34] Synchronisation failed, dropping peer peer=730c94a7227d2ef8 err="retrieved hash chain is invalid"
then it gave me the original error again, but itstead of #9134, it said #9136. but now it seems to be importing new chain segments... lol.... i have no clue whats going on... I'm gonna just go have a coffee and see whats up in like 30 mins..
sorts itself out eventually looks like it just needs good peers
it looks like it gave up on that block(?) and gave the message
WARN [03-16|09:30:34] Synchronisation failed, dropping peer peer=730c94a7227d2ef8 err="retrieved hash chain is invalid"
then it gave me the original error again, but itstead of #9134, it said #9136. but now it seems to be importing new chain segments... lol.... i have no clue whats going on... I'm gonna just go have a coffee and see whats up in like 30 mins..
WARN [03-16|09:30:34] Synchronisation failed, dropping peer peer=730c94a7227d2ef8 err="retrieved hash chain is invalid"
then it gave me the original error again, but itstead of #9134, it said #9136. but now it seems to be importing new chain segments... lol.... i have no clue whats going on... I'm gonna just go have a coffee and see whats up in like 30 mins..
same, managed to mine a few now keep getting this
Code:
INFO [03-16|13:31:15] Block synchronisation started
INFO [03-16|13:31:15] Mining aborted due to sync
ERROR[03-16|13:31:17]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14400}
Number: 9134
Hash: 0xd372ead31b9ab37886b9b4edbc340a0c98bf5789240cb4efe3d276938d5720ea
Error: uncle's parent is not ancestor
##############################
WARN [03-16|13:31:17] Synchronisation failed, dropping peer peer=d435bc2789d54ad3 err="retrieved hash chain is invalid"
INFO [03-16|13:31:17] Starting mining operation
INFO [03-16|13:31:17] Commit new mining work number=9134 txs=0 uncles=0 elapsed=345.955µs diff=188801209 gas=0
INFO [03-16|13:31:20] Generating DAG in progress epoch=1 percentage=2 elapsed=34.234s
same here.
trying to run the console and been getting this message over and over for like 10 minutes. am i doing something wrong?
ERROR[03-16|09:27:47]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14400}
Number: 9134
Hash: 0x22edd012cd35fcd1c82d63dc7e7d707ebfc4bb4f71efc99d64df12d00aae098b
Error: uncle's parent is not ancestor
##############################
ERROR[03-16|09:27:47]
########## BAD BLOCK #########
Chain config: {ChainID: 1, Engine: aquahash, HF-Ready: 0:3000 1:3600 2:7200 3:14400}
Number: 9134
Hash: 0x22edd012cd35fcd1c82d63dc7e7d707ebfc4bb4f71efc99d64df12d00aae098b
Error: uncle's parent is not ancestor
##############################
Jump to: