Author

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 2988. (Read 9723803 times)

legendary
Activity: 1318
Merit: 1040
Hmm i'm having some trouble with the latest version:

PROCESSMESSAGE: INVALID MESSAGESTART
2015-02-13 23:01:12 Added time data, samples 72, offset +0 (+0 minutes)
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: CheckProofOfWork() : nBits below minimum work
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Errors in block header

Happened two times already, a restart with -reindex works - lets see how long it rolls this time.

Anyone else problems with crashing wallet ?

My disk is ok btw.. Just ran a check ..

Had the same on a couple of nodes, deleted peers.dat and -reindex - all good again!


I did -reindex too - did not help, I deleted the blockchain and the peers now.. Lets see

In case reindex fails try to sync using bootstrap https://github.com/UdjinM6/darkcoin-bootstrap

EDIT: and btw, can I have debug.log please?  Roll Eyes [email protected]
legendary
Activity: 1030
Merit: 1006
I casn't believe how greedy are some of those fucking miners ... absolutely no precaution was taken to hide his tracks actually.
Shameful.
It's the pool..

I aggree that what lack of ethic!!!

So for each block found by the hatd work of their miner, they was robing 1.75DRK for each block!!!

MiningPoolHub was doing this. Quit this POOL!!!

True enough, I should have said the MiningPoolHub pool operator scammer, miners are actually used and victims as much as the MN owners.
Are we shure that they have ONLY ONE masternode?
full member
Activity: 160
Merit: 100
I didn't get paid for days because of these freaks, profiting on our back ...

We should be extremely careful with every major overhaul of the network ..

Our development cycles are going to start slowing down now that we have IX & DS out there and working properly.

Maybe we just need to give a little more time for security testing, trying to recreate some scenarios of bad acting to prevents possible issues on mainnet.
It should be great if we could contribute as testers  in this aspect also Smiley .
member
Activity: 97
Merit: 10
v0.11.1.25 - MANDATORY UPDATE

Due to some pools taking advantage of paying the incorrect masternodes (on purpose), enabling enforcement failed earlier today. Please update to the latest version of the software, 11.1.25, which includes a much stronger policy for enforcing masternode payments. This will also cause bans on any clients mining on the wrong chain. After the entire network updates (Pools, Exchanges, Masternodes, etc), we'll activate enforcement again.

https://www.darkcoin.io/downloads/





I am VERY COOL with Enforcement being turned on ASAP

Don't wait for me - kill that theif ASAP

He won't wait for you, but he will for the network to be updated to 11.1.25.
30% of the MNs are uptodate for the moment.


legendary
Activity: 2702
Merit: 1240
Hmm i'm having some trouble with the latest version:

PROCESSMESSAGE: INVALID MESSAGESTART
2015-02-13 23:01:12 Added time data, samples 72, offset +0 (+0 minutes)
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: CheckProofOfWork() : nBits below minimum work
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Errors in block header

Happened two times already, a restart with -reindex works - lets see how long it rolls this time.

Anyone else problems with crashing wallet ?

My disk is ok btw.. Just ran a check ..

Had the same on a couple of nodes, deleted peers.dat and -reindex - all good again!


I did -reindex too - did not help, I deleted the blockchain and the peers now.. Lets see
legendary
Activity: 1036
Merit: 1000
I didn't get paid for days because of these freaks, profiting on our back ...

We should be extremely careful with every major overhaul of the network ..

Our development cycles are going to start slowing down now that we have IX & DS out there and working properly.

Evan, Can we please enable the InstantX API so Exchanges can use it?
legendary
Activity: 1036
Merit: 1000
Hmm i'm having some trouble with the latest version:

PROCESSMESSAGE: INVALID MESSAGESTART
2015-02-13 23:01:12 Added time data, samples 72, offset +0 (+0 minutes)
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: CheckProofOfWork() : nBits below minimum work
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Errors in block header

Happened two times already, a restart with -reindex works - lets see how long it rolls this time.

Anyone else problems with crashing wallet ?

My disk is ok btw.. Just ran a check ..

Had the same on a couple of nodes, deleted peers.dat and -reindex - all good again!
legendary
Activity: 2702
Merit: 1240
Hmm i'm having some trouble with the latest version:

PROCESSMESSAGE: INVALID MESSAGESTART
2015-02-13 23:01:12 Added time data, samples 72, offset +0 (+0 minutes)
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: CheckProofOfWork() : nBits below minimum work
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Errors in block header

Happened two times already, a restart with -reindex works - lets see how long it rolls this time.

Anyone else problems with crashing wallet ?

My disk is ok btw.. Just ran a check ..
legendary
Activity: 1036
Merit: 1000
v0.11.1.25 - MANDATORY UPDATE

