Shadow Cash {SDC} Updatd Details:

  • The Shadow Project is an open source project aiming to be the core of privacy, where people will build decentralized applications.


    Block time: 60 s

    Difficulty re-target: every block

    Nominal stake interest: 2% (PoSv3 – static inflation annually)

    Min. stake age: 8 hours (no max age)

    P2P port: 51737

    RPC port: 51736


    Min. Fee: 0.0001 SDC

    Confirmations: 10

    Maturity: 500


    Virtual currencies are quickly becoming very popular due to their superiority over traditional methods of exchange. Prior to Bitcoin, the largest problem for these virtual currencies was the prevention of double spending attacks. In short, double spending is the malicious act of executing multiple transactions using the same units of currency (the equivalent of counterfeiting paper money). Bitcoin was able to solve this major issue by integrating a public ledger of all previous transactions known as a block chain. Each member of Bitcoin’s network has the ability to analyze every transaction ever executed, allowing them to see if coins had been previously spent before accepting any new transactions. Unfortunately, as one may be able to easily deduce, a block chain such as Bitcoin’s does not allow for native anonymity or privacy. The public nature of a block chain allows anyone to observe the entire transaction history and holdings of every participant.

    Mission Statement

    On December 10, 1948, the General Assembly of the United Nations adopted and proclaimed the Universal Declaration of Human Rights. Article 12 states: “No one shall be subjected to arbitrary interference with his privacy, family, home or correspondence, nor to attacks upon his honour and reputation. Everyone has the right to the protection of the law against such interference or attacks." Nearly 67 years later, we believe this declaration to be more important than ever. To help protect this most basic right to privacy, The Shadow Project is building an encrypted, digital ecosystem. Cryptographic innovations will catalyze the evolution of communication, commerce, and currency. Shadow’s mission is to remain at the forefront of this evolution with it’s decentralized privacy platform, made available to all operating systems


    Download Wallet

    Windows X64:

    Windows X32:


    MacOS X

    Pro Tip — Download the blockchain separately, to get in sync in minutes!

    Block Explorers – Official Explorer – SDC at CryptoID – Insight Block Explorer


    For guides and technical documentation please refer to






    Trade Satoshi

    You can also pay with ShadowCash (SDC) anywhere Bitcoin (BTC) is accepted instantly with:




    Alpha private testing

    Invites can be requested using the following link: ALPHA

    Beta public testing

    More info coming soon.


    Video coming soon.


    See — ShadowProject Roadmaps


    Follow recent updates on Shadow Blog

    See latest commits on


    Shadow is an Open Source project which is created almost entirely by volunteers. There are lots of ways you can get involved and help the project grow and improve. Here are some ways for you to get started!

    Know how to code? Help us!

    The Shadow project is hosted over on GitHub. This is where our developers work hard on the next version(s) of the software. To get involved with developing Shadow, check out our detailed contributing guidelines. We credit all contributors to the Shadow project in every major and minor release.

    We hold public development meetings and chat in our Slack team (get an invite and join our chat). We also maintain a public roadmap and dev blog to give you an idea of what's being worked on right now, and what's coming next.

    We're currently looking for lead contributors in the following roles:



    Do you know someone who might be interested? Do not hesitate and contact us directly.

    Found a problem? Let us know!

    If you think you've found a bug or a problem with Shadow, please let us know! First, search our issue tracker to search to see if someone has already reported the problem. If they haven't, click here to open a new issue, and fill out the template with as much information as possible. The more you can tell us about the problem and how it occurred, the more likely we are to fix it. Please check out our bug and bounty program for our guidelines and more details.

    Please do not report security vulnerabilities publicly.

    We are a non-profit and Open Source software project and are trying to build a private economy. We appreciate all the help we can get in making this a reality. Both addresses are managed by Rynomster (lead developer). If applicable, please specify whether you want to remain anonymous. Many thanks to all our sponsors!

    Official BTC donation address: 1GiosBkSpN8RS9pm1kgZU8AZUBEnLKYFem

    Official SDC donation address: SdcDevWEbq3CZgZc8UNbST1TaYLA5vLZTS


    According to Linus’ Law, “given enough eyeballs, all bugs are shallow”. That’s one of the reasons why Shadow’s source code is publicly available; but merely making the source code available doesn’t accomplish anything if people don’t read it!

    For this reason, Shadow has a series of bug bounties. Similar to the bounties offered by Mozilla and Google, Shadow bug bounties provide an opportunity for people who find bugs to be compensated. Unlike those programs, however, Shadow’s bounties are not limited to security vulnerabilities.

    Depending on the type of bug and when it is reported, different bounties will be awarded. Bounties are paid out in SDC, at the 3-day average of each to a fixed US Dollar value.

    Things that do not qualify under the bug bounty

    • Bugs found on third-party/community sites, software or services, which is not due to an improper configuration issue specific to us. Please submit any potential issues to the maintainers of that site or providers of that service.
    • Vulnerabilities which are too broad or not documented properly (i.e. do not include a specific example relevant to a Shadow-controlled site or application).
    • Bugs or issues with a third-party site, software, or service that we use, which is not due to an improper configuration issue specific to us. Please submit any potential issues to the maintainers of that site or providers of that service.
    • Bugs and errors found in software/code that is still undergoing alpha or beta testing.
    • Usability issues
    • Anything requiring social engineering
    • DOS/DDOS attacks
    • Missing HSTS (HttpOnly flags), Secure flag, Browser Cache vulnerabilities
    • CSRF that doesn’t affect the victim
    • Referrer leakage to pages an attacker cannot control.
    • The presence of unnecessary files, e.g. for backups, when these files do not expose any sensitive information.
    • Anything that is the result of an automated Nessus/PCI scans (too general)
    • DNS issues (e.g. lack of an SPF record)
    • SSL certificate issues
    • Bugs that have received mainstream tech media or community attention before the date of your disclosure.


    Depending on the type of bug and when it is reported, different bounties will be awarded. Bounties are paid out in SDC, at the 3-day average of each to a fixed US Dollar value.

    Please do not report security vulnerabilities publicly.




    Deanonymize ShadowChat or ShadowSend (proof that a protocol is not anonymous)


    A flaw in the protocol that allows for theft or loss of funds


    A bug in the reference client that leads to consensus issues


    A bug which causes data corruption or loss


    A bug which causes the application to crash

    Note — Bounties will be paid out for bugs found in the master branch of the official GitHub repositories (en)


  • Protect the fortress - Dev Update [2 December]


    Welcome to our December update. Since our last post we have covered a lot of ground, hence the lack of communication. We have made several improvements to our platform and have been planning some major changes to the project as a whole. Over the last few months, we have seen greater support and excitement surrounding the project than we could of imagined. As a team we have been discussing some pivotal changes we would like to make to ensure this project gets the exposure and support it needs to be the best decentralized marketplace & privacy platform. We have come a long way from the beginning, but we still have a long way to go to get it into the hands of people all around the world.While we are currently in the planning phase of these changes, there are a few things we know need to take immediate priority. One of these priorities is building out and structuring the team in a more efficient and official manner. This should drastically help each developer, and the team as a whole, complete tasks, fix bugs, and push updates much easier. Bugs and issues are now managed on GitHub itself, anyone can participate.

    There has been a lot of internal discussion about the future ahead and how to get there. Several ideas are floating around and we're all putting our brains together to find the optimal situations. A few members of the team have been busy this month meeting with outside advisors on the best steps forward, and we will divulge more information on this in the near future. As a team, we all agree that in order to build a world-class platform we need to recruit top talent and bring on expert advisors. So the process starts now.

    With that said, we are happy to announce Tecnovert has recently rejoined the team in order to inspect the codebase and explore the possibilities and estimate timeframes for several new features. For those not familiar, Tecnovert helped create Shadow when it first launched and knows his way through the code very well. There is no developer better fit for the task at hand. We have a rough estimate on the necessary budget to sustain the development and are in the midst of planning out a sustainable method for funding. We will touch more on this in the near future as wel


    We have recently made our new graphical user interface fully open source. This allows other developers with knowledge of HTML, CSS and JavaScript to help a hand with issues and improvements.We have also opened up the tracking of issues to the public, improve contributors guidelines and quality assurance.

    All users who make use of the chat have to upgrade to Old clients (< will not be able to receive messages sent from and upward. A security improvement was made to the message verification scheme; namely the IV is now also included in the HMAC hash such that it can not be tampered with in transit.sp

    Translations have arrived! There is now translation support for nearly all phrases and for a majority of all the supported languages. A few phrases are still English by default but those will be changed as they are found.Note: You can change the language in the options menu. You can join our translation effort on Transifex!

    As some of you may know we have recently launched and bootstrapped our own wikipedia. This has been done by allien and he has created the only well-organized wikipedia in the entire universe. Anyone can easily edit and create pages to share their knowledge. It will remain in active development and will most likely become the main hub for our documentation.

    Click here to visit our wiki

    Support our Wiki with SDC!


    A new checkbox "enable messaging" has been added to the wallet unlock screen, now you can unlock your wallet for staking and message at the same time. Previously you had to unlock the wallet fully before being able to send or receive a message.

    Encrypted wallets are now able to stake without relocking from the command line. This is especially useful on raspberry pi's and other staking devices where the terminal is the preferred way of operating.

    ./shadowcoind walletpassphrase yoursuperlongpasswordhere 0 true

    When viewing a message sent in a chat message you will now see this image first, preventing the leakage of the IP address to third party servers. Additional work is planned to route images loaded in the GUI over the proxy for enhanced privacy and security.

    Improved estimate anon fee (work in progress)

    Some code clean up, remove json from messaging

    bridge datadir parameters

    various bug fixes


    We now have a docker image with Tor support, created by community member 6ea86b96! It's pretty neat and does the tedious process of setting up the Tor config for you, with additional security features to protect against known fingerprinting attacks and network analysis attacks against static onion addresses. When restarting the docker, a fresh new onion address is generated as a security measure.Running UMBRA over Tor hides the IP addresses from the network, and offers greater privacy. We advice all users to set this up, join IRC or Slack if you want to do this, we will gladly help. A tutorial documenting this will be available soon. Download the docker files here!

  • Shadowcash New Exchange:

     For more Info about CryptXC

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.