[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[Ozziecoin]

Looking at pool hash stats, enforcement is becoming an irresistible itch!

[1714466853]

1714466853

[1714466853]

1714466853

[1714466853]

1714466853

[1714466853]

1714466853

[1714466853]

1714466853

[chaeplin]

Looking at pool hash stats, enforcement is becoming an irresistible itch!

+ 100000 duff

We should name those pool_unknown_xxx.

[camosoul]

Looking at pool hash stats, enforcement is becoming an irresistible itch!

On darkcointalk it was suggested to warn 24hr notice, then do partial turn-on of enforcement, a few hours each day...

Why? Hose these assholes! I don't even have an MN right now, waiting for multi-entry and some kind of obfuscation. But these pricks are flat out robbing MN operators. The unknown pools are increasing in number, deliberately because of it... They need to get forcibly fucked off the blockchain, if not kicked in the crotch until they bleed out their ears....

Worst, they're holding back DRK's development.

[Ozziecoin]

Interesting darkcoin stats from coingecko: http://www.coingecko.com/

[Ozziecoin]

Looking at pool hash stats, enforcement is becoming an irresistible itch!

+ 100000 duff

We should name those pool_unknown_xxx.

I think we can assume these guys are choosing not to update?

[darianc]

Code:

user@sv:~/doubleshot> grep Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe getblocktemplate/*
getblocktemplate/92938.txt:{"masternode_payments": true, "coinbaseaux": {"flags": "062f503253482f"}, "votes": [], "previousblockhash": "0000000000017494e6c1652d6c594d0c09416b9161278c99c33cc754160cb86b", "target": "00000000000a9f0c000000000000000000000000000000000000000000000000", "noncerange": "00000000ffffffff", "transactions": [{"hash": "6f64c89ecf62cfdaaa8329315355d89420b17602aa85262b235a70a50aba3533", "depends": [], "fee": 0, "data": "01000000011cf96a28f489636a3e015fd633abfbb1b0e09f9237bedbce54661a1119390db8000000006b48304502204e078c5ccb18842438f68d33a5ee602f900e0f4f772d462d17cc38f58a1e1775022100e16bbc033a70bc122a8a7ee86fae3abd6fb2a40693a427e7c532ca809e410b97012103a254d948ff70bbf19f7e7dd97001f11e3ae4869eae015b537f687d16bcb1d2abffffffff010065cd1d000000001976a91406fe1565a94d0691e74e34350f91b3be4959e71288ac00000000", "sigops": 1}], "mintime": 1403929596, "sigoplimit": 20000, "curtime": 1403931067, "height": 92938, "payee": "Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe", "version": 2, "coinbasevalue": 500000000, "sizelimit": 1000000, "enforce_masternode_payments": false, "mutable": ["time", "transactions", "prevblock"], "bits": "1b0a9f0c"}

How did you dump all getblocktemplate's for all blocks?

[tibolt]

i cant understand why dark and litecoin fallowing same price path?

[chaeplin]

Looking at pool hash stats, enforcement is becoming an irresistible itch!

On darkcointalk it was suggested to warn 24hr notice, then do partial turn-on of enforcement, a few hours each day...

Why? Hose these assholes! I don't even have an MN right now, waiting for multi-entry and some kind of obfuscation. But these pricks are flat out robbing MN operators. The unknown pools are increasing in number, deliberately because of it... They need to get forcibly fucked off the blockchain, if not kicked in the crotch until they bleed out their ears....

Worst, they're holding back DRK's development.

I think +a deterministic list of the “top 10 masternodes”+ is first.
https://darkcointalk.org/threads/rc4-development-and-path-going-forward.1604/

With 9.11.5 and 10.11.5, most part of inconsistency in NM list is gone.

But still some NMs have problem.

May be propagation delay or banning or setup problem or ..

This inconsistency will cause a problem.
1) Darksend masternode selection
2) Masternode payout








http://drk.poolhash.org/masternode.html

[chaeplin]

Code:

user@sv:~/doubleshot> grep Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe getblocktemplate/*
getblocktemplate/92938.txt:{"masternode_payments": true, "coinbaseaux": {"flags": "062f503253482f"}, "votes": [], "previousblockhash": "0000000000017494e6c1652d6c594d0c09416b9161278c99c33cc754160cb86b", "target": "00000000000a9f0c000000000000000000000000000000000000000000000000", "noncerange": "00000000ffffffff", "transactions": [{"hash": "6f64c89ecf62cfdaaa8329315355d89420b17602aa85262b235a70a50aba3533", "depends": [], "fee": 0, "data": "01000000011cf96a28f489636a3e015fd633abfbb1b0e09f9237bedbce54661a1119390db8000000006b48304502204e078c5ccb18842438f68d33a5ee602f900e0f4f772d462d17cc38f58a1e1775022100e16bbc033a70bc122a8a7ee86fae3abd6fb2a40693a427e7c532ca809e410b97012103a254d948ff70bbf19f7e7dd97001f11e3ae4869eae015b537f687d16bcb1d2abffffffff010065cd1d000000001976a91406fe1565a94d0691e74e34350f91b3be4959e71288ac00000000", "sigops": 1}], "mintime": 1403929596, "sigoplimit": 20000, "curtime": 1403931067, "height": 92938, "payee": "Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe", "version": 2, "coinbasevalue": 500000000, "sizelimit": 1000000, "enforce_masternode_payments": false, "mutable": ["time", "transactions", "prevblock"], "bits": "1b0a9f0c"}

How did you dump all getblocktemplate's for all blocks?

Use command option blocknotify.

Code:

# darkcoin.conf 
blocknotify=/home/user/scripts/blocks.py

[Ozziecoin]

I think +a deterministic list of the “top 10 masternodes”+ is first.
https://darkcointalk.org/threads/rc4-development-and-path-going-forward.1604/

With 9.11.5 and 10.11.5, most part of inconsistency in NM list is gone.

But still some NMs have problem.

May be propagation delay or banning or setup problem or ..

This inconsistency will cause a problem.
1) Darksend masternode selection
2) Masternode payout








http://drk.poolhash.org/masternode.html

Makes sense. Some kind of propagation/banning issue, as I experienced variances with exact same setup across all my monitored MNs.

[camosoul]

Looking at pool hash stats, enforcement is becoming an irresistible itch!

On darkcointalk it was suggested to warn 24hr notice, then do partial turn-on of enforcement, a few hours each day...

Why? Hose these assholes! I don't even have an MN right now, waiting for multi-entry and some kind of obfuscation. But these pricks are flat out robbing MN operators. The unknown pools are increasing in number, deliberately because of it... They need to get forcibly fucked off the blockchain, if not kicked in the crotch until they bleed out their ears....

Worst, they're holding back DRK's development.

I think +a deterministic list of the “top 10 masternodes”+ is first.
https://darkcointalk.org/threads/rc4-development-and-path-going-forward.1604/

With 9.11.5 and 10.11.5, most part of inconsistency in NM list is gone.

But still some NMs have problem.

May be propagation delay or banning or setup problem or ..

This inconsistency will cause a problem.
1) Darksend masternode selection
2) Masternode payout




http://drk.poolhash.org/masternode.html

Watching all this log data was the whole point of it, no? Moving on to RC4 when there's still something to fix here...

I don't mind silence, but the crossed signals are kinda annoying...

I guess it's possible to leave enforcement off into RC4, but we're starting to get sloppy...

[darianc]

Code:

user@sv:~/doubleshot> grep Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe getblocktemplate/*
getblocktemplate/92938.txt:{"masternode_payments": true, "coinbaseaux": {"flags": "062f503253482f"}, "votes": [], "previousblockhash": "0000000000017494e6c1652d6c594d0c09416b9161278c99c33cc754160cb86b", "target": "00000000000a9f0c000000000000000000000000000000000000000000000000", "noncerange": "00000000ffffffff", "transactions": [{"hash": "6f64c89ecf62cfdaaa8329315355d89420b17602aa85262b235a70a50aba3533", "depends": [], "fee": 0, "data": "01000000011cf96a28f489636a3e015fd633abfbb1b0e09f9237bedbce54661a1119390db8000000006b48304502204e078c5ccb18842438f68d33a5ee602f900e0f4f772d462d17cc38f58a1e1775022100e16bbc033a70bc122a8a7ee86fae3abd6fb2a40693a427e7c532ca809e410b97012103a254d948ff70bbf19f7e7dd97001f11e3ae4869eae015b537f687d16bcb1d2abffffffff010065cd1d000000001976a91406fe1565a94d0691e74e34350f91b3be4959e71288ac00000000", "sigops": 1}], "mintime": 1403929596, "sigoplimit": 20000, "curtime": 1403931067, "height": 92938, "payee": "Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe", "version": 2, "coinbasevalue": 500000000, "sizelimit": 1000000, "enforce_masternode_payments": false, "mutable": ["time", "transactions", "prevblock"], "bits": "1b0a9f0c"}

How did you dump all getblocktemplate's for all blocks?

Use command option blocknotify.

Code:

# darkcoin.conf 
blocknotify=/home/user/scripts/blocks.py

Works for new blocks, but not historical blocks. Any ideas?
Deleted directories blocks and chainstate expecting blocknotify invocation for all historical blocks. No joy.

[raze182]

Watching all this log data was the whole point of it, no? Moving on to RC4 when there's still something to fix here...

I don't mind silence, but the crossed signals are kinda annoying...

I guess it's possible to leave enforcement off into RC4, but we're starting to get sloppy...

6/26  8:31 pm    <jimbit> do we have a rough time frame for enforce?
6/26  8:32 pm    <evan82> RC4
6/26  8:33 pm    <evan82> I wrote the enforcement protocol and it's all there, but I need to rewrite the payment system

[Ozziecoin]

Watching all this log data was the whole point of it, no? Moving on to RC4 when there's still something to fix here...

I don't mind silence, but the crossed signals are kinda annoying...

I guess it's possible to leave enforcement off into RC4, but we're starting to get sloppy...

I think they are fixing with the new more robust voting system in RC4.

[TanteStefana2]

Watching all this log data was the whole point of it, no? Moving on to RC4 when there's still something to fix here...

I don't mind silence, but the crossed signals are kinda annoying...

I guess it's possible to leave enforcement off into RC4, but we're starting to get sloppy...

I'm quite sure Evan isn't leaving enforcement off until RC4.  I think this stupid problem (not to minimize the problem, just irritated that it happened, now)  With the official pool has taken Evan away from what he was doing and now he has to make sure everyone gets their coins.  17000 accounts is a lot of freakin accounts to audit!  Who knows how many days this will set things back    But it can't be helped.  I'm sure Evan and Kyle are doing the best they can.

Anyway, I honestly don't think the development team is getting sloppy, rather they've become way more cautious.  I think they strike a pretty good balance in the end.  Glad Elito gave us an update today and I'm sure we'll hear more soon.

I do agree that the speculation and silence is getting annoying, LOL.  It just takes time.  And though these miners are not paying out, we knew this would happen, but at least some coins are being paid out, and the issues are being logged so Evan can study any possible concerns and work on them.  This way masternode owners can get a little reward sometimes, rather than none

It's far from optimal, but it's only for a short while.  Hang in there everyone!

[chaeplin]

Code:

user@sv:~/doubleshot> grep Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe getblocktemplate/*
getblocktemplate/92938.txt:{"masternode_payments": true, "coinbaseaux": {"flags": "062f503253482f"}, "votes": [], "previousblockhash": "0000000000017494e6c1652d6c594d0c09416b9161278c99c33cc754160cb86b", "target": "00000000000a9f0c000000000000000000000000000000000000000000000000", "noncerange": "00000000ffffffff", "transactions": [{"hash": "6f64c89ecf62cfdaaa8329315355d89420b17602aa85262b235a70a50aba3533", "depends": [], "fee": 0, "data": "01000000011cf96a28f489636a3e015fd633abfbb1b0e09f9237bedbce54661a1119390db8000000006b48304502204e078c5ccb18842438f68d33a5ee602f900e0f4f772d462d17cc38f58a1e1775022100e16bbc033a70bc122a8a7ee86fae3abd6fb2a40693a427e7c532ca809e410b97012103a254d948ff70bbf19f7e7dd97001f11e3ae4869eae015b537f687d16bcb1d2abffffffff010065cd1d000000001976a91406fe1565a94d0691e74e34350f91b3be4959e71288ac00000000", "sigops": 1}], "mintime": 1403929596, "sigoplimit": 20000, "curtime": 1403931067, "height": 92938, "payee": "Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe", "version": 2, "coinbasevalue": 500000000, "sizelimit": 1000000, "enforce_masternode_payments": false, "mutable": ["time", "transactions", "prevblock"], "bits": "1b0a9f0c"}

How did you dump all getblocktemplate's for all blocks?

Use command option blocknotify.

Code:

# darkcoin.conf 
blocknotify=/home/user/scripts/blocks.py

Works for new blocks, but not historical blocks. Any ideas?
Deleted directories blocks and chainstate expecting blocknotify invocation for all historical blocks. No joy.

No way for historical blocks.

If result of getblocktemplate is same on all the clients, and all clients verify a block(which contains result of getblocktemplate),
getblock = getblocktemplate.

[chaeplin]

FYI:

Amazon Web Services

Dear Amazon EC2 Customer,

We are pleased to announce the immediate availability of Amazon EC2 T2 instances. T2 instances are a new low-cost, General Purpose instance type that are designed to provide a baseline level of CPU performance with the ability to burst above the baseline. With On-Demand Instance prices starting at $0.013 per hour ($9.50 per month), T2 instances are the lowest-cost Amazon EC2 instance option and are ideal for web servers, developer environments, and small databases.
T2 instances are for workloads that don't use the full CPU often or consistently, but occasionally need to burst to higher CPU performance. Many applications such as web servers, developer environments, and small databases don't need consistently high levels of CPU, but benefit significantly from having full access to very fast CPUs when they need them. T2 instances are engineered specifically for these use cases.

T2 instances are available in three sizes: t2.micro, t2.small, and t2.medium and work well in combination with Amazon EBS General Purpose (SSD) volumes for instance block storage.

Code:

Instance Type	vCPUs	Memory (GiB)
t2.micro	1	1
t2.small	1	2
t2.medium	2	4

T2 instances are backed by the latest Intel Xeon processors with clock speeds up to 3.3GHz during burst periods. If you are currently using T1 or M1 instances, we encourage you to try T2 instances for better performance for many applications at a lower cost.

T2 instances are available in the US East (N. Virginia), US West (Oregon), EU (Ireland), Asia Pacific (Singapore), Asia Pacific (Tokyo), Australia (Sydney), and Brazil (Sao Paulo) regions and are coming soon to all other AWS Regions. T2 instances can be purchased as On-Demand and Reserved Instances. To learn more about Amazon EC2 T2 instances, see the Amazon EC2 details page.

Sincerely,
The Amazon EC2 Team

[toknormal]

But still some NMs have problem.

May be propagation delay or banning or setup problem or ..

One of those masternodes is mine. What's the problem with them ?

[dotnetmin]

Code:

user@sv:~/doubleshot> grep Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe getblocktemplate/*
getblocktemplate/92938.txt:{"masternode_payments": true, "coinbaseaux": {"flags": "062f503253482f"}, "votes": [], "previousblockhash": "0000000000017494e6c1652d6c594d0c09416b9161278c99c33cc754160cb86b", "target": "00000000000a9f0c000000000000000000000000000000000000000000000000", "noncerange": "00000000ffffffff", "transactions": [{"hash": "6f64c89ecf62cfdaaa8329315355d89420b17602aa85262b235a70a50aba3533", "depends": [], "fee": 0, "data": "01000000011cf96a28f489636a3e015fd633abfbb1b0e09f9237bedbce54661a1119390db8000000006b48304502204e078c5ccb18842438f68d33a5ee602f900e0f4f772d462d17cc38f58a1e1775022100e16bbc033a70bc122a8a7ee86fae3abd6fb2a40693a427e7c532ca809e410b97012103a254d948ff70bbf19f7e7dd97001f11e3ae4869eae015b537f687d16bcb1d2abffffffff010065cd1d000000001976a91406fe1565a94d0691e74e34350f91b3be4959e71288ac00000000", "sigops": 1}], "mintime": 1403929596, "sigoplimit": 20000, "curtime": 1403931067, "height": 92938, "payee": "Xrr9QM87kBrkns5LPF4FMyNBiu8Syc6ZAe", "version": 2, "coinbasevalue": 500000000, "sizelimit": 1000000, "enforce_masternode_payments": false, "mutable": ["time", "transactions", "prevblock"], "bits": "1b0a9f0c"}

How did you dump all getblocktemplate's for all blocks?

Use command option blocknotify.

Code:

# darkcoin.conf 
blocknotify=/home/user/scripts/blocks.py

Works for new blocks, but not historical blocks. Any ideas?
Deleted directories blocks and chainstate expecting blocknotify invocation for all historical blocks. No joy.

could you please explain how this works and how to do to get these results ?

blocks.py is a script that runs when a new block is found ?
What to put into this script ?

Waiting now for more than 96h without a payment so it would be nice to know get voted but only issue pool is not paying

[georgem]

Guys
Coming home back from work and.... my wife has prepared me the supper.... who wouldn`t like to have something like that? LOL

Hm, could it be that your name is DIRK splawik and your wife is a little bit dyslexic sometimes?

If not, then you have an AWESOME wife.