[ANN][DGC] Digitalcoin | Multi-algo & Masternodes | Established 2013

[Walt Sobchak]

Going back to bed, while I collect orphans

[coinerd]

Yup, Yup, send charity.

D76DvJKwtwdMQxcZenRNdFgaqzY5SixML8

The 5 confirmed on generated coins is pretty rough it doesn't allow for much reorg, and once I'm "confirmed" I like to keep them.

[kimosan]

I don't understand how blocks can be accepted, immature coins show in wallet, then disappear a few seconds later? Does anybody feel like taking a bit of time to explain how this happens?  Thank ya kindly.

Due to faster workers getting block at same time?

[SylTi]

finally was able to build the qt wallet on linux from the second mega download link

pulling from github is easier  

oh, i see, code on github is complete now, it was not 20 min before, qt stuff was missing, ty OP

No, it's not :

Code:

syl@ubuntu:~/Documents/digitalcoinSource$ git pull
Already up-to-date.
syl@ubuntu:~/Documents/digitalcoinSource$ qmake
Project MESSAGE: Building with UPNP support
Project MESSAGE: Building with UPNP supportlrelease warning: Met no 'TRANSLATIONS' entry in project file '/home/syl/Documents/digitalcoinSource/digitalcoin-qt.pro'
WARNING: Failure to find: src/qt/bitcoin.cpp
WARNING: Failure to find: src/qt/bitcoingui.cpp
WARNING: Failure to find: src/qt/transactiontablemodel.cpp
WARNING: Failure to find: src/qt/addresstablemodel.cpp
WARNING: Failure to find: src/qt/optionsdialog.cpp
WARNING: Failure to find: src/qt/sendcoinsdialog.cpp

[Walt Sobchak]

Dammit, just got 15 coins, literally gone a second later.......

[rocketron]

Same happened me with wdc. Once diff goes up if you have decent hash power you will prevail with confirms. On wdc initially I got nothing for hour then all of a sudden I started hitting confirms every few min.

[erk]

Well somebody must be getting the coins if we are up over block 4000 in less than an hour.

[cryptohunter]

anyone getting a pool up for this?

[jonptl]

I don't understand how blocks can be accepted, immature coins show in wallet, then disappear a few seconds later? Does anybody feel like taking a bit of time to explain how this happens?  Thank ya kindly.

There are a few possible reasons.

1) Lag. When the wallet accepts the coin, it will immediately list as immature if the network doesn't say its an orphan. The moment the network tells the wallet that the block is an orphan, the wallet will simply remove it. Maybe there was a slight communication delay between the nodes and your wallet?

2) Mini-fork. Two (or more) miners solve the chain at the same time, faster than it can propogate the network. Other miners will side either fork, whichever reaches them first. When the two mini-forks propagate throughout the entire network, the longer one wins everything, the other loses. Could be that your semi-confirmed block was on the shorted block

Cheers!

Would like a block or two to feed mah orphans ty!

DSWScubhzoGyiWvJ2dmhh3uUoc6ruiaiT8

[derpcoin]

Wtf is going on with the blockchain? anyone else noticed it keeps going backwards or something weird anyway.

[willhash4food]

[coinerd]

I don't understand how blocks can be accepted, immature coins show in wallet, then disappear a few seconds later? Does anybody feel like taking a bit of time to explain how this happens?  Thank ya kindly.

The time it takes for the new blocks to propagate is more than the time it takes to find a block in a fresh blockchain with everyone trying to sync.

So, sometimes you find a block but it's too late, and you get orphaned. These don't usually show up in your wallet but sometimes...

when the clock chain is fresh,a nd propgating slowly across the p2p network you and/or a couple of your peers are sorking on a chain, when you come across a longer block chain on the network.

Faced with this, the client takes the longer blockchain as the "master" and changes to it.  So you lose any coins you had mined in the orphan chain during the reorg in most cases, since you weren't mining on the longer chain.

[kimosan]

I don't understand how blocks can be accepted, immature coins show in wallet, then disappear a few seconds later? Does anybody feel like taking a bit of time to explain how this happens?  Thank ya kindly.

There are a few possible reasons.

1) Lag. When the wallet accepts the coin, it will immediately list as immature if the network doesn't say its an orphan. The moment the network tells the wallet that the block is an orphan, the wallet will simply remove it. Maybe there was a slight communication delay between the nodes and your wallet?

2) Mini-fork. Two (or more) miners solve the chain at the same time, faster than it can propogate the network. Other miners will side either fork, whichever reaches them first. When the two mini-forks propagate throughout the entire network, the longer one wins everything, the other loses. Could be that your semi-confirmed block was on the shorted block

Cheers!

I don't understand how blocks can be accepted, immature coins show in wallet, then disappear a few seconds later? Does anybody feel like taking a bit of time to explain how this happens?  Thank ya kindly.

The time it takes for the new blocks to propagate is more than the time it takes to find a block in a fresh blockchain with everyone trying to sync.

So, sometimes you find a block but it's too late, and you get orphaned. These don't usually show up in your wallet but sometimes...

when the clock chain is fresh,a nd propgating slowly across the p2p network you and/or a couple of your peers are sorking on a chain, when you come across a longer block chain on the network.

Faced with this, the client takes the longer blockchain as the "master" and changes to it.  So you lose any coins you had mined in the orphan chain during the reorg in most cases, since you weren't mining on the longer chain.

Thank you.

[Aragami]

Wow willhash4food =o. Just wow.

[shaal]

Over 950 rejects, 300 accepted and  30 confirmed blocks, that's with 2khash and 85 connections.

[jonptl]

I don't understand how blocks can be accepted, immature coins show in wallet, then disappear a few seconds later? Does anybody feel like taking a bit of time to explain how this happens?  Thank ya kindly.

There are a few possible reasons.

1) Lag. When the wallet accepts the coin, it will immediately list as immature if the network doesn't say its an orphan. The moment the network tells the wallet that the block is an orphan, the wallet will simply remove it. Maybe there was a slight communication delay between the nodes and your wallet?

2) Mini-fork. Two (or more) miners solve the chain at the same time, faster than it can propogate the network. Other miners will side either fork, whichever reaches them first. When the two mini-forks propagate throughout the entire network, the longer one wins everything, the other loses. Could be that your semi-confirmed block was on the shorted block

Cheers!

Thank you!

Cheers!

No problem!


donations anyone?

DSWScubhzoGyiWvJ2dmhh3uUoc6ruiaiT8

Thanks!

[megablue]

I don't understand how blocks can be accepted, immature coins show in wallet, then disappear a few seconds later? Does anybody feel like taking a bit of time to explain how this happens?  Thank ya kindly.

Due to faster workers getting block at same time?

it depends on how fast your accepted block get propagated through the p2p network,

basically, you can view p2p as multiple segments of networks.

If you're at the lower hash power & higher latency end of the network, your accepted & confirmed block might got overwritten by the higher  hashpower & lower latency end of the network.

Cryptocoin (or Bitcoin based coin), work like rumor spreading, more people spread the same rumor, more people would believe it.

[stevenlam]

Ya, the orphans is nothing, Got alot block

[coinerd]

yeah thanks whoever's passing out a few coins.

[rbdrbd]

Code:

root@minermom:/opt/coins/digitalcoinSource/src# make -f makefile.unix 
/bin/sh ../share/genbuild.sh obj/build.h
../share/genbuild.sh: 33: ../share/genbuild.sh: cannot create obj/build.h: Directory nonexistent
../share/genbuild.sh: 34: ../share/genbuild.sh: cannot create obj/build.h: Directory nonexistent
make: *** [obj/build.h] Error 2

Right from a github pull right now. You'll need to do mkdir src/obj if building from there.

Source from a zipfile works fine, but not from github.