[SDC] ShadowCash | Welcome to the UMBRA

[MantaMine]

Wallet is in maintenance on trex.  What's going on?  New release being implemented?

[rutherford]

extremistan: Not yet. Prob just maintenance, like yesterday.

[MantaMine]

extremistan: Not yet. Prob just maintenance, like yesterday.

wth is this "extremistan"?

[rutherford]

extremistan: It's my slack handle, posting on BCT through the slack channel #bitcointalk (via a bot).

[MantaMine]

extremistan: It's my slack handle, posting on BCT through the slack channel #bitcointalk (via a bot).

ok, got it.  Was wondering about that in other posts.

[.m.]

I was not able to sync the client v1.4.0.1, stuck at block 994543, 6 active connections.
What is wrong ?

The latest version is 1.4.0.3 you can get it from

https://shadowproject.io/en/gettingstarted


The quickest way to get everything sync'd up fast is by downloading the blockchain from https://github.com/shadowproject/blockchain



For your own security double check you are getting the correct official downloads, do not trust links posted/quoted on this forum.

Thanks, I did that before, trying again with v1.4.0.3, the result seems the same (downloaded 994543 - 99.61% of transaction history - and stuck there)
log :

Code:

ProcessBlock: ORPHAN BLOCK 795, prev=124ca113ab17cfb872bcfc1c761439fcc98c1e5d7e759646a53f9efec0442c38
Received mblk 1
ProcessBlock: ORPHAN BLOCK 796, prev=9d5891b20d393c100be34eb4a7fe532fd66fc14b947165cd46e71498a308c0f3
....

[systh]

I was not able to sync the client v1.4.0.1, stuck at block 994543, 6 active connections.
What is wrong ?

The latest version is 1.4.0.3 you can get it from

https://shadowproject.io/en/gettingstarted


The quickest way to get everything sync'd up fast is by downloading the blockchain from https://github.com/shadowproject/blockchain



For your own security double check you are getting the correct official downloads, do not trust links posted/quoted on this forum.

Thanks, I did that before, trying again with v1.4.0.3, the result seems the same (downloaded 994543 - 99.61% of transaction history - and stuck there)
log :

Code:

ProcessBlock: ORPHAN BLOCK 795, prev=124ca113ab17cfb872bcfc1c761439fcc98c1e5d7e759646a53f9efec0442c38
Received mblk 1
ProcessBlock: ORPHAN BLOCK 796, prev=9d5891b20d393c100be34eb4a7fe532fd66fc14b947165cd46e71498a308c0f3
....

We have some tutorials on the website that might help:
→ Stuck on block X?

(the rewindchain command should do the trick alone)

[dasource]

Thanks, I did that before, trying again with v1.4.0.3, the result seems the same (downloaded 994543 - 99.61% of transaction history - and stuck there)
log :

Code:

ProcessBlock: ORPHAN BLOCK 795, prev=124ca113ab17cfb872bcfc1c761439fcc98c1e5d7e759646a53f9efec0442c38
Received mblk 1
ProcessBlock: ORPHAN BLOCK 796, prev=9d5891b20d393c100be34eb4a7fe532fd66fc14b947165cd46e71498a308c0f3
....

Did you try using the https://github.com/shadowproject/blockchain method? It'll get you back onto the main chain.

[dasource]

I've not been able to find answers to these questions so apologies if they have been asked before.
1. If all the outputs of a transaction are zero knowledge how does the network or miner know what the fees will be?
2. Is there any way a shadowcash user can provide the ability for a third party to see their anonymous account activity, e.g. like a Monero "view key", without exposing their private key?
3. Is there any way to enforce instant transactions on the network like Dash? Or does shadow cash rely on the normal method of confirmations until statistical certainty on non-reversibility (due to chain reorganisation) reaches a certain threshold.
4. Why did the blockchain switch from PoW to PoS? Was this to seed an initial distribution of coins?
5. Where can I read up on the specific type of PoW used?
6. Where can I read up on the decentralised market protocol?

1. Blocks and Fees are not obfuscated.
2. Yes Shadow also has a View Key.
3. Short answer is no support for instant transactions, we prefer the statistical certainty on non-reversibility of tradition confirmations.
4. Correct, whilst I was not around during the launch my understanding is the Core Developer wanted to distribute the coin without doing a ICO. ~2 years ago mining was a hot subject so you can expect it got a fairly good share of mining power and has since been historically low in price allowing good distribution of supply.
5. https://doc.shadowproject.io/#network-consensus
6. This has not been released to the public but we have done several Q&A sessions to answer any questions.

