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

so far i can tell 7000 BTC is resting in these 7 wallets (each 1000 BTC) and the rest (170 BTC) has been mixed further down in smaller and smaller amounts..

1MgM7WMAVteJ3k4PqfyB9AKdaBnHvdxvdG
14kgEXiKWCN46BEHVNwYjyuohFN83Uc5Jt
1AFbZuU5PufViRhNCChw8br6beo6K78r2H
1KPNHv8mfMPNivHptAiwwytUVZmzovVF8f
1J4TJQKgh1phPMcsV8cbRkAhV2Q6V8wW25
1Q2MxBc9Zbe6A35mTcD5jyU8PMr4K6oqGC
1Muse5NL7nDPPHVreF2Gkq5wv5XLbC2Qtz

I had like 40% of my masternodes affected.
All ok now.

darkcoin is rising again, hopefully steaming towards 0.012 (although a big sell awaits us at 0.0115999)

Hacks all over the place! Take care!

https://exco.in/

bump

Bitcoindark vs darkcoin, who do you think wins and why? I prefer Darkcoin atm, still heitant to which anon crypto will surpass Bitcoin.

That is really kind of fun. I found a couple of forks, that ended up sending them to the same address here: https://blockchain.info/address/1GBaPdA22TvGGpbN3reNJc8q55618o6yHZ (It's only up to 5.5btc)



Edit: Also: https://blockchain.info/address/3KJGtFJ7XnXpimppxEw22PjKKZ53WPSUEb (looks like it's just sitting there, in an address with a 3, that's usually multisig right?) ~16 BTC

Edit 2: This one may be, but I kind of lost track, looking on blockchain.info with it https://blockchain.info/address/3G3VpVD6fJs1Usg52zB8LToy1pHzDHC4a2 (another 3 address, and showed up a few more times) ~143 BTC

Edit 3: https://blockchain.info/address/3MtoT3LeUHHdxdwCnH7kyecBHeqRJybLFD (another 3 address) ~179 BTC

yes i had the same problem. Solved! Thnx Evan.

I opened the ticket.. we'll see.. 

voilà

Yup - I had that too.

A -reindex did not help, only a full resync with deleted blocks/chainstate (or a bootstrap resync)

i had those two days ago .. they must have caused my MN to stop working back then. I remember someone else complaining about these errors back then .. i did a reindex with version .25 and had no problems anymore.

2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 22:33:07 ERROR: CheckProofOfWork() : nBits below minimum work
2015-02-13 22:33:07 ERROR: ReadBlockFromDisk : Errors in block header
2015-02-13 23:02:08

3 machine's debug logs scanned and checked, all good here, including one local masternode wallet 

I heard earlier there was a mined block of 2.6 darkcoin, is this connected, was it forked off or orphaned then?

A smartest question would be "Why Otho is so heavily interested in Darkcoin?"
Get you it ?

 

From what we can tell there's a uncommon condition on the network (seems to be about 1 in 10 clients), where some databases have became corrupt. Please check your logs for these messages:

--

2015-02-15 17:34:26 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
OR
2015-02-15 17:34:26 ERROR: ReadBlockFromDisk : Errors in block header

---

If you find entries like that delete ~/.darkcoin/blocks and chainstate, then resync from the bootstrap:

https://github.com/UdjinM6/darkcoin-bootstrap

Thanks 

Event:  Connectivity Loss

Date/Time: 12 February 2015, 15:30 GMT

At approximately 15:30 GMT Level(3) leaked routes to Vultr in Amsterdam. This event destabilized BGP for Level(3) and NTT causing Vultr to lose connectivity.

Our engineers have stabilized the network and we will be performing a maintenance next week to upgrade the routers to prevent this issue from reoccurring.

A credit for the outage has been automatically applied to your account. If you have any further questions, please open a support ticket from your customer portal.

-- Vultr Operations Team --

everything normal for me

Exchanges should write code that track stolen funds transferred to future wallets.  When a deposit is made to an exchange from one of those wallets, the exchange should automatically seize the deposit before it can be spent.  Thieves will be left to doing face to face transactions for liquidation of their stolen funds.  This will lead to capture at some point.

Another possible solution would be to build a feature into every wallet that would warn merchants and individuals that they received coins from a 'blacklist' address.  Any theft that can be proven and tracked to an address(es) can be added to a 'blacklist' database which is then broadcast to ever wallet.

If the community can figure out a way to make it unprofitable, we would see less problems from hackers.

Whaaaat? 

Just checked my AWS traffic seems normal...