[SDC] ShadowCash | Welcome to the UMBRA

[dbt1033]

^what he said

MAKE NO MISTAKE
Shadow is the most exciting thing in this space right now.

https://www.youtube.com/watch?v=3INbCnEfZq4

It really is incredible that these things are REAL and exist right NOW.

I think people are finally starting to realize what an absolute steal SDC is at current price levels.

Shadow technology is years ahead of the next guy.

[child_harold]

^ https://youtu.be/3INbCnEfZq4?t=2m32s

comes in at 2m 32secs…

Only a short presentation. Well worth watching.
Gavin discusses NIZKPs (which Shadow uses) as a possibility for BitCoin. NIZKPs (non-nteractive zero knowledge proofs) had not yet been discovered in 2009 when Satoshi created bitcoin. Gavin speaks to the possible future integration into BTC, an extraordinary feat which Shadow has already accomplished.

[fearcoka]

Mmmm Shadow rising, bitcoin rising. This is gonna be one heck of a moon

Keep up the great work everyone! Its only the start!

[Cornett]

Mmmm Shadow rising, bitcoin rising. This is gonna be one heck of a moon

Keep up the great work everyone! Its only the start!

I predict that when a m.wallet will be presented, the price will rise to 40ksat again. SDC feels extremely bullish

[bangomatic]

I sold all my shitcoins today and bought more SDC.

[Cornett]

Guys why we haven't shadowcash.info and shadowchain.info links on the website ?

[LiteBit]

With all this name changing talk around the crypto-spheres there is one I'd like to see 

[jokowi]

I predict in the next 12 months it will be somewhere between $1 and $10,000   

WOOWWWWW..very brave,so how about Bitcoin about 12 month later??$0.1..?

[fearcoka]

I sold all my shitcoins today and bought more SDC.

Good move, im selling my remaining Darks this week In hope we don't pump too fast :p

[Shadow_Runner]

I wish I had some BTC to buy SDC now... 
Hope will sell some alt. coins a bit later, don't pump very high! 

[LucyLovesCrypto]

Is the dev team working on the issue of SDC>Shadow>Shadow>SDC conversion time rules?

If someone converts SDC to Shadow, sends it to another Shadow address and that person converts it all back into SDC right away, the anonymous nature of Shadow>Shadow wont matter much. Anyone can see on the blockchain that one SDC address was debited by a certain amount and shortly thereafter another SDC address receives an almost identical SDC amount (after the Shadow was converted back into SDC) and thereby "link" the transactions with basic logic. Yes this would not be proof of the transaction because they are not directly connected on the blockchain, but common sense links them quite easily.

One possible fix could be to set minimum (and perhaps random) time limits before a Shadow transaction can be sent after a SDC>Shadow conversion and between the time a Shadow transaction is received before it can be converted back into SDC

Can the dev team comment on this? It seems like an easy way to improve practical anonymity on the network

[Blazin604]

Is the dev team working on the issue of SDC>Shadow>Shadow>SDC conversion time rules?

If someone converts SDC to Shadow, sends it to another Shadow address and that person converts it all back into SDC right away, the anonymous nature of Shadow>Shadow wont matter much. Anyone can see on the blockchain that one SDC address was debited by a certain amount and shortly thereafter another SDC address receives an almost identical SDC amount (after the Shadow was converted back into SDC) and thereby "link" the transactions with basic logic. Yes this would not be proof of the transaction because they are not directly connected on the blockchain, but common sense links them quite easily.

One possible fix could be to set minimum (and perhaps random) time limits before a Shadow transaction can be sent after a SDC>Shadow conversion and between the time a Shadow transaction is received before it can be converted back into SDC

Can the dev team comment on this? It seems like an easy way to improve practical anonymity on the network

this is key...

[rustynailer]

Is the dev team working on the issue of SDC>Shadow>Shadow>SDC conversion time rules?