Please feel free to drop into Slack where we hangout daily (I generally don't use BCT much anymore)

[dickwhite]

extremistan: And Satoshi wouldn't be on the most wanted list for developing Bitcoin, the only reason he would be "wanted" is for tax purposes... 

Yeah, them capital gains. Bet they're licking their lips.

[Axente]

It looks like support is buidling for 0.0003 btc and I expect it wont get lower then this after it.

[.m.]

I feel like an idiot, but I really was not able to move.

Used
https://shadowproject.io/en/tutorials/stuck-on-block-x
and
https://shadowproject.io/en/tutorials/fast-sync-blockchain
and the latest Linux64 client
v1.4.0.3

btw
http://shadow.cash/downloads/latest/linux64
says
Error 521 Ray ID: 2dda1a7a87253dd8 • 2016-09-05 13:42:15 UTC
Web server is down


and deleted EVERYTHING (except wallet and inf file) and unpacked blockchain.

The result is still the same : Downloaded xxxxx which is 99.xx% and stuck.

Code:

ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(9e6f1e3ffb, 1), 1472797488) for block 70c31d54dc542dcacde3
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(4e3b5e90aa, 1), 1472797504) for block 86229aed9decf8c3b8fd
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(247ddd001d, 1), 1472797536) for block bbd2e12a811b0201da4c
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(2ea073a558, 1), 1472797616) for block 9e387fee6be9903fe831
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(38eff4b4fb, 1), 1472797632) for block 42ef87baa74ee880e290
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(3ee729753a, 1), 1472797808) for block 2196cb38507f53336a66
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(077fdfd899, 1), 1472797840) for block e9c2d1a04e56a6291699
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(5018997451, 1), 1472798064) for block d8cdddab4f6e0b263e7e
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(a0d8a34578, 1), 1472798080) for block 23c01fcb4c7a362fae79
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(dbc9805e18, 1), 1472798112) for block ae3a62b2bd0636009d28
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(ab2c8345a7, 1), 1472798144) for block 6dc5569930faa47637fe
Added 5 addresses from 46.28.206.146: 17 tried, 700 new
Received mblk 1
ProcessBlock: ORPHAN BLOCK 449, prev=12706683871f1638d91fd4b5290fbf85240e423b33f7514822608b1732a7f923
Received mblk 1
ProcessBlock: ORPHAN BLOCK 450, prev=1af84bf37b2d31d55c41ff71db9026637ceb7c8a7d67640dce30f47a6260b813
Received mblk 1
ProcessBlock: ORPHAN BLOCK 451, prev=987eb2d3929b97c0f1c080977daa757d25e8e2bd1ac70f3ac6fa3d3f73d81fdc
ERROR: FetchInputs() : c1a9bcd104b6c20a5b8a2b1629e2de8e0827b64a85bb44b33fb531585f921e9c mempool Tx prev not found aa3bad500aca08f54763ca215cd05aea12cbcf084f9dd2de0f412e12f0800fb2
stored orphan tx c1a9bcd104 (mapsz 18)
Received mblk 1
ProcessBlock: ORPHAN BLOCK 452, prev=0961bb11a48b0ef667f6053f9cf47b9dba7feccf1b314a448e0671d25191964d
Received mblk 1
ProcessBlock: ORPHAN BLOCK 453, prev=215841d77bcdf49c579c605e16d6862dcb60923a09a8d8ad19c1bda93886a263
Received mblk 1
ProcessBlock: ORPHAN BLOCK 454, prev=ac831159b58193c11a608b1f86b8a8cdf17159a1164f000bd2df55876e15416a
Received mblk 1
ProcessBlock: ORPHAN BLOCK 455, prev=049279ff13c6aa99c796375e659774662b519bc77d7f8cd96e8b98106f68efc7
ERROR: FetchInputs() : 8e5de439625a56cacd9e0d08e95b881967723d2e18bb2556df057381b470029d mempool Tx prev not found 36c3cabf380b30443d14ec28ea5eb95853f3e470bdb8eaca9a88390aa7fc1424
stored orphan tx 8e5de43962 (mapsz 19)
ERROR: FetchInputs() : 51cba428f8aa6a8621b486ed8b19e0868b20d6f9714e80f67a2a7ae9d82cd0d3 mempool Tx prev not found 70b11f9d4cd4244ecd5f92ea143ca3268d144be1c0dbc1fbb16c8581ca2983e4
stored orphan tx 51cba428f8 (mapsz 20)
Received mblk 1
ProcessBlock: ORPHAN BLOCK 456, prev=d3e45c7cbf5e09785c417d4377b26e0a5d2495fb4d9bf618b194acb46ec5975d
Received mblk 1
ProcessBlock: ORPHAN BLOCK 457, prev=1726758c56e13ba99418b76f80f463beabf7d33c79ad8b82b57e29ab67f72459
Received mblk 1
ProcessBlock: ORPHAN BLOCK 458, prev=7324d1ef25efa15d6107c8b0e33856d82d1af96558fdceae4c1bbe08bfdb6069
Received mblk 1
ProcessBlock: ORPHAN BLOCK 459, prev=f3b0efb75cf278f15a18d4b83a31e4a10e9f4a9d1f5975165eb094da17d02004
Received mblk 1
ProcessBlock: ORPHAN BLOCK 460, prev=f3b0efb75cf278f15a18d4b83a31e4a10e9f4a9d1f5975165eb094da17d02004
Received mblk 1
ProcessBlock: ORPHAN BLOCK 461, prev=b32181304d586b8f9494b80ed79a3312b19ddd667789e5a283e597c52ad88396

