I'm working on a patch to try to skip the check at block 3712...
so at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
I have the "block 32713 problem" with the last update All of you guys saying you are stuck at this block, isn't it something to do with the secp256k1 update? It won't compile with latest secp256k1, but it does compile fine if you roll back Some people are not even compiling and being stuck at that block So I don't think its a problem with secp256k1 |
|
|
|
I'm working on a patch to try to skip the check at block 3712...
so at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
I have the "block 32713 problem" with the last update Sorry, yes 32712 it starts for me, and I've seen it at 32713 also |
|
|
|
|
I'm working on a patch to try to skip the check at block 3712...
so at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
|
|
|
|
i have run 10 nodes and have no error what is the error?
tail -f debug.log and look at the messages about spork |
|
|
|
the update was released 2 days ago calm down i agree with you Kimowa, never before in the history of bitcointalk, a dev finished a roadmap in just 2 weeks after coin release and delivered so many extra big features as the first mobile wallet with stake and masternodes and people are complaining about minor bugs that always happen in early days with all releases of all coins. ICM also need to rest. I'm sorry but something as simplistic as being able to sync and/or import a bootstrap.dat - that I and other people cannot successfully do is kind of fucked up. something is wrong with client wallet and the way it is importing and/or syncing the blockchain Dev has been asked multiple times and does not respond to any of this. why  ?? |
|
|
|
At this point, I believe that masternode payment enforcement is NOT on. Reasons being:
1. The spork errors many are getting in their error log.
2. The "luck" involved with masternode payments. When masternode enforcement is on, payments should be like clockwork. But many are complaining about long durations between payments.
The problem here is, with Darkcoin, when payment enforcement is NOT on, coins get stolen. There is a means where coins that should get sent to a masternode owner for payment instead get sent to another masternode or not paid at all.
If masternode payment enforcement is not on like I suspect, this is a serious issue and needs to be fixed ASAP.
Dev?
I do wish we could get an answer on this. Also why are so many people not able to sync past 3712 block? Shouldn't be having to copy over other people's block data / blk files! It won't even import from a bootstrap.dat !!! All of this starts to scream at me - someone doesn't know what they're doing or they're messing stuff up !! Seriously .. wtf? And I'm not one trying to say bs about the coin.. these are serious issues that need to be addressed! |
|
|
|
Lets say i can make 14 masternodes
Can someone tell me the safest vps? to rent?
would the vps service providers steal my crave?
would i make good money with 14 masternodes?
Sologap and Kimowa masternodes setup service https://bitcointalk.org/index.php?topic=1016963.0I don't trust them with my 7000 crave (worth a million dollars to me) no offense. If your crave were worth a million dollars to you then you wouldn't trust them with it either. Does anyone know how is it possible to make a masternode in a way were you wouldn't need to trust anyone.(not even the vps service providers like digital ocean) Use the Tor method and your own computer. You can set up as many MN's as you like with that method. Edit: But as others have said, you can trust those people. Others have used them. |
|
|
|
<snipped because of random bullshit spewed>
Please research first. Don't take your butthurt & jealousy that you didn't get into this coin; out on others. |
|
|
|
Update: after researching more, I found a similar syncing problem (in another coin) & that had to do with increasing maximum file descriptors. Tried increasing file descriptors (in Ubuntu trusty) as per this method: http://posidev.com/blog/2009/06/04/set-ulimit-parameters-on-ubuntu/But still no luck, still sticks at 3712 block. with ERROR: AcceptBlock() : incorrect proof-of-stake i fix it by uploading my local win crave folder to dropbox and replacing the one in vps (not the wallet and the .conf) if you want i can do a small tutorial how to do it. not really great but still it fix it. Thanks, I created my own bootstrap.dat from blk's on another computer. Trying to see if it will import.. if it doesn't, I'll copy the whole folder. |
|
|
|
Damn, the aborted rats are falling for the scam...
AGAIN
So how do you afford to eat at $0.23 per post? Welfare queen? Either way, here's some material for you (since yours is so tired). It might help you stay employed. I was syncing from a fresh bootstrap.dat from a fully synced node. The process was incomplete due to "incorrect proof-of-stake". I just found this and I don't have time to debug it. ICM should know about this because not being able to sync from a bootstrap is a deal killer. I can check it out later, but here's my log file: SetBestChain: new best=15682588a31e9064596fc45aa2403558dc62eed296e709e4f577beca1669e788 height=32712
trust=1214093198340208647 blocktrust=15423982777032 date=04/08/15 23:58:24
ProcessBlock: ACCEPTED
SetBestChain: new best=890ccac905c56597ebec4b2da6b2a842fa1a63262a0ebc961ef3a55c809f03b5 height=32713
trust=1214108540505152897 blocktrust=15342164944250 date=04/09/15 00:04:48
ProcessBlock: ACCEPTED
ERROR: AcceptBlock() : incorrect proof-of-stake
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 29, prev=474619e0a58ec88c8e2516f8232064881750e87acac3a416d65b99bd61246968
I just tried syncing from the full 1.4.1 node list at cryptoid, and got the same problem: SetBestChain: new best=15682588a31e9064596fc45aa2403558dc62eed296e709e4f577beca1669e788 height=32712
trust=1214093198340208647 blocktrust=15423982777032 date=04/08/15 23:58:24
ERROR: AcceptBlock() : incorrect proof-of-stake
ProcessBlock: ACCEPTED
Misbehaving: 205.237.142.191:30104 (6 -> 7)
ProcessMessage(dseep, 116 bytes) FAILED
ProcessBlock: ORPHAN BLOCK 306, prev=69c4795c2dd3b1c2e86a2feae955383ba82c5f08d8c1d3b7ea4877061fbd5e96
Same problem here, can we get someone to look into this? A lot of problems sync'ing and being stuck at block 3712 - even after multiple attempts. Using latest cloned & compiled daemon from github & Ubuntu trusty Update: after researching more, I found a similar syncing problem (in another coin) & that had to do with increasing maximum file descriptors. Tried increasing file descriptors (in Ubuntu trusty) as per this method: http://posidev.com/blog/2009/06/04/set-ulimit-parameters-on-ubuntu/But still no luck, still sticks at 3712 block. with ERROR: AcceptBlock() : incorrect proof-of-stake |
|
|
|
<snip> there is no URGE market <snip>
Do you have any proof of that to support your accusations? No, didn't think so. Do you have any proof that dev has not delivered things so far? No, didn't think so. |
|
|
|
Sorry man,just tried to help
No, its not that! I appreciate the help! Its just i'm concerned about security and the risk to people. Not saying your upload is bad or anything, just prefer official source  |
|
|
|
Could we please get an official bootstrap.dat to sync from? I know how to create my own, but just saying we shouldn't have random people uploading blk files  Problem is - latest crave daemon compiled from github won't even sync ! |
|
|
|
Damn, the aborted rats are falling for the scam...
AGAIN
So how do you afford to eat at $0.23 per post? Welfare queen? Either way, here's some material for you (since yours is so tired). It might help you stay employed. I was syncing from a fresh bootstrap.dat from a fully synced node. The process was incomplete due to "incorrect proof-of-stake". I just found this and I don't have time to debug it. ICM should know about this because not being able to sync from a bootstrap is a deal killer. I can check it out later, but here's my log file: SetBestChain: new best=15682588a31e9064596fc45aa2403558dc62eed296e709e4f577beca1669e788 height=32712
trust=1214093198340208647 blocktrust=15423982777032 date=04/08/15 23:58:24
ProcessBlock: ACCEPTED
SetBestChain: new best=890ccac905c56597ebec4b2da6b2a842fa1a63262a0ebc961ef3a55c809f03b5 height=32713
trust=1214108540505152897 blocktrust=15342164944250 date=04/09/15 00:04:48
ProcessBlock: ACCEPTED
ERROR: AcceptBlock() : incorrect proof-of-stake
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 29, prev=474619e0a58ec88c8e2516f8232064881750e87acac3a416d65b99bd61246968
I just tried syncing from the full 1.4.1 node list at cryptoid, and got the same problem: SetBestChain: new best=15682588a31e9064596fc45aa2403558dc62eed296e709e4f577beca1669e788 height=32712
trust=1214093198340208647 blocktrust=15423982777032 date=04/08/15 23:58:24
ERROR: AcceptBlock() : incorrect proof-of-stake
ProcessBlock: ACCEPTED
Misbehaving: 205.237.142.191:30104 (6 -> 7)
ProcessMessage(dseep, 116 bytes) FAILED
ProcessBlock: ORPHAN BLOCK 306, prev=69c4795c2dd3b1c2e86a2feae955383ba82c5f08d8c1d3b7ea4877061fbd5e96
Same problem here, can we get someone to look into this? A lot of problems sync'ing and being stuck at block 3712 - even after multiple attempts. |
|
|
|
How to creat masternode without VPS Use TOR |
|
|
|
|
anyone have a list of some onion nodes I can addnode in my conf?
|
|
|
|
Getting this when trying to compile daemon with latest secp256k1 installed: key.cpp:729:106: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_tweak_add(const secp256k1_context_t*, unsigned char*, int, const unsigned char*)’
bool ret = secp256k1_ec_pubkey_tweak_add((unsigned char*)pubkeyChild.begin(), pubkeyChild.size(), out);
^
make: *** [obj/key.o] Error 1
I'm assuming because as was mentioned, crave daemon does not currently support latest secp256k1 ? Had to do this to get it to actually reset/rollback and successfully compile: git clone https://github.com/bitcoin/secp256k1
cd secp256k1
git reset a0d3b8
git add .
git reset --hard
./autogen.sh
./configure
make
sudo make install
cd ..
sudo ldconfig
cd crave/src
make -f makefile.unix USE_UPNP=
strip craved |
|
|
|
Getting this when trying to compile daemon with latest secp256k1 installed: key.cpp:729:106: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_tweak_add(const secp256k1_context_t*, unsigned char*, int, const unsigned char*)’
bool ret = secp256k1_ec_pubkey_tweak_add((unsigned char*)pubkeyChild.begin(), pubkeyChild.size(), out);
^
make: *** [obj/key.o] Error 1
I'm assuming because as was mentioned, crave daemon does not currently support latest secp256k1 ? |
|
|
|
I have my node working on my ip now but when i try to run through tor it says i am unable to connect.
test to make sure your ports are open. are you sure tor is running? put in some addnodes in your conf |
|
|
|
|
Show Posts