If someone converts SDC to Shadow, sends it to another Shadow address and that person converts it all back into SDC right away, the anonymous nature of Shadow>Shadow wont matter much. Anyone can see on the blockchain that one SDC address was debited by a certain amount and shortly thereafter another SDC address receives an almost identical SDC amount (after the Shadow was converted back into SDC) and thereby "link" the transactions with basic logic. Yes this would not be proof of the transaction because they are not directly connected on the blockchain, but common sense links them quite easily.

One possible fix could be to set minimum (and perhaps random) time limits before a Shadow transaction can be sent after a SDC>Shadow conversion and between the time a Shadow transaction is received before it can be converted back into SDC

Can the dev team comment on this? It seems like an easy way to improve practical anonymity on the network

One way to fix that is to send more sdc than you need to shadow and keep them in shadow tokens and spend or send as needed.

[child_harold]

Is the dev team working on the issue of SDC>Shadow>Shadow>SDC conversion time rules?

If someone converts SDC to Shadow, sends it to another Shadow address and that person converts it all back into SDC right away, the anonymous nature of Shadow>Shadow wont matter much. Anyone can see on the blockchain that one SDC address was debited by a certain amount and shortly thereafter another SDC address receives an almost identical SDC amount (after the Shadow was converted back into SDC) and thereby "link" the transactions with basic logic. Yes this would not be proof of the transaction because they are not directly connected on the blockchain, but common sense links them quite easily.

One possible fix could be to set minimum (and perhaps random) time limits before a Shadow transaction can be sent after a SDC>Shadow conversion and between the time a Shadow transaction is received before it can be converted back into SDC

Can the dev team comment on this? It seems like an easy way to improve practical anonymity on the network

One way to fix that is to send more sdc than you need to shadow and keep them in shadow tokens and spend or send as needed.

This has been brought up before.

Even if a user does what LucyLovesCrypto suggests the transaction is still unlinkable and untraceable and even though one SDC addy gains a similar amount of SDC (tx fee varies on ring sizes) there is still plausible deniability. It cannot be proven the those SDC (similar in amount as they are) were sent from addy A to B. B could have received any of the networks Shadow tokens. Moreover it is a 2 step process: SDC>SDT (shadow tokens) followed by SDT>SDC so the timings are not predictable.

It is also worth bearing in mind that when an SDT>SDC transaction is made the newly created SDC arrive in a brand new SDC addy created on-the-fly in the recipients wallet. This means that the SDC received cannot be connected with any of your existing SDC addys. It is as though the SDC magically sprang into existence out of nowhere.

However as rustynailer points out, it is better to make your own stash of Shadow tokens which you spend off at your own leisure. Personally I keep between 10-20% of my Shadow as SDT, ready to be deployed at a moments notice when I hit send  

n.b. also IIRC converting SDT>SDC does NOT decrease the networks available anonymous I/O

[child_harold]

A NEW CHART which displays more information about what's going on with SDC/SDT. thanks dasource!

http://shadowchain.info/stats/shadow.php

[dbt1033]

A NEW CHART which displays more information about what's going on with SDC/SDT. thanks dasource!

http://shadowchain.info/stats/shadow.php

Wow....  That's a LOT of Shadow Tokens!

[Shadow_Runner]

What is Shadow Tokens? Can't find info at OP.

[dbt1033]

What is Shadow Tokens? Can't find info at OP.

