Pages:
Author

Topic: [ANN][DUCK]DuckDuckCoin - Patched KGW - Trophy Coin 4 Hunters and Bird Watchers. - page 44. (Read 152357 times)

sr. member
Activity: 284
Merit: 250
I've been with this since the beginning. This was way worse of a launch than maxcoin for the record. I offered assistance but OP ignored it, posted warnings blah blah but he continued letting it go on. Either the people behind this coin are really stupid or they're in on it. Something's fishy in the pond. Glad I didn't invest. Enjoy your stinky marsh, feel free to join me on the moon



For the record, I am glad you didn't invest too!

Now stop stalking this thread. What have you got here -- like 30 posts? What are you, some weirdo or something?

Go to those threads that are going to join you on the "moon"! What pleasure are you taking from taunting other people? It's one thing to invest and then criticize, but what you're doing is just plain weird.

Now, as you post your (hopefully) parting shot at all of us stupid Duck investors, why don't you tell us where your "smart" money is going, so that we can all track your progress. Does that sound fair?

If we made a mistake by investing in Duckduckcoin, well, we are all grown up and can deal with it.

Now, leave us alone and get out of here.
hero member
Activity: 2086
Merit: 761
To boldly go where no rabbit has gone before...
Code:
git clone https://github.com/duckduckcoin/duckduckcoin
cd ~/duckduckcoin/src

make -f makefile.unix

results in

Code:
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/root/duckduckcoin/src -I/root/duckduckcoin/src/obj -I/usr/local/BerkeleyDB.4.8/include -DUSE_UPNP=0 -DUSE_IPV6=1 -I/root/duckduckcoin/src/leveldb/include -I/root/duckduckcoin/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/main.d -o obj/main.o main.cpp

main.cpp: In function ‘void BitcoinMiner(CWallet*)’:
main.cpp:4687:23: warning: unused variable ‘nBlockNonce’ [-Wunused-variable]

g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.

See for instructions.

make: *** [obj/main.o] Error 4

has anyone seen that g++: internal compiler error before?  

What to do?

i sent you a pm
member
Activity: 90
Merit: 10
I've been with this since the beginning. This was way worse of a launch than maxcoin for the record. I offered assistance but OP ignored it, posted warnings blah blah but he continued letting it go on. Either the people behind this coin are really stupid or they're in on it. Something's fishy in the pond. Glad I didn't invest. Enjoy your stinky marsh, feel free to join me on the moon
sr. member
Activity: 448
Merit: 250
Are u fucking kidding me?
Is anyone buying this shit?

At least they're not dropping 5 duck puns per sentence anymore.

Also, I like how their decision-making tree was limited to: STEAL FROM INVESTORS or STEAL FROM PREMINE.

So there was the dilemma, do we steal the DUCK from the community to give to him, or do we steal the DUCK from the investors to give to him.

One of the early investors, aka the negotiator, stepped up and offered his share of DUCK to give to the Genesis Egg Kidnapper in order to resolve the hostage situation without having to hard fork or issue a new blockchain.
hero member
Activity: 826
Merit: 1000
see my profile
Code:
git clone https://github.com/duckduckcoin/duckduckcoin
cd ~/duckduckcoin/src

make -f makefile.unix

results in

Code:
g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/root/duckduckcoin/src -I/root/duckduckcoin/src/obj -I/usr/local/BerkeleyDB.4.8/include -DUSE_UPNP=0 -DUSE_IPV6=1 -I/root/duckduckcoin/src/leveldb/include -I/root/duckduckcoin/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/main.d -o obj/main.o main.cpp

main.cpp: In function ‘void BitcoinMiner(CWallet*)’:
main.cpp:4687:23: warning: unused variable ‘nBlockNonce’ [-Wunused-variable]

g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.

See for instructions.

make: *** [obj/main.o] Error 4

has anyone seen that g++: internal compiler error before?  

What to do?
hero member
Activity: 588
Merit: 500
Will Bitcoin Rise Again to $60,000?
wts 1000 ducklings (0.00001) for 0.05 btc Smiley
newbie
Activity: 56
Merit: 0
鸭币-中国挖矿、交易信息交流QQ群 244547403
member
Activity: 84
Merit: 10
ATTN Genesis Block Investors - we will start sending DUCK tomorrow! It's been a long night.

Good to hear!
legendary
Activity: 1442
Merit: 1001
Wouldn't the software only accept a chain that builds on the correct early blocks? And woudn't those early blocks secure the premine to an account whose key was only known to the original developers? Are premines really this badly implemented in all the alt coins that have them?! These are utterly obvious precautions. It seems like this would only be possible if the premine was implemented with mind-boggling ineptitude.

yes and no... some of the things that you said are true, and yes this was a sub-optimal, perhaps lacking in eptitude launch - but we saved it and I'll explain more below.

