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

[mahowi]

AFAIK Christian didn't implement X11 to cudaminer and won't do this in the near future. Or did I miss something?

Isn't it open source?

Bounty would equally apply to any miner running on nvidia as per the stated hashrates. Doesn't have to be a cudaminer fork.

Ah, ok. I thought somebody is working on a cudaminer fork and I missed it. Would be interesting because the new NVidia Maxwell GPUs are very power efficient.

[1715016799]

1715016799

[1715016799]

1715016799

[1715016799]

1715016799

[1715016799]

1715016799

[LimLims]

"52.24   Professionally produced infographic of darksend, reference: http://imgur.com/GXPvNgn"

Sorry but that does not look professionally produced. Bounty should not have been granted. Judgement of bounty owner is critical here and seems poor.

That's just the reference infographic I threw together as a starting point. This bounty hasn't been claimed yet, although there was a strong contender posted earlier.

[sharkbyte093]

https://twitter.com/moolah_io/status/444085771193303040

#darkcoin currently being pushed to the (Moolah) platform...



P.S. follow the Darkcoin google+ page!
https://plus.google.com/u/0/b/113501121429723618585/113501121429723618585/posts

Wouldn't following Darkcoin on Google, and revealing your identity defeat the purpose of Darkcoin?

No? How would it?

I thought the purpose of Darkcoin was to be anonymous. Going on Google+ and following it, would thereby sacrifice that anonymity in the sense that your real identity would be linked to your support of Darkcoin. Obviously it wouldn't link transactions on the blockchain to you, but still.

oh come on...you sacrifice you anonymity by posting here without a proxy, by mining, by retweeting, by facebook by everything...
Obviously you dont have to post your darkcoin wallet address on google+

your transactions are the ones that you may want to be anonymous. not your support for an anonymous coin thats political and your right to support it.

Just saying, if people want to stay as anonymous as possible, it's something to think about. Thankfully I don't use facebook or twitter, so that's not an issue for me.

are you using a proxy for bitcointalk? i am just curious...

Nope. Then again I don't have my face and all my personal information in my bitcointalk profile for all to see.

[chaeplin]

Why are the lower hashrate miners receiving larger payouts when they've been mining for the same amount of time on the same block?

P2Pool share period is 24 hours. Not between blocks.

Use site graph.

Which one do you mind ?

Probaly lower hashrate miners have been mined more than 24 hours.

[GreekBitcoin]

https://twitter.com/moolah_io/status/444085771193303040

#darkcoin currently being pushed to the (Moolah) platform...



P.S. follow the Darkcoin google+ page!
https://plus.google.com/u/0/b/113501121429723618585/113501121429723618585/posts

Wouldn't following Darkcoin on Google, and revealing your identity defeat the purpose of Darkcoin?

No? How would it?

I thought the purpose of Darkcoin was to be anonymous. Going on Google+ and following it, would thereby sacrifice that anonymity in the sense that your real identity would be linked to your support of Darkcoin. Obviously it wouldn't link transactions on the blockchain to you, but still.

oh come on...you sacrifice you anonymity by posting here without a proxy, by mining, by retweeting, by facebook by everything...
Obviously you dont have to post your darkcoin wallet address on google+

your transactions are the ones that you may want to be anonymous. not your support for an anonymous coin thats political and your right to support it.

Just saying, if people want to stay as anonymous as possible, it's something to think about. Thankfully I don't use facebook or twitter, so that's not an issue for me.

are you using a proxy for bitcointalk? i am just curious...

Nope. Then again I don't have my face and all my personal information in my profile.

you dont need to have in order for them to find you

[sharkbyte093]

https://twitter.com/moolah_io/status/444085771193303040

#darkcoin currently being pushed to the (Moolah) platform...



P.S. follow the Darkcoin google+ page!
https://plus.google.com/u/0/b/113501121429723618585/113501121429723618585/posts

Wouldn't following Darkcoin on Google, and revealing your identity defeat the purpose of Darkcoin?

No? How would it?

I thought the purpose of Darkcoin was to be anonymous. Going on Google+ and following it, would thereby sacrifice that anonymity in the sense that your real identity would be linked to your support of Darkcoin. Obviously it wouldn't link transactions on the blockchain to you, but still.

oh come on...you sacrifice you anonymity by posting here without a proxy, by mining, by retweeting, by facebook by everything...
Obviously you dont have to post your darkcoin wallet address on google+

your transactions are the ones that you may want to be anonymous. not your support for an anonymous coin thats political and your right to support it.

Just saying, if people want to stay as anonymous as possible, it's something to think about. Thankfully I don't use facebook or twitter, so that's not an issue for me.

are you using a proxy for bitcointalk? i am just curious...

Nope. Then again I don't have my face and all my personal information in my profile.

you dont need to have in order for them to find you

Depends on who you perceive as 'them.' There is a certain degree to which one can reasonably protect themselves short of paranoia.

[chaeplin]

Why are the lower hashrate miners receiving larger payouts when they've been mining for the same amount of time on the same block?

[Dude5082]

P2Pool share period is 24 hours. Not between blocks.

Use site graph.

Which one do you mind ?

Probaly lower hashrate miners have been mined more than 24 hours.

Mining on http://207.12.89.180:7903/static/

Also, is there a way to check to see the number of shares that are credited to your address?

[chaeplin]

P2Pool share period is 24 hours. Not between blocks.

Use site graph.

Which one do you mind ?

Probaly lower hashrate miners have been mined more than 24 hours.

Mining on http://207.12.89.180:7903/static/

Also, is there a way to check to see the number of shares that are credited to your address?

Use classic info link http://207.12.89.180:7903/static/classic/
bottom current payout.
And top there graph link http://207.12.89.180:7903/static/classic/graphs.html?Day

or really classic cmd
http://207.12.89.180:7903/current_payouts

[HooDude]

Edited: missed previous post.

[anonymousxx1503]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

Mining the Dark Gravity Core

Dark Well




or DGW for dark gravity well.  That's awesome btw eduffield.

[Schwede65]

why can't i login at the official pool of the OP?

1. message: Token expired, please try again
2. message: Unable to login: Account locked.

i have had no e-mail to unlock my account...

whats going on here - this is not a good way to distribute the hashrate to other pools...

Edit: i will try the lottery-pool - this seems to work

[bitcoindirect]

Here is the direct Reddit link where I will have most of the updates.

http://www.reddit.com/r/Bitcoin/comments/207014/penguin_books_penguin_foundation_charitable

Thanks again to all those who are helping these kids who don't have the opportunity to have books like we do, and the Penguin Foundation!

Charity Box's so far:
BTC-0.03122
LTC-0.00
DOGE-1,005.60
PENG-200,000.00
AURORA-0.00
FLAP-0.00
RIPPLE-0.00
KLONDIKE-0.00
ULTRA-0.00
EARTH-0.00
DARK-0.00
LEAF-0.00
MINT-0.00
BLACK-0.00

"Hey everyone!

So for those of you who know me either from Reddit or Bitcointalk, I am the guy who has a glass etching business with my girl that started doing glass etched Bitcoin Glasses and have been an active member in the crypto currency world.

Today, I want to inform you that with being a big part in the Penguincoin community, our community has setup with two charitable organizations for whom we are going to work directly with on helping their cause.

In doing so, I personally have promised to the community that ANY SALE made with our glass etching at https://www.etsy.com/shop/pixskull, we will PERSONALLY DONATE 25% off the sale to our donation wallet, which will get divided between the two charitites.  By tomorrow we will post an article that http://cryptoarticles.com

Our first charity we have been in communication with is Penguin Books and the Pearson Foundation.  

Who is known for such books as:*
*Of Mice & Men
*Jane Eyre
*Pride and Prejudice
*The Odyssey
*Hamlet
*Moby Dick

They're charity is http://wegivebooks.org.  We give books donates books to children less fortunate and tries to inspire caregivers and educators the chance to inspire children to become lifelong readers and lifelong givers.

For every $5 dollars donated, they will send two more bookbooks to their charity partners.

The other organization we have communicated with and are making promises to is **The Penguin Foundation**
http://penguinfoundation.org.au

The Penguin Foundation was established to protect and preserve one of Australia's most important natural assets - the little penguin.

The Penguin Foundation aims to provide a dedicated source of funding to support little penguin conservation projects on Phillip Island. These include little penguin rescue and rehabilitation in the event of a man-made disaster; building new little penguin nesting areas; monitoring little penguin health and behaviour; protecting the little penguins' natural environment; and contributing funding to the vital Phillip Island Nature Parks Wildlife Clinic on Phillip Island. Since its establishment in 2006, the Penguin Foundation has raised over $1.5 million.

Our Goal for the penguin foundation is to be a sponsor, but we will have an adopted penguin as well.  And with the current news articles about the Penguin Foundations need, such as http://www.chron.com/news/nation-world/article/Knit-a-penguin-sweater-to-help-them-survive-an-5293898.php We felt the need to reach out directly to them.

Any and all donations are beneficial to our cause and the meaning of what Penguincoin is trying to achieve, and what a positive outlook the crypto-currency world will achieve from this and it's ability to do more positive for the world then negative.

Thank you for any help, and please spread the word.  I will gladly update everyone on here, as well as on bitcointalk about the updates and donations we have been receiving, as well as the updates on our penguins and books that have been donated.

Sincerely,

Rich Ferry

Donations are accepted in any of these forms so far.  We will gladly give other currencies the option to donate on request.

*BTC-1MEnRWb5EWoiQm32p3aF78MkBAPheqAvZQ
*LTC-LSAgpiArAQCe8jyUrHZ7vG3vyQv4xwY5GQ
*PENG-pDFQzCdyeqKdzP7LRgAc2G21LQJKzHKXQz
*DOGE-DMEAqJBRkPL38A5MPwmfanDx98sWen6Kgu
*RIPPLE-rPYpuvDH7sXBDF2hEYC1E7Ko2sUEKqYetG
*AURORACOIN-ASZfre39f9Po8ndukHznRzo2y18MF2tift
*FLAP-FFUZk1m7gohkbNCK42YjdZA44FuJ5W3tDe
*KLONDIKE-L6zvYLLeVjwFgWN7cpJb3EMfwjJJXenx1J
*ULTRA-UjkkNHz3X9VrVw1t3z6gA74nhg31ZBKHip
*EARTH-epYihNy9sNmLBHo8HUaSKoVsrgaY2c9LvQ
*DARK-XhgrwWsfE3pGcy6sBqcMTSwvegnqQQGjMF
*LEAF-fHxCcHMzRFjrythxRHhZmM2Xz2E4Q7PtV6
*MINT-MXQcJJCmkFTByLuUYqgatVKBuH3FPNmbcn
*BLACK-B4s9FErujyGYrp4VuR5u94vVBwytoTL9XS

[bumaga]

I can make *Russian language translation of website

Send me link to the text or new website

[jdp527]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

BlackHole

[jdp527]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

BlackHole

SINGULARITY

[Kai Proctor]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

BlackHole

I think that "Dark" must be in the name, it's better for the brand.

[darkproton]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

BlackHole

I think that "Dark" must be in the name, it's better for the brand.

DuffDarkField
DDF

[coins101]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

BlackHole

I think that "Dark" must be in the name, it's better for the brand.

DuffDarkField
DDF

Evans Dark Well

[Kai Proctor]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

BlackHole

I think that "Dark" must be in the name, it's better for the brand.

DuffDarkField
DDF

Evans Dark Well

Dark Field