Show Posts
|
Pages: [1] 2 3 »
|
5 hours is very good. Just try Bitcoin and you might wait more than a week to load the full blockchain... It depends on your internet speed... If you dont want to load the full blockchain, use the Loki Electron Wallet https://docs.loki.network/Wallets/WalletsOverview/...and connect to a remote node. It is the wallet that I am using and I connect to a remote node, but when I send with priority Blink tells me PRIORITY ERROR, it also happens with Slow priority, it gives me a TRANSACTION WAS NOT CONSTRUCTED error. by any chance is there a torrent that can download full blockchain?
|
|
|
Just get the latest version and try again
Thank you very much, you are already synchronizing and my coins have already started to appear, another question to withdraw should I wait for the wallet to finish synchronizing? or if there is a faster way to sync the wallet? takes 5 hours and only takes 1% synchronized
|
|
|
Hello, since I started the Loki project I got my wallet and I can't sync it, is there any way to know my balance through the address of my wallet in any Loki block explorer? Thank you.
|
|
|
Coming soon Release date 05/31/2018
|
|
|
Has someone managed to mine? I get an error.
|
|
|
I do not know if I laugh or kill someone jajajaja, the truth is that I transferred 100 XLC to Cryptopia and they arrived without problems, then I sent 50 XLC to cryptopia and they arrive without problems, I am deigned to send me 2500 XLC to Cryptopia and they block me the coins , the wallet generates a TXID but with a question mark "?", I waited several hours and the transaction never appeared, after a couple of hours I had to restart my lapto and when I went back to my wallet I asked for a password , something strange because I never configure it with a password, after that I had to reinstall the wallet and with the backup I had to synchronize the wallet, I reviewed my transaction history and it turns out that there are 100 and 50 that had already been confirmed , but the 2500 disappeared and my balance is 0, hahaha well done by developers, I was scammed.
having a technical problem isn't being scammed. don't say things without a proof I can say that you are stupid idiot but I don't have a proof ... oh wait I do have a proof that you are really really stupid. Anyway we are working on this problem. I think the insults are too, here I have my proofs, the first image shows where the transactions of 2517 are ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi68.tinypic.com%2Faw6eqv.jpg&t=663&c=eyZoQZ93y8T8eQ) After several hours I had a failure with my lapto, restart and when I was opening the wallet again the transaction disappears. ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi63.tinypic.com%2F2d0xveo.jpg&t=663&c=a_3Hz2B0s15S2w) You are hopeless. that is a transaction that has not been mined because of the blocksize issue. I understand perfectly friend, which does not mean that is what I mean, my wallet or the place where I am, because it does not appear in the transaction history.
|
|
|
I do not know if I laugh or kill someone jajajaja, the truth is that I transferred 100 XLC to Cryptopia and they arrived without problems, then I sent 50 XLC to cryptopia and they arrive without problems, I am deigned to send me 2500 XLC to Cryptopia and they block me the coins , the wallet generates a TXID but with a question mark "?", I waited several hours and the transaction never appeared, after a couple of hours I had to restart my lapto and when I went back to my wallet I asked for a password , something strange because I never configure it with a password, after that I had to reinstall the wallet and with the backup I had to synchronize the wallet, I reviewed my transaction history and it turns out that there are 100 and 50 that had already been confirmed , but the 2500 disappeared and my balance is 0, hahaha well done by developers, I was scammed.
having a technical problem isn't being scammed. don't say things without a proof I can say that you are stupid idiot but I don't have a proof ... oh wait I do have a proof that you are really really stupid. Anyway we are working on this problem. I think the insults are too, here I have my proofs, the first image shows where the transactions of 2517 are ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi68.tinypic.com%2Faw6eqv.jpg&t=663&c=eyZoQZ93y8T8eQ) After several hours I had a failure with my lapto, restart and when I was opening the wallet again the transaction disappears. ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi63.tinypic.com%2F2d0xveo.jpg&t=663&c=a_3Hz2B0s15S2w)
|
|
|
I do not know if I laugh or kill someone jajajaja, the truth is that I transferred 100 XLC to Cryptopia and they arrived without problems, then I sent 50 XLC to cryptopia and they arrive without problems, I am deigned to send me 2500 XLC to Cryptopia and they block me the coins , the wallet generates a TXID but with a question mark "?", I waited several hours and the transaction never appeared, after a couple of hours I had to restart my lapto and when I went back to my wallet I asked for a password , something strange because I never configure it with a password, after that I had to reinstall the wallet and with the backup I had to synchronize the wallet, I reviewed my transaction history and it turns out that there are 100 and 50 that had already been confirmed , but the 2500 disappeared and my balance is 0, hahaha well done by developers, I was scammed.
|
|
|
What is the port to mine ETZ?
|
|
|
Several messages I deleted the dev, surely something in mind was brought to forget this.
|
|
|
@NicNacCoin
I have returned for a new question, could you tell me that there is an additional configuration to be done to the server to create the node so that I can run as I should? or am I doing something wrong or the node that is configured in Vultr does not work for CryptoNote?.
The nodes that I have configured in Vultr run me but I do not know if I'm doing it right, because when connecting from my laptop with Windows it does not connect and simplewallet does not synchronize, when you mount the test node with my .conf everything is connected perfectly, Can you help me with the config of the serer in Vultr? I pass you by private user and password of Vultr you can enter with all the confidence and configure 2 nodez and you warn me to do the test from my lapto, you can pass me your wallet BTC for private donation, Thanks
|
|
|
Hi- @NicNacCoin. Could you help me in telling me if my node is running well? if what that shows is the right thing, because when entering the wallet that creates with the same .conf that the nodes have, it tells me that there is an error in synchronizing.
Is this node running well? or is it not working as it should be? fork@tech2:~/forknote-linux$ ./forknoted --config-file configs/technetium.conf Success: Configuration file openned: "configs/technetium.conf" 2018-Jan-02 19:36:18.743872 INFO forknote v2.1.1.1245 () 2018-Jan-02 19:36:18.744925 INFO Module folder: ./forknoted 2018-Jan-02 19:36:18.746964 INFO Opening DB in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.763394 INFO DB opened in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.766321 INFO Initializing core... 2018-Jan-02 19:36:18.777807 INFO Core initialized OK 2018-Jan-02 19:36:18.778304 INFO Initializing p2p server... 2018-Jan-02 19:36:18.778495 INFO Generated new peer ID: 7029398983946693145 2018-Jan-02 19:36:18.778632 INFO Binding on 0.0.0.0:34250 2018-Jan-02 19:36:18.778833 INFO Net service binded on 0.0.0.0:34250 2018-Jan-02 19:36:18.778966 INFO Attempting to add IGD port mapping. 2018-Jan-02 19:36:22.784096 INFO No IGD was found. 2018-Jan-02 19:36:22.784263 INFO P2p server initialized OK 2018-Jan-02 19:36:22.792004 INFO Starting core rpc server on address 127.0.0.1:34377 2018-Jan-02 19:36:22.792378 INFO Core rpc server started ok 2018-Jan-02 19:36:22.792522 INFO Starting p2p net loop... 2018-Jan-02 19:36:22.792608 INFO Starting node_server 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.799842 INFO You are now synchronized with the network. You may now start simplewallet. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command. 2018-Jan-02 19:36:22.799842 INFO Otherwise, you will possibly need to synchronize the blockchain again. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Use "help" command to see the list of available commands. 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.802332 WARNING [207.246.65.66:[b]57677[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:[b]46316[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:[b]33803[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:[b]46890[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:[b]35115[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:[b]38274[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:[b]38731[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:[b]54882[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:[b]54645[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:[b]51703[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:[b]44667[/b] INC] Exception in connectionHandler: TcpConnection::read
Looks like your coins config file has p2p-bind-port= 34250this is just your daemon attempt to connect to 207.246.65.66:(all those other ports) its fine I get that when testing More interested in what error Simplewallet gives(if any)? FYI, you should have at minimun 2 nodes. Once those nodes are up and you get the message "You are now sync.." try connecting with a desktop or laptop. Are you able to connect to this network using 3rd machine in its current state? Most error can be fixed by deleting stored blockchain on server. I tried the simplewallet "reset" but that works like 1 out of 1,000 times. I've notice after v2.0.6 creating Pre-mine coins and getting block reward mismatch or genesis tx coinbase blah blah blah require workaround. then if you test min a few blocks with ZAWY params and let your network go unmined for a period of time and mining resumes the difficulty will adjust to diff 1 and then there's the forknoted "height overhead diff" error that requires another fix. Good luck. reach me by email at support@nicnaccoins.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf EMISSION_SPEED_FACTOR=18 DIFFICULTY_TARGET=120 CRYPTONOTE_DISPLAY_DECIMAL_POINT=12 MONEY_SUPPLY=18446744073709551615 GENESIS_BLOCK_REWARD=0 DEFAULT_DUST_THRESHOLD=1000000 MINIMUM_FEE=1000000 CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW=10 CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE=100000 MAX_TRANSACTION_SIZE_LIMIT=100000 CRYPTONOTE_PUBLIC_ADDRESS_BASE58_PREFIX=287 DIFFICULTY_CUT_V1=60 DIFFICULTY_CUT_V2=60 DIFFICULTY_CUT=0 DIFFICULTY_LAG_V1=15 DIFFICULTY_LAG_V2=15 DIFFICULTY_LAG=0 DIFFICULTY_WINDOW_V1=720 DIFFICULTY_WINDOW_V2=720 DIFFICULTY_WINDOW=17 ZAWY_DIFFICULTY_V3=1 ZAWY_DIFFICULTY_DIFFICULTY_BLOCK_VERSION=3 p2p-bind-port=22850 rpc-bind-port=22851 BYTECOIN_NETWORK=a0a5ac32-4450-4c62-c743-c63d3fe13ba5 CRYPTONOTE_NAME=technetium GENESIS_COINBASE_TX_HEX=010a01ff0001ffffffffffff0f029b2e4c0281c0b02e7c53291a94d1d0cbff8883f8024f5142ee494ffbbd0880712101fff35ac4f45553edcadf0be748fb3dee99d5978f835e21c6949fab34ade1982b MAX_BLOCK_SIZE_INITIAL=100000 UPGRADE_HEIGHT_V2=1 UPGRADE_HEIGHT_V3=30 seed-node=207.246.65.248:22850 seed-node=207.246.112.171:22850 The servers will be active if you want to test, then I will remove it for security reasons. I did it step by step as you explained to me and I still have the same error message in simplewalletC:\fork\forknote>simplewallet.exe --config-file configs/technetium.conf Success: Configuration file openned 2018-Jan-02 23:22:16.774509 INFO forknote wallet v2.1.2.1251 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. o Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: ****** 2018-Jan-02 23:22:25.791290 INFO Loading wallet... Sync from timestamp: 1514857800 2018-Jan-02 23:22:25.838320 INFO Opened wallet: TbcFDrKbVmbA4tzNHvF513FCivJXsZ91TGA7eaL36gwUHrW8YYRScdGdrYfFX4YV4DJPWEt759CojLUMACWPMFWe1rpS1KuUW 2018-Jan-02 23:22:25.842823 INFO ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** 2018-Jan-02 23:22:25.852829 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error
[wallet TbcFDr]: 2018-Jan-02 23:22:30.858810 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:35.870153 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:40.877934 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:10.930158 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:15.949587 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error C:\Users\Crackup\Music\technetium>lib\simplewallet --config-file configs/technetiumcoin.conf Success: Configuration file openned 2018-Jan-02 21:48:51.554000 INFO forknote wallet v2.0.1.1221 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. g Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: **** Sync from timestamp: 1514864938 2018-Jan-02 21:48:58.465000 INFO Generated new wallet: Tbc9gPp3Vih3JWsX75gLr91TxqbuvdJoUe1ufFrCtGKfB1j8tYR84XpTj2pcVmwU661gFfq4EVqJuMBGSaGTmk7q3C1L 2018-Jan-02 21:48:58.465000 INFO view key: f306fea55ad26819f2588b61d9aef3998d46e911c891926c4f8170933f506e01 2018-Jan-02 21:48:58.484000 INFO ********************************************************************** Your wallet has been generated. Use "help" command to see the list of available commands. Always use "exit" command when closing simplewallet to save current session's state. Otherwise, you will possibly need to synchronize your wallet again. Your wallet key is NOT under risk anyway. **********************************************************************
[wallet Tbc9gP]: 2018-Jan-02 21:50:34.051000 INFO Height 1, transaction a7bb9f4ad14af1e3198872f80473d6fb06b5212d01dc352c1575e234075c33dc, received resett 1 of 1 Sync from timestamp: 1514864938 2018-Jan-02 21:54:11.727000 INFO Reset completed successfully. 2018-Jan-02 21:54:12.457000 INFO Height 1, transaction a7bb9f4ad14af1e3198872f80473d6fb06b5212d01dc352c1575e234075c33dc, received 70.368475742208 Those were simply trouble shooting step, no grntee You want to try those 1st in this case I simple made new seeds for the configs on ubuntu 14.04 64 bit Feel free to test yourself using config file param EMISSION_SPEED_FACTOR=18 DIFFICULTY_TARGET=120 CRYPTONOTE_DISPLAY_DECIMAL_POINT=12 MONEY_SUPPLY=18446744073709551615 GENESIS_BLOCK_REWARD=0 DEFAULT_DUST_THRESHOLD=1000000 MINIMUM_FEE=1000000 CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW=10 CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE=100000 MAX_TRANSACTION_SIZE_LIMIT=100000 CRYPTONOTE_PUBLIC_ADDRESS_BASE58_PREFIX=287 DIFFICULTY_CUT_V1=60 DIFFICULTY_CUT_V2=60 DIFFICULTY_CUT=0 DIFFICULTY_LAG_V1=15 DIFFICULTY_LAG_V2=15 DIFFICULTY_LAG=0 DIFFICULTY_WINDOW_V1=720 DIFFICULTY_WINDOW_V2=720 DIFFICULTY_WINDOW=17 ZAWY_DIFFICULTY_V3=1 ZAWY_DIFFICULTY_DIFFICULTY_BLOCK_VERSION=3 p2p-bind-port=22850 rpc-bind-port=22851 BYTECOIN_NETWORK=a0a5ac32-4450-4c62-c743-c63d3fe13ba5 CRYPTONOTE_NAME=technetium GENESIS_COINBASE_TX_HEX=010a01ff0001ffffffffffff0f029b2e4c0281c0b02e7c53291a94d1d0cbff8883f8024f5142ee494ffbbd0880712101fff35ac4f45553edcadf0be748fb3dee99d5978f835e21c6949fab34ade1982b MAX_BLOCK_SIZE_INITIAL=100000 UPGRADE_HEIGHT_V2=1 UPGRADE_HEIGHT_V3=30 seed-node=159.89.46.135:22850 seed-node=159.89.176.66:22850 It works great for me, so my problem is with the nodes? I could even mine a few and everything perfectly. If you like, let's talk about PM.
|
|
|
Hi- @NicNacCoin. Could you help me in telling me if my node is running well? if what that shows is the right thing, because when entering the wallet that creates with the same .conf that the nodes have, it tells me that there is an error in synchronizing.
Is this node running well? or is it not working as it should be? fork@tech2:~/forknote-linux$ ./forknoted --config-file configs/technetium.conf Success: Configuration file openned: "configs/technetium.conf" 2018-Jan-02 19:36:18.743872 INFO forknote v2.1.1.1245 () 2018-Jan-02 19:36:18.744925 INFO Module folder: ./forknoted 2018-Jan-02 19:36:18.746964 INFO Opening DB in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.763394 INFO DB opened in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.766321 INFO Initializing core... 2018-Jan-02 19:36:18.777807 INFO Core initialized OK 2018-Jan-02 19:36:18.778304 INFO Initializing p2p server... 2018-Jan-02 19:36:18.778495 INFO Generated new peer ID: 7029398983946693145 2018-Jan-02 19:36:18.778632 INFO Binding on 0.0.0.0:34250 2018-Jan-02 19:36:18.778833 INFO Net service binded on 0.0.0.0:34250 2018-Jan-02 19:36:18.778966 INFO Attempting to add IGD port mapping. 2018-Jan-02 19:36:22.784096 INFO No IGD was found. 2018-Jan-02 19:36:22.784263 INFO P2p server initialized OK 2018-Jan-02 19:36:22.792004 INFO Starting core rpc server on address 127.0.0.1:34377 2018-Jan-02 19:36:22.792378 INFO Core rpc server started ok 2018-Jan-02 19:36:22.792522 INFO Starting p2p net loop... 2018-Jan-02 19:36:22.792608 INFO Starting node_server 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.799842 INFO You are now synchronized with the network. You may now start simplewallet. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command. 2018-Jan-02 19:36:22.799842 INFO Otherwise, you will possibly need to synchronize the blockchain again. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Use "help" command to see the list of available commands. 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.802332 WARNING [207.246.65.66:[b]57677[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:[b]46316[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:[b]33803[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:[b]46890[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:[b]35115[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:[b]38274[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:[b]38731[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:[b]54882[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:[b]54645[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:[b]51703[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:[b]44667[/b] INC] Exception in connectionHandler: TcpConnection::read
Looks like your coins config file has p2p-bind-port= 34250this is just your daemon attempt to connect to 207.246.65.66:(all those other ports) its fine I get that when testing More interested in what error Simplewallet gives(if any)? FYI, you should have at minimun 2 nodes. Once those nodes are up and you get the message "You are now sync.." try connecting with a desktop or laptop. Are you able to connect to this network using 3rd machine in its current state? Most error can be fixed by deleting stored blockchain on server. I tried the simplewallet "reset" but that works like 1 out of 1,000 times. I've notice after v2.0.6 creating Pre-mine coins and getting block reward mismatch or genesis tx coinbase blah blah blah require workaround. then if you test min a few blocks with ZAWY params and let your network go unmined for a period of time and mining resumes the difficulty will adjust to diff 1 and then there's the forknoted "height overhead diff" error that requires another fix. Good luck. reach me by email at support@nicnaccoins.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf EMISSION_SPEED_FACTOR=18 DIFFICULTY_TARGET=120 CRYPTONOTE_DISPLAY_DECIMAL_POINT=12 MONEY_SUPPLY=18446744073709551615 GENESIS_BLOCK_REWARD=0 DEFAULT_DUST_THRESHOLD=1000000 MINIMUM_FEE=1000000 CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW=10 CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE=100000 MAX_TRANSACTION_SIZE_LIMIT=100000 CRYPTONOTE_PUBLIC_ADDRESS_BASE58_PREFIX=287 DIFFICULTY_CUT_V1=60 DIFFICULTY_CUT_V2=60 DIFFICULTY_CUT=0 DIFFICULTY_LAG_V1=15 DIFFICULTY_LAG_V2=15 DIFFICULTY_LAG=0 DIFFICULTY_WINDOW_V1=720 DIFFICULTY_WINDOW_V2=720 DIFFICULTY_WINDOW=17 ZAWY_DIFFICULTY_V3=1 ZAWY_DIFFICULTY_DIFFICULTY_BLOCK_VERSION=3 p2p-bind-port=22850 rpc-bind-port=22851 BYTECOIN_NETWORK=a0a5ac32-4450-4c62-c743-c63d3fe13ba5 CRYPTONOTE_NAME=technetium GENESIS_COINBASE_TX_HEX=010a01ff0001ffffffffffff0f029b2e4c0281c0b02e7c53291a94d1d0cbff8883f8024f5142ee494ffbbd0880712101fff35ac4f45553edcadf0be748fb3dee99d5978f835e21c6949fab34ade1982b MAX_BLOCK_SIZE_INITIAL=100000 UPGRADE_HEIGHT_V2=1 UPGRADE_HEIGHT_V3=30 seed-node=207.246.65.248:22850 seed-node=207.246.112.171:22850 The servers will be active if you want to test, then I will remove it for security reasons. I did it step by step as you explained to me and I still have the same error message in simplewalletC:\fork\forknote>simplewallet.exe --config-file configs/technetium.conf Success: Configuration file openned 2018-Jan-02 23:22:16.774509 INFO forknote wallet v2.1.2.1251 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. o Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: ****** 2018-Jan-02 23:22:25.791290 INFO Loading wallet... Sync from timestamp: 1514857800 2018-Jan-02 23:22:25.838320 INFO Opened wallet: TbcFDrKbVmbA4tzNHvF513FCivJXsZ91TGA7eaL36gwUHrW8YYRScdGdrYfFX4YV4DJPWEt759CojLUMACWPMFWe1rpS1KuUW 2018-Jan-02 23:22:25.842823 INFO ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** 2018-Jan-02 23:22:25.852829 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error
[wallet TbcFDr]: 2018-Jan-02 23:22:30.858810 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:35.870153 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:40.877934 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:45.887917 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:50.893404 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:55.901803 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error2018-Jan-02 23:23:00.909823 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:05.917073 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:10.930158 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:15.949587 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error
|
|
|
Hi- @NicNacCoin. Could you help me in telling me if my node is running well? if what that shows is the right thing, because when entering the wallet that creates with the same .conf that the nodes have, it tells me that there is an error in synchronizing.
Is this node running well? or is it not working as it should be? fork@tech2:~/forknote-linux$ ./forknoted --config-file configs/technetium.conf Success: Configuration file openned: "configs/technetium.conf" 2018-Jan-02 19:36:18.743872 INFO forknote v2.1.1.1245 () 2018-Jan-02 19:36:18.744925 INFO Module folder: ./forknoted 2018-Jan-02 19:36:18.746964 INFO Opening DB in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.763394 INFO DB opened in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.766321 INFO Initializing core... 2018-Jan-02 19:36:18.777807 INFO Core initialized OK 2018-Jan-02 19:36:18.778304 INFO Initializing p2p server... 2018-Jan-02 19:36:18.778495 INFO Generated new peer ID: 7029398983946693145 2018-Jan-02 19:36:18.778632 INFO Binding on 0.0.0.0:34250 2018-Jan-02 19:36:18.778833 INFO Net service binded on 0.0.0.0:34250 2018-Jan-02 19:36:18.778966 INFO Attempting to add IGD port mapping. 2018-Jan-02 19:36:22.784096 INFO No IGD was found. 2018-Jan-02 19:36:22.784263 INFO P2p server initialized OK 2018-Jan-02 19:36:22.792004 INFO Starting core rpc server on address 127.0.0.1:34377 2018-Jan-02 19:36:22.792378 INFO Core rpc server started ok 2018-Jan-02 19:36:22.792522 INFO Starting p2p net loop... 2018-Jan-02 19:36:22.792608 INFO Starting node_server 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.799842 INFO You are now synchronized with the network. You may now start simplewallet. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command. 2018-Jan-02 19:36:22.799842 INFO Otherwise, you will possibly need to synchronize the blockchain again. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Use "help" command to see the list of available commands. 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.802332 WARNING [207.246.65.66:[b]57677[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:[b]46316[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:[b]33803[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:[b]46890[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:[b]35115[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:[b]38274[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:[b]38731[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:[b]54882[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:[b]54645[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:[b]51703[/b] INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:[b]44667[/b] INC] Exception in connectionHandler: TcpConnection::read
Looks like your coins config file has p2p-bind-port= 34250this is just your daemon attempt to connect to 207.246.65.66:(all those other ports) its fine I get that when testing More interested in what error Simplewallet gives(if any)? FYI, you should have at minimun 2 nodes. Once those nodes are up and you get the message "You are now sync.." try connecting with a desktop or laptop. Are you able to connect to this network using 3rd machine in its current state? Most error can be fixed by deleting stored blockchain on server. I tried the simplewallet "reset" but that works like 1 out of 1,000 times. I've notice after v2.0.6 creating Pre-mine coins and getting block reward mismatch or genesis tx coinbase blah blah blah require workaround. then if you test min a few blocks with ZAWY params and let your network go unmined for a period of time and mining resumes the difficulty will adjust to diff 1 and then there's the forknoted "height overhead diff" error that requires another fix. Good luck. reach me by email at support@nicnaccoins.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf EMISSION_SPEED_FACTOR=18 DIFFICULTY_TARGET=120 CRYPTONOTE_DISPLAY_DECIMAL_POINT=12 MONEY_SUPPLY=18446744073709551615 GENESIS_BLOCK_REWARD=0 DEFAULT_DUST_THRESHOLD=1000000 MINIMUM_FEE=1000000 CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW=10 CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE=100000 MAX_TRANSACTION_SIZE_LIMIT=100000 CRYPTONOTE_PUBLIC_ADDRESS_BASE58_PREFIX=287 DIFFICULTY_CUT_V1=60 DIFFICULTY_CUT_V2=60 DIFFICULTY_CUT=0 DIFFICULTY_LAG_V1=15 DIFFICULTY_LAG_V2=15 DIFFICULTY_LAG=0 DIFFICULTY_WINDOW_V1=720 DIFFICULTY_WINDOW_V2=720 DIFFICULTY_WINDOW=17 ZAWY_DIFFICULTY_V3=1 ZAWY_DIFFICULTY_DIFFICULTY_BLOCK_VERSION=3 p2p-bind-port=22850 rpc-bind-port=22851 BYTECOIN_NETWORK=a0a5ac32-4450-4c62-c743-c63d3fe13ba5 CRYPTONOTE_NAME=technetium GENESIS_COINBASE_TX_HEX=010a01ff0001ffffffffffff0f029b2e4c0281c0b02e7c53291a94d1d0cbff8883f8024f5142ee494ffbbd0880712101fff35ac4f45553edcadf0be748fb3dee99d5978f835e21c6949fab34ade1982b MAX_BLOCK_SIZE_INITIAL=100000 UPGRADE_HEIGHT_V2=1 UPGRADE_HEIGHT_V3=30 seed-node=207.246.65.248:22850 seed-node=207.246.112.171:22850 The servers will be active if you want to test, then I will remove it for security reasons.
|
|
|
Hi- @NicNacCoin. Could you help me in telling me if my node is running well? if what that shows is the right thing, because when entering the wallet that creates with the same .conf that the nodes have, it tells me that there is an error in synchronizing.
|
|
|
Is this node running well? or is it not working as it should be? fork@tech2:~/forknote-linux$ ./forknoted --config-file configs/technetium.conf Success: Configuration file openned: "configs/technetium.conf" 2018-Jan-02 19:36:18.743872 INFO forknote v2.1.1.1245 () 2018-Jan-02 19:36:18.744925 INFO Module folder: ./forknoted 2018-Jan-02 19:36:18.746964 INFO Opening DB in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.763394 INFO DB opened in /home/fork/.technetium/DB 2018-Jan-02 19:36:18.766321 INFO Initializing core... 2018-Jan-02 19:36:18.777807 INFO Core initialized OK 2018-Jan-02 19:36:18.778304 INFO Initializing p2p server... 2018-Jan-02 19:36:18.778495 INFO Generated new peer ID: 7029398983946693145 2018-Jan-02 19:36:18.778632 INFO Binding on 0.0.0.0:34250 2018-Jan-02 19:36:18.778833 INFO Net service binded on 0.0.0.0:34250 2018-Jan-02 19:36:18.778966 INFO Attempting to add IGD port mapping. 2018-Jan-02 19:36:22.784096 INFO No IGD was found. 2018-Jan-02 19:36:22.784263 INFO P2p server initialized OK 2018-Jan-02 19:36:22.792004 INFO Starting core rpc server on address 127.0.0.1:34377 2018-Jan-02 19:36:22.792378 INFO Core rpc server started ok 2018-Jan-02 19:36:22.792522 INFO Starting p2p net loop... 2018-Jan-02 19:36:22.792608 INFO Starting node_server 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.799842 INFO You are now synchronized with the network. You may now start simplewallet. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command. 2018-Jan-02 19:36:22.799842 INFO Otherwise, you will possibly need to synchronize the blockchain again. 2018-Jan-02 19:36:22.799842 INFO 2018-Jan-02 19:36:22.799842 INFO Use "help" command to see the list of available commands. 2018-Jan-02 19:36:22.799842 INFO ********************************************************************** 2018-Jan-02 19:36:22.802332 WARNING [207.246.65.66:57677 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:46316 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:33803 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:46890 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:35115 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:38274 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:38731 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:54882 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:54645 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:51703 INC] Exception in connectionHandler: TcpConnection::read 2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:44667 INC] Exception in connectionHandler: TcpConnection::read
@slb hi. How about this node? it's already working?
|
|
|
|