we??  someone has already said that it was only 2btc and that amount was donated from someone else..meaning not a dev.
please explain...also how much duck was kept...rumored that it was .5

We wanted a fair launch with nobody on the team having unfair access to the sourcecode. We didn't want anyone getting any unfair mining advantage, the community can spot an instamine and that can taint the developers as untrustworthy. We didn't want to mine lots of blocks, we only mined and checkpointed to block 3 to secure the genesis block.

The coin bandit took advantage of a small window at launch, when a couple of essential things did not go as planned, to create a new chain with a new genesis block! The premine was secure on the original chain, but the original chain got replaced. The technical name for what transpired is referred to as an embarrassing clusterduck.

Immediately we scrambled a team of 16 for a 3 hour skype call, including pool owners, miners & other coin core devs. One of our developers was literally just out of the delivery room, his wife had just given birth when The Big Quack happened at ~9:30 PM EST.  He was able to take 30 mins to join the skype mastermind session on his cell phone outside of the hospital. Over all I'm proud of the way the entire team came together and worked on solving it. We did not plan for this, but we found a solution and worked well. This had never happened to us before, which is why we did not react as fast as we should have.

We acted slow because we did not want to shut everything down and delay the launch until tomorrow night because we would have lost momentum, which might kill the coin. This may have caused financial loss to the pool owners and miners that worked hard for the launch.

The other option was to use our sizeable hash power to relaunch right away, fork and take control of the blockchain with the miners & pool owners ... but we eventually decided against that as there would be competing blockchains that might never resolve itself, and some miners would have lost out on coins they mined.

While we were planning for a re-launch of the coin, taking down the repo and rebuilding the blockchain, syncing up with the pool owners to make a technical fix, some members of the marketing team took it upon themselves to negotiate with the premine pirate who reached out on IRC.

Our options were to solve it technically, which we were ready to do to save the coin, or give into his ransom demands. The problem with giving into the ransom demands is that the Crypto Catburgler wanted DUCKCOIN. We had to give him duckcoin from somewhere.

Keep in mind that our only premine compensation is 0.4% of the premine which is split evenly amongst THIRTY people. That's right there's 30 people on the team that have helped get this project off the ground, and will be providing infrastructure, resources, marketing, development, community support etc in the future.

The other 2.6% is for community giveaways and bounties. The final 17% was purchased by the investors. So there was the dilemma, do we steal the DUCK from the community to give to him, or do we steal the DUCK from the investors to give to him.

One of the early investors, aka the negotiator, stepped up and offered his share of DUCK to give to the Genesis Egg Kidnapper in order to resolve the hostage situation without having to hard fork or issue a new blockchain.

The amount that he made off with was 0.5 DUCK, which was equivalent to 2 BTC, which was send by this member for his share of The Big Quack. It's not a total loss for this member as we promised to buy him back 0.5 DUCK with the BTC that was raised once the coin is listed on an exchange. He asked us to do it this way rather than just sending him back the BTC because we will be helping provide liquidity to a miner or another investor by buying it off of the exchange for him.

There's a a couple of bugs left to squash, there's a transaction fee problem that we unfortunately missed, which is causing stuck transquacktions at the pools. This will require a client update hopefully in the next 12 hours. There's also an issue for some duck hunters trying to sync which requires fixing some configuration. This should be resolved soon.

We hope you enjoyed the entertainment, this should go down as The Great Genesis Egg Heist: The Best Failed Premine In History!

Are u fucking kidding me?
Is anyone buying this shit?

Yes. As one of the investors mentioned, I can vouch that this is indeed what happened. It's funny, but not that funny and I guess as investor I am buying this shit, er duck.
sr. member
Activity: 350
Merit: 250
Vires in Numeris
Wouldn't the software only accept a chain that builds on the correct early blocks? And woudn't those early blocks secure the premine to an account whose key was only known to the original developers? Are premines really this badly implemented in all the alt coins that have them?! These are utterly obvious precautions. It seems like this would only be possible if the premine was implemented with mind-boggling ineptitude.

yes and no... some of the things that you said are true, and yes this was a sub-optimal, perhaps lacking in eptitude launch - but we saved it and I'll explain more below.

we??  someone has already said that it was only 2btc and that amount was donated from someone else..meaning not a dev.
please explain...also how much duck was kept...rumored that it was .5

We wanted a fair launch with nobody on the team having unfair access to the sourcecode. We didn't want anyone getting any unfair mining advantage, the community can spot an instamine and that can taint the developers as untrustworthy. We didn't want to mine lots of blocks, we only mined and checkpointed to block 3 to secure the genesis block.

The coin bandit took advantage of a small window at launch, when a couple of essential things did not go as planned, to create a new chain with a new genesis block! The premine was secure on the original chain, but the original chain got replaced. The technical name for what transpired is referred to as an embarrassing clusterduck.