Spending Shadow
There are two ways in which Shadow tokens can be spent: they can be sent as Shadow tokens or
redeemed as SDC.
1. When sent as Shadow tokens, new tokens are minted for the recipient to the value of the
input Shadow minus the transaction fee.
2. When redeemed as SDC, new SDC is created to the value of the input Shadow minus the
transaction fee.
In both cases the input tokens become unspendable.
The transaction fee for spending Shadow is 100x greater than the fee for standard transactions. This
is to cover the cost of the extra activity required by the network to transmit, verify and store shadow
transactions, which are larger and require more processing than standard transactions.
In order to spend Shadow, we use ring signatures to sign the transaction[5][6]. Our scheme consists
of three functions, generateRingSignature, generateKeyImage, verifyRingSignature.
For efficiency’s sake, when spending Shadow, we get a list of all anonymous outputs in the system,
then we remove coins that don't have enough same value outputs in the system, then we choose
the smallest coin or least number of smallest coins that can cover the amount + transaction fee.
Each Shadow coin has its own private key, so when spending Shadow, each coin or anonymous
input, will need to have its own ring signature generated, and will then have to be verified.
❖ generateRingSignature
➢ Executed by the sender / signer, when spending Shadow.
➢ After executing generateRingSignature, the ring signature will have to be verified.
➢ Takes an input­output / reference to the keyImage, the transaction hash, the ring size,
the secret key offset, the secret key for signing the transaction, a list of public keys for
all the coins or outputs in the ring signature and the ring signature, and a hash of the
transaction in which the signature is included (preimage).
❖ generateKeyImage
➢ Executed by the receiver, when receiving Shadow➢ The key image is revealed to the network to prevent a token from being spent more
than once.



From the Whitepaper

Basically, shadow is the anonymous component of SDC.

It is created by burning SDC.  When it is redeemed, new SDC is created on the blockchain. 

It is my understanding that as more and more Shadow is created, more and more anon inputs/outputs are also created, strengthening the anon component of the network as it is used over time.

[Cornett]

A NEW CHART which displays more information about what's going on with SDC/SDT. thanks dasource!

http://shadowchain.info/stats/shadow.php

Thank You Dasource !

With regards. Cornett

[00Smurf]

What is Shadow Tokens? Can't find info at OP.

Spending Shadow
There are two ways in which Shadow tokens can be spent: they can be sent as Shadow tokens or
redeemed as SDC.
1. When sent as Shadow tokens, new tokens are minted for the recipient to the value of the
input Shadow minus the transaction fee.
2. When redeemed as SDC, new SDC is created to the value of the input Shadow minus the
transaction fee.
In both cases the input tokens become unspendable.
The transaction fee for spending Shadow is 100x greater than the fee for standard transactions. This
is to cover the cost of the extra activity required by the network to transmit, verify and store shadow
transactions, which are larger and require more processing than standard transactions.
In order to spend Shadow, we use ring signatures to sign the transaction[5][6]. Our scheme consists
of three functions, generateRingSignature, generateKeyImage, verifyRingSignature.
For efficiency’s sake, when spending Shadow, we get a list of all anonymous outputs in the system,
then we remove coins that don't have enough same value outputs in the system, then we choose
the smallest coin or least number of smallest coins that can cover the amount + transaction fee.
Each Shadow coin has its own private key, so when spending Shadow, each coin or anonymous
input, will need to have its own ring signature generated, and will then have to be verified.
❖ generateRingSignature
➢ Executed by the sender / signer, when spending Shadow.
➢ After executing generateRingSignature, the ring signature will have to be verified.
➢ Takes an input­output / reference to the keyImage, the transaction hash, the ring size,
the secret key offset, the secret key for signing the transaction, a list of public keys for
all the coins or outputs in the ring signature and the ring signature, and a hash of the
transaction in which the signature is included (preimage).
❖ generateKeyImage
➢ Executed by the receiver, when receiving Shadow➢ The key image is revealed to the network to prevent a token from being spent more
than once.



From the Whitepaper

Basically, shadow is the anonymous component of SDC.

It is created by burning SDC.  When it is redeemed, new SDC is created on the blockchain. 

It is my understanding that as more and more Shadow is created, more and more anon inputs/outputs are also created, strengthening the anon component of the network as it is used over time.

That is correct, also converting to shadow tokens, reduces the avail supply of SDC, So it has an interesting effect.