|
popcoins
|
 |
October 01, 2017, 04:55:04 PM |
|
Hi, I have a few questions Huh
1 how profitable, one input or split coins into several equal parts?
2 you can use the minicomputer to PoS mining >>> Raspberry/Orange?
Thanks!!!
As far as I know, LADAcoin is only PoW mining and only mine with CPU devices, and there is no PoS mining for LADA. |
|
|
|
|
|
|
|
|
|
|
Whoever mines the block which ends up containing your transaction will get its fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
LADAcoin (OP)
|
|
October 15, 2017, 10:53:55 AM |
|
New wallet download: New Latest Ladacoin: v0.10.4.10-5560b6e Download v0.10.4.10-5560b6e: v0.10.4.97 |
|
|
|
m1rk0z
Newbie
 Offline
Activity: 16
Merit: 0
|
|
October 16, 2017, 09:58:19 PM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
|
|
|
|
|
|
popcoins
|
|
October 17, 2017, 07:59:24 AM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers  |
|
|
|
m1rk0z
Newbie
Offline
Activity: 16
Merit: 0
|
|
October 17, 2017, 02:23:15 PM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. |
|
|
|
|
|
LADAcoin (OP)
|
|
October 17, 2017, 04:00:08 PM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet |
|
|
|
m1rk0z
Newbie
Offline
Activity: 16
Merit: 0
|
|
October 17, 2017, 04:32:28 PM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet Done right now. Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less). |
|
|
|
|
|
popcoins
|
|
October 19, 2017, 09:55:46 AM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet Done right now. Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less). This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-) |
|
|
|
m1rk0z
Newbie
Offline
Activity: 16
Merit: 0
|
|
October 19, 2017, 11:09:04 AM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet Done right now. Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less). This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-) Have you been able to sync correctly? Or do you have the same problem? I tried connecting to a "good" node, but I get an error regarding wrong header and I don't know what to do. By the way, I think I'm able to download till the last block (reporter by the explorer) and as soon as I have it in my blockchain I get the segfault (and it stops debug.log from recording all the info, cause I see from strace a "Done loading" which isn't in debug file). If it is a bug already seen developers should address it... |
|
|
|
|
|
LADAcoin (OP)
|
|
October 19, 2017, 02:44:40 PM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet Done right now. Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less). This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-) Have you been able to sync correctly? Or do you have the same problem? I tried connecting to a "good" node, but I get an error regarding wrong header and I don't know what to do. By the way, I think I'm able to download till the last block (reporter by the explorer) and as soon as I have it in my blockchain I get the segfault (and it stops debug.log from recording all the info, cause I see from strace a "Done loading" which isn't in debug file). If it is a bug already seen developers should address it... Please quote here last entered debug.log. I want see this error in to debug.log And what do you connect to the wallet after synchronization? |
|
|
|
|
popcoins
|
|
October 19, 2017, 03:06:51 PM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet Done right now. Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less). This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-) Have you been able to sync correctly? Or do you have the same problem? I tried connecting to a "good" node, but I get an error regarding wrong header and I don't know what to do. By the way, I think I'm able to download till the last block (reporter by the explorer) and as soon as I have it in my blockchain I get the segfault (and it stops debug.log from recording all the info, cause I see from strace a "Done loading" which isn't in debug file). If it is a bug already seen developers should address it... Try to limit your node connections to max of 4, so only the good nodes that you found from the explorer, those that are fully syned, then add the good ones to the .conf file. So when the wallet first executed should connect straight to those working ones. This should bypass the troubling nodes. |
|
|
|
m1rk0z
Newbie
Offline
Activity: 16
Merit: 0
|
|
October 19, 2017, 07:28:08 PM |
|
Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet Done right now. Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less). This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-) Have you been able to sync correctly? Or do you have the same problem? I tried connecting to a "good" node, but I get an error regarding wrong header and I don't know what to do. By the way, I think I'm able to download till the last block (reporter by the explorer) and as soon as I have it in my blockchain I get the segfault (and it stops debug.log from recording all the info, cause I see from strace a "Done loading" which isn't in debug file). If it is a bug already seen developers should address it... Please quote here last entered debug.log. I want see this error in to debug.log And what do you connect to the wallet after synchronization? The log is normal, nothing strange, just block syncing and suddenly it stops (when I get the segmentation fault from the daemon). I will post the (last part of) debug.log as soon as I resync the daemon What does the second question mean? I just start the daemon, I wait for it to sync and, just when it approaches last blocks... crash! Hi,
I've download the latest wallet and it segfaults when it reaches current block downloading. How can I solve?
Have you managed to get it worked out syn to the current block? By the way what is "segfaults"? Please let me know your progress if you can, I am just about to test the new wallet. Cheers It just arrives at the last block or few blocks before and the daemon crashes with a segmentation fault error (a common error given when a program tries to access illegal area in the RAM). If I use the old wallet all works flawlessly but it syncs to an height above the one reported by the explorer/Cryptopia (a separate blockchains for the new wallet?) Let me know if you encounter the same problem, too. Please resynchronize the wallet from the very beginning, delete the folders blocks chainstate and delete file peers.dat and restart ladacoin wallet Done right now. Deleted old ladacoin datadir, started the already compiled wallet, it synced till block 261543 and then crashed. When I restarted it went on from block ~160000 (about 100000 blocks less). This has happened before back to the last version of the Ladacoin wallet. It was casused because a few nodes was connected to my wallet and their blocks was stucked and not being syned correctly. I think we have to search the right nodes and have them edited in the .conf file so when the wallet first executed it will connect to tbe right nodes at start. Hope this will work out. ;-) Have you been able to sync correctly? Or do you have the same problem? I tried connecting to a "good" node, but I get an error regarding wrong header and I don't know what to do. By the way, I think I'm able to download till the last block (reporter by the explorer) and as soon as I have it in my blockchain I get the segfault (and it stops debug.log from recording all the info, cause I see from strace a "Done loading" which isn't in debug file). If it is a bug already seen developers should address it... Try to limit your node connections to max of 4, so only the good nodes that you found from the explorer, those that are fully syned, then add the good ones to the .conf file. So when the wallet first executed should connect straight to those working ones. This should bypass the troubling nodes. How to set max connections to 4? Btw, thanks for your help |
|
|
|
|
m1rk0z
Newbie
Offline
Activity: 16
Merit: 0
|
|
October 19, 2017, 07:42:44 PM |
|
I synced last blocks with '-maxconnections=4' and... IT WORKED!
Really really thanks popcoins!
After that I restarted the daemon without arguments and no problem whatsoever.
|
|
|
|
|
Funnymyth
Newbie
Offline
Activity: 14
Merit: 0
|
|
October 20, 2017, 03:53:57 AM |
|
is there going to be a masternode for this coin?
|
|
|
|
|
Funnymyth
Newbie
Offline
Activity: 14
Merit: 0
|
|
October 20, 2017, 04:06:32 AM |
|
is there a telegram or slack set up for up to date information?
|
|
|
|
|
|
|
|
popcoins
|
|
October 23, 2017, 12:15:41 PM |
|
I synced last blocks with '-maxconnections=4' and... IT WORKED!
Really really thanks popcoins!
After that I restarted the daemon without arguments and no problem whatsoever.
It seems there are still some issues behind the network or the wallet about syn problem, even though we managed to syn up with limited connections. Hope devs is already looking into this.  |
|
|
|
hammerhart
Member
Offline
Activity: 381
Merit: 11
|
|
November 02, 2017, 03:09:32 PM |
|
is there still some activities going on? bought some in the past and wonder if the project is frogtten..
|
|
|
|
|
|
popcoins
|
|
November 05, 2017, 05:41:36 PM |
|
is there still some activities going on? bought some in the past and wonder if the project is frogtten..
Just leave your request here or send PM to devs, they will get back to you or reply you here. Sometimes it will take them a while, but will get back to you eventually |
|
|
|
|
LADAcoin (OP)
|
|
November 08, 2017, 11:45:20 AM |
|
LADACoin(LDC) Node info
addnode=52.14.135.22:8833
addnode=46.183.165.155:8833
addnode=34.210.65.170:8833
addnode=35.176.43.173:8833
addnode=35.177.255.125:8833
|
|
|
|
|