Immediately we scrambled a team of 16 for a 3 hour skype call, including pool owners, miners & other coin core devs. One of our developers was literally just out of the delivery room, his wife had just given birth when The Big Quack happened at ~9:30 PM EST.  He was able to take 30 mins to join the skype mastermind session on his cell phone outside of the hospital. Over all I'm proud of the way the entire team came together and worked on solving it. We did not plan for this, but we found a solution and worked well. This had never happened to us before, which is why we did not react as fast as we should have.

We acted slow because we did not want to shut everything down and delay the launch until tomorrow night because we would have lost momentum, which might kill the coin. This may have caused financial loss to the pool owners and miners that worked hard for the launch.

The other option was to use our sizeable hash power to relaunch right away, fork and take control of the blockchain with the miners & pool owners ... but we eventually decided against that as there would be competing blockchains that might never resolve itself, and some miners would have lost out on coins they mined.

While we were planning for a re-launch of the coin, taking down the repo and rebuilding the blockchain, syncing up with the pool owners to make a technical fix, some members of the marketing team took it upon themselves to negotiate with the premine pirate who reached out on IRC.

Our options were to solve it technically, which we were ready to do to save the coin, or give into his ransom demands. The problem with giving into the ransom demands is that the Crypto Catburgler wanted DUCKCOIN. We had to give him duckcoin from somewhere.

Keep in mind that our only premine compensation is 0.4% of the premine which is split evenly amongst THIRTY people. That's right there's 30 people on the team that have helped get this project off the ground, and will be providing infrastructure, resources, marketing, development, community support etc in the future.

The other 2.6% is for community giveaways and bounties. The final 17% was purchased by the investors. So there was the dilemma, do we steal the DUCK from the community to give to him, or do we steal the DUCK from the investors to give to him.

One of the early investors, aka the negotiator, stepped up and offered his share of DUCK to give to the Genesis Egg Kidnapper in order to resolve the hostage situation without having to hard fork or issue a new blockchain.

The amount that he made off with was 0.5 DUCK, which was equivalent to 2 BTC, which was send by this member for his share of The Big Quack. It's not a total loss for this member as we promised to buy him back 0.5 DUCK with the BTC that was raised once the coin is listed on an exchange. He asked us to do it this way rather than just sending him back the BTC because we will be helping provide liquidity to a miner or another investor by buying it off of the exchange for him.

There's a a couple of bugs left to squash, there's a transaction fee problem that we unfortunately missed, which is causing stuck transquacktions at the pools. This will require a client update hopefully in the next 12 hours. There's also an issue for some duck hunters trying to sync which requires fixing some configuration. This should be resolved soon.

We hope you enjoyed the entertainment, this should go down as The Great Genesis Egg Heist: The Best Failed Premine In History!

Are u fucking kidding me?
Is anyone buying this shit?
newbie
Activity: 53
Merit: 0
ATTN Genesis Block Investors - we will start sending DUCK tomorrow! It's been a long night.
newbie
Activity: 16
Merit: 0
Code:
addnode=162.213.254.217:12121
addnode=100.1.82.147:12121
addnode=66.172.11.82:12121
addnode=107.170.37.158:12121
addnode=69.90.132.64:12121
addnode=23.227.161.68:12121
addnode=69.90.132.181:12121
Wallet is still not synching.
full member
Activity: 196
Merit: 100
on bitember payouts working?
sr. member
Activity: 435
Merit: 250
Maybe mine out pool http://duck.scryptominers.com/ to http://duck.bitember.com/ pool

The pool http://duck.scryptominers.com is still disable payout.

Duckcoin be died from egg.
hero member
Activity: 588
Merit: 500
Will Bitcoin Rise Again to $60,000?
Super Duck Block soon! Which pool will get it?Smiley
sr. member
Activity: 322
Merit: 250
Transactoin fix is up, pull from git/download qt. Pools need to update.

yup , payouts still disabled at http://duck.scryptominers.com . I want my duckies in my duck wallet.

you should want your credit fees that are 2.2% rather than 1% Smiley
hero member
Activity: 770
Merit: 500
Transactoin fix is up, pull from git/download qt. Pools need to update.

yup , payouts still disabled at http://duck.scryptominers.com . I want my duckies in my duck wallet.
newbie
Activity: 53
Merit: 0
Transactoin fix is up, pull from git/download qt. Pools need to update.
member
Activity: 77
Merit: 10
hero member
Activity: 588
Merit: 500
Will Bitcoin Rise Again to $60,000?
So how did this coin turn out? Worth mining?

YES! JOIN POOL.


showing this on scrptominers pool
Quote
The DuckDuckCoin client is reporting transactions are too small to send.

All being resolved - your coins are safe - pools will upgrade with fix.

So everything I'm mining right now (200kh/s) I will get them once the pools are fixed?
Cause right now I'm not getting a single satoshi. (or is it duckling)
Pages:
Jump to: