Grifftech2k4
|
|
July 01, 2014, 12:37:40 AM |
|
bholzar? Any update man?
Thanks
|
|
|
|
bmwz520
Newbie
Offline
Activity: 49
Merit: 0
|
|
July 01, 2014, 01:59:46 AM |
|
bholzar? Any update man? bholzar? Any update man? bholzar? Any update man?
|
|
|
|
BadAss.Sx
Legendary
Offline
Activity: 1526
Merit: 1002
Bulletproof VPS/VPN/Email @ BadAss.Sx
|
|
July 01, 2014, 07:50:20 AM |
|
Network seems fine, multiple transactions confirmed sent and recieved to escrow, wallet staking - the bug may not be real. Some have rolled back to wallet version 1.0.9 and have had no problems since.
I also never noticed a bug in the confirmation process. I think it is bullshit made by original dev.
|
|
|
|
nzminer
Legendary
Offline
Activity: 1918
Merit: 1001
|
|
July 01, 2014, 08:59:15 AM |
|
Here's my latest concept logo:
|
NEM, THE SECURE, SCALABLE BLOCKCHAIN [NEM.IO] [T.ME/NEMRED]
|
|
|
|
lonely@thetop
|
|
July 01, 2014, 10:27:59 AM |
|
How is the wallet fix progressing? Perhaps a confirmation that no bug exists at all is all that is needed for exchanges to re-enable it?
|
|
|
|
Seldar
|
|
July 01, 2014, 11:00:40 AM |
|
How is the wallet fix progressing? Perhaps a confirmation that no bug exists at all is all that is needed for exchanges to re-enable it?
Yes, that would be the best news
|
Sorry for my bad english
|
|
|
souscoin
Newbie
Offline
Activity: 1
Merit: 0
|
|
July 01, 2014, 11:24:06 AM |
|
他能复活吗?
|
|
|
|
bestcoinever
|
|
July 01, 2014, 11:27:53 AM |
|
uh, stupid coin I have ever bought. Hope it will rebourn
|
|
|
|
ObscureBean
Legendary
Offline
Activity: 1148
Merit: 1000
|
|
July 01, 2014, 12:15:00 PM |
|
Some good news. Looks like Bittrex has re-enabled deposits and withdrawals for SC It's great that we can get the coins flowing again. Can't wait for bholzer's client update though Happy trading!!
|
|
|
|
dandruff1138
|
|
July 01, 2014, 12:34:36 PM |
|
Some good news. Looks like Bittrex has re-enabled deposits and withdrawals for SC It's great that we can get the coins flowing again. Can't wait for bholzer's client update though Happy trading!! I sold my coins at a loss just so I could get them off Bittrex literally yesterday haha... Oh well. Good luck everyone.
|
|
|
|
hamzatu
Member
Offline
Activity: 70
Merit: 10
|
|
July 01, 2014, 12:41:11 PM |
|
I don't find any bug. Tested all last night. Has anyone been able to reproduce it? Never had any problems with the wallet. I am out.
|
|
|
|
jaipagare
|
|
July 01, 2014, 01:52:57 PM |
|
Hey Guys,
This is great stuff to see, Bittrex enabled Silkcoin. I don't know; but I never had problems with my SC wallet SYNC and I do mine SC everyday for 12 hours and been earning good amount.
SC will push volume and price accelerator hard once "bholzar" comes back with flying colors.
|
|
|
|
yell4george
|
|
July 01, 2014, 03:58:15 PM |
|
bholzar? Any update man? bholzar? Any update man? bholzar? Any update man?
Patience man, bholzer is our only hope without him or another temporary dev we are dead. We have nothing to loose so let him work at his own pace. This is great stuff to see, Bittrex enabled Silkcoin. I don't know; but I never had problems with my SC wallet SYNC and I do mine SC everyday for 12 hours and been earning good amount.
SC will push volume and price accelerator hard once "bholzar" comes back with flying colors.
Sweet! I have setup the following wallets:
1SiLkm9SWbzQnqzyG1D2iW52sp9W3DB8q for BTC donations BQLUqZZHD2R9jFRqQp4gVrxJgAkcjzCb3u for SC donations
Sent 2500 silk to the escrow fund from my Bittrex account Development escrow http://explorer.silk-coin.com/address/BQLUqZZHD2R9jFRqQp4gVrxJgAkcjzCb3u
|
|
|
|
ontopicplease
|
|
July 01, 2014, 04:01:18 PM |
|
Did bholzer stop posting here?
|
|
|
|
kewlya
|
|
July 01, 2014, 04:16:51 PM |
|
Did bholzer stop posting here?
just sold everything, i lost 0.6 btc . bholzer is active everyday and posting on another threads but he not anwering here, i even messaged him 2days ago,asking him to give us an update here but he did not answer. just want to thank him because i bought after he opened this thread and i had hopes in him. illl recover my loss from another coin. good luck to you all but i suggest you to find a new dev.
|
|
|
|
Grifftech2k4
|
|
July 01, 2014, 04:25:07 PM |
|
bholzer will be back. He is a busy man and I am sure we will see him post soon.
|
|
|
|
arteleis
|
|
July 01, 2014, 04:38:17 PM |
|
Did bholzer stop posting here?
just sold everything, i lost 0.6 btc . bholzer is active everyday and posting on another threads but he not anwering here, i even messaged him 2days ago,asking him to give us an update here but he did not answer. just want to thank him because i bought after he opened this thread and i had hopes in him. illl recover my loss from another coin. good luck to you all but i suggest you to find a new dev. I dont think it would be in any interest of bholzer to post such lengthy heartfelt promises to the community and then just vanish completely. For now the rolled back client works fine, coins stake correctly, 0 confirm bug turned out to be just another layer of bs involving the scam we just experienced, development fund is growing everyday, there is a full development support team ready for action, bittrex just unfroze withdrawls and im sure polo and mintpal will be following suit.. things are looking good. If bholzer decides he is not doing what he said he would, then im sure a post will come soon, otherwise the assumption should be made that he is still working on the client. At this point the poll shows overwhingly that silkcoin should keep its original name and move forward as planned with a possible simple ticker change. All is well and progress is being made. Relax and buy silk while it is still cheap.
|
SILKCOIN - DARKSILK - SILKWEAVER - FREEDOM
|
|
|
ontopicplease
|
|
July 01, 2014, 04:50:31 PM |
|
Did bholzer stop posting here?
just sold everything, i lost 0.6 btc . bholzer is active everyday and posting on another threads but he not anwering here, i even messaged him 2days ago,asking him to give us an update here but he did not answer. just want to thank him because i bought after he opened this thread and i had hopes in him. illl recover my loss from another coin. good luck to you all but i suggest you to find a new dev. I dont think it would be in any interest of bholzer to post such lengthy heartfelt promises to the community and then just vanish completely. For now the rolled back client works fine, coins stake correctly, 0 confirm bug turned out to be just another layer of bs involving the scam we just experienced, development fund is growing everyday, there is a full development support team ready for action, bittrex just unfroze withdrawls and im sure polo and mintpal will be following suit.. things are looking good. If bholzer decides he is not doing what he said he would, then im sure a post will come soon, otherwise the assumption should be made that he is still working on the client. At this point the poll shows overwhingly that silkcoin should keep its original name and move forward as planned with a possible simple ticker change. All is well and progress is being made. Relax and buy silk while it is still cheap. aha, thanks
|
|
|
|
mbishop75
Newbie
Offline
Activity: 25
Merit: 0
|
|
July 01, 2014, 06:01:04 PM |
|
I just started looking at the wallet code since there is talk of the 0 confirmations not being an actual bug...and here is what I found.
TransactionRecord::updateStatus(const CWalletTx &wtx) is used to determine a transaction's status (../src/qt/transactionrecord.cpp line 156) by looking for the block the transaction belongs to. Next it determines maturity by calling CMerkleTx::GetBlocksToMaturity() (../src/main.cpp line 811), which in turn determines if the coins are already in your wallet (base or being staked) and as long as they are not, the next call to CMerkleTx::GetDepthInMainChain(CBlockIndex* &pindexRet) (../src/main.cpp line 802) determines chain depth. First it calls CMerkleTx::GetDepthInMainChainINTERNAL(CBlockIndex* &pindexRet) (../src/main.cpp line 777) to check the block we think the transaction is in and then we make sure the merkle branch connects to this block, and if it does not it returns '0', which results in a chain depth of '-1' which causes the updateStatus method to flag the transaction as 'Conflicted' (if (status.depth < 0) { status.status = TransactionStatus::Conflicted; }).
I'll check some other coins to compare methods, but at first glance this does not seem to be a real issue. Again, I just started looking at this a little while ago and maybe bholzer has some more insight to share since he is more familiar with the code base than I am.
|
|
|
|
|