really nobody knows what the problem may be ?

[dickwhite]

I feel like an idiot, but I really was not able to move.

Used
https://shadowproject.io/en/tutorials/stuck-on-block-x
and
https://shadowproject.io/en/tutorials/fast-sync-blockchain
and the latest Linux64 client
v1.4.0.3

btw
http://shadow.cash/downloads/latest/linux64
says
Error 521 Ray ID: 2dda1a7a87253dd8 • 2016-09-05 13:42:15 UTC
Web server is down


and deleted EVERYTHING (except wallet and inf file) and unpacked blockchain.

The result is still the same : Downloaded xxxxx which is 99.xx% and stuck.


really nobody knows what the problem may be ?

Have you tried building the client from source?

[nasituygun]

It looks like support is buidling for 0.0003 btc and I expect it wont get lower then this after it.

0.003 is still a joke. SDC barely has 10m cap. We have a lot of way too go up. This is just a lol phase to me. The best part of this rise is that people actually realized what shadow is and how valuable is the project.

[cryptospreader]

It looks like support is buidling for 0.0003 btc and I expect it wont get lower then this after it.

0.003 is still a joke. SDC barely has 10m cap. We have a lot of way too go up. This is just a lol phase to me. The best part of this rise is that people actually realized what shadow is and how valuable is the project.

It is a very big rise for me. I don't expect this much high. What is the reason behind this rise? I don't know the exact thing for the price increase.

[.m.]

Sorry everybody for wasting your time.
The client just needed an hour or so. It is synced now.

A little warning that it may look like stuck would avoid my "problem".

Thanks everybody for help and patience !

[Axente]

It looks like support is buidling for 0.0003 btc and I expect it wont get lower then this after it.

0.003 is still a joke. SDC barely has 10m cap. We have a lot of way too go up. This is just a lol phase to me. The best part of this rise is that people actually realized what shadow is and how valuable is the project.

It is a very big rise for me. I don't expect this much high. What is the reason behind this rise? I don't know the exact thing for the price increase.

I expect the announcement that will happen in 22 hours or so.

[vtr99]

It looks like support is buidling for 0.0003 btc and I expect it wont get lower then this after it.

0.003 is still a joke. SDC barely has 10m cap. We have a lot of way too go up. This is just a lol phase to me. The best part of this rise is that people actually realized what shadow is and how valuable is the project.

It is a very big rise for me. I don't expect this much high. What is the reason behind this rise? I don't know the exact thing for the price increase.

Realistically our market cap should be 20x what it currently is. The reason is that people are finally doing their homework and discovering what SDC has to offer.

Statistically there are about half as many SDC as there are XMR. SDC offers superior technology, privacy, features, and ease of use.

I think it's safe to say without any hype that SDC's market cap is close to the bottom compared to where we are headed. 

[fearcoka]

Quick question. First time I have had this error. VerifyRingSignatureAB()failed  when sending Shadow to SDC

how do i fix this? thanks

[Kewde]

Quick question. First time I have had this error. VerifyRingSignatureAB()failed  when sending Shadow to SDC

how do i fix this? thanks

What version are you on?
Join slack if you want faster help.
Keep your debug files!