Due to some pools taking advantage of paying the incorrect masternodes (on purpose), enabling enforcement failed earlier today. Please update to the latest version of the software, 11.1.25, which includes a much stronger policy for enforcing masternode payments. This will also cause bans on any clients mining on the wrong chain. After the entire network updates (Pools, Exchanges, Masternodes, etc), we'll activate enforcement again.

https://www.darkcoin.io/downloads/


legendary
Activity: 1456
Merit: 1000
I didn't get paid for days because of these freaks, profiting on our back ...

We should be extremely careful with every major overhaul of the network ..

Our development cycles are going to start slowing down now that we have IX & DS out there and working properly.

I see you're starting optimizations on the wallet. Any idea on some outstanding features:

-Masternode Obfuscation
-Masternode Blinding (you mentioned about fragmenting inputs across multiple masternodes)
-2FA

Dude. The guy just created eCash for the first time ever.  Let him take a night off and grab a beer.
legendary
Activity: 1442
Merit: 1018
I didn't get paid for days because of these freaks, profiting on our back ...

We should be extremely careful with every major overhaul of the network ..

Our development cycles are going to start slowing down now that we have IX & DS out there and working properly.

I see you're starting optimizations on the wallet. Any idea on some outstanding features:

-Masternode Obfuscation
-Masternode Blinding (you mentioned about fragmenting inputs across multiple masternodes)
-2FA
member
Activity: 97
Merit: 10
How are they SUCKING IN damn near every block?


That is just horrible - OMG !!!!   ugh


Wondering the exact same thing.... anyone?

They don't grab all blocks, but their pool is approximatively 30% of actual hashrate on the DRK network - so when they found a block from time to time, instead of randomly electing a MN, they have modified the code to systematically promote their own.
legendary
Activity: 1442
Merit: 1018
How are they SUCKING IN damn near every block?


That is just horrible - OMG !!!!   ugh



Dude... they have 30% of the network hash. It's not rocket science.
legendary
Activity: 1176
Merit: 1036
Dash Developer
I didn't get paid for days because of these freaks, profiting on our back ...

We should be extremely careful with every major overhaul of the network ..

Our development cycles are going to start slowing down now that we have IX & DS out there and working properly.
hero member
Activity: 611
Merit: 500
How are they SUCKING IN damn near every block?


That is just horrible - OMG !!!!   ugh


Wondering the exact same thing.... anyone?

According to Evan they are intercepting payment messages in transit and changing the payee to their own masternode.
hero member
Activity: 525
Merit: 510
How are they SUCKING IN damn near every block?


That is just horrible - OMG !!!!   ugh


Wondering the exact same thing.... anyone?
full member
Activity: 163
Merit: 100
I didn't paid for days because of these freaks, profiting on our back ...

We should be extremely careful with every major overhaul of the network ..

Did ya help the testnet? otherwise you can't bitch :p
full member
Activity: 160
Merit: 100
I didn't get paid for days because of these freaks, profiting on our back ...

We should be extremely careful with every major overhaul of the network ..
full member
Activity: 163
Merit: 100
member
Activity: 78
Merit: 10
Im trying to get darkcoind to run on a PI 2 which seems to be going work. Only im compiling over n over and it takes pretty long on the Pi, even with 3 cores.

Can i just MAKE the one file i need?: Darkcoind?

And how?

check if this helps:
http://stackoverflow.com/questions/7815400/how-do-i-make-makefile-to-recompile-only-changed-files

or an alternative method is to try to cross compile it
http://stackoverflow.com/questions/19162072/installing-raspberry-pi-cross-compiler/19269715#19269715

edit: you can pull this docker image ready for raspberry pi cross compilation
https://registry.hub.docker.com/u/philipz/raspberry-pi-crosscompile/

cross compile darkcoin for rasperberry pi:

install docker in your computer
https://www.docker.com


docker pull philipz/raspberry-pi-crosscompile
docker run -ti philipz/raspberry-pi-crosscompile
cd /home
git clone https://github.com/darkcoin/darkcoin
sudo apt-get install dh-autoreconf
sudo apt-get install libdb++-dev
sudo apt-get install libboost-all-dev
sudo apt-get install libssl-dev
sudo apt-get install pkg-config


./autogen.sh
./configure --with-incompatible-bdb
make

cd src
scp darkcoind darkcoin-cli user@rasperberry_ip:/your_directory/

I do not own a rasperberry pi (yet) so I just compiled. Further tests needed
Next step is to create a docker image to make the above permanent.
On a new release you would only have to git pull and run commands from ./autogen.sh forward
Compilation is way faster then compiling in rasperberry pi

Turns out that philipz/raspberry-pi-crosscompile is for old PI. Doesnt work for PI2. Other ARM kernel?
No alternative found yet. In the middle of this mess i might as well browse the docker site for alternative containers.

for the moment im compiling on the pi 2 again Sad
Jump to: