Blockchain (faster sync)All updated live and always current. Are you sure this list (from OP) is always current? I downloaded the 2.3 gb Windows blockchain from the link above and started out 125 days behind. I am now still 114 days behind seem to keep getting stuck. Thanks! The auto-updater is down at the moment as we're moving servers around, but it shouldn't have fallen back to 125 days behind. I'll take a look at it this afternoon and see if I can finish the move and bring it back up. Based on the block number I started with (I cant remember it exactly) I was definitely 125 + days behind after putting the blockchain in the proper folder. As of this moment I am only on block 230418 (108 days behind). I will get there slowly but I still think it would be very helpful for the link to be current for the benefit of new users. Thanks again! 2 more questions: 1. What is the current recommended amount of RAM for running bitmonerod? I saw 4GB listed at one point but that was late summer. Is more needed now? 2. If someone does not have enough RAM for bitmonerod? How can they verify their current balance? I know you can use simple wallet to create an offline wallet without using bitmonerod and generate an address to receive payments. For example can the view key be used for this purpose somehow by using the block explorer to check the current balance for an address in cold storage? |
|
|
|
Blockchain (faster sync)All updated live and always current. Are you sure this list (from OP) is always current? I downloaded the 2.3 gb Windows blockchain from the link above and started out 125 days behind. I am now still 114 days behind seem to keep getting stuck. Thanks! |
|
|
|
Can someone create a to a step by step guide to creating a cold storage wallet for Monero?
I think it would be helpful for new investors who are uncomfortable keeping XMR on an exchange.
Perhaps separate guides for Windows and Linux with screenshots would be best
It is pretty much the same on all OS. Mac/Linux: simplewallet --generate-new-wallet wallet-nameWindows: simplewallet.exe --generate-new-wallet wallet-name(When asked for a password, give a really long random one -- don't worry about remembering it.) Write down the address and seed words. Double check that you got them right. Delete the wallet files. You can do this with an offline computer, and you don't need to be running the daemon (in fact you don't even need the daemon binary installed). Or use fluffypony's extended guide: http://www.reddit.com/r/Monero/comments/2dt1h9/definite_guide_to_securely_storing_monero_on_a/https://bitcointalk.org/index.php?topic=583449.msg8246348#msg8246348Hey everyone,
What security measures do you recommend for your cold storage keys. I was thinking more about measures to prevent hacking/theft of the keys. Should i be paranoid to the point of creating the wallet in an air gap and never look into it until I need it? (Lets not go into the "Ruiu says badBIOS leaps air gaps" territory).
Regarding backup I'm doing the _strongly encrypt your files and stored them in offline and online sources and don't forget the deterministic seed_ routine. If anyone as further thoughts on backup that would be appreciated also.
Remember, rockets are old school. We are going to the moon in a space elevator. Keep calm and get some moar.
Peace!
My suggestion is as follows: 1. Take any machine you have lying around, even your normal workstation. You may find it easier to use an older computer that has no wifi or bluetooth if you're particularly paranoid. 2. Create a Linux or Windows bootable disk, and make sure you have the Monero binaries on the same disk or on a second disk (for Linux make sure you have also downloaded copies of the dependencies you will need, libboost1.55 and miniupnpc for instance). 3. Disconnect the network and/or Internet cables from your machine, physically remove the wifi card or switch the wifi/bluetooth off on a laptop if possible. 4. Boot into your bootable OS, install the dependencies if necessary. 5. Copy the Monero binaries to to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something) 6. Don't run the Monero daemon. Instead, using the command line, use simplewallet to create a new wallet. 7. When prompted for a name, give it any name, it doesn't really matter. 8. When prompted for a password, type in like 50 - 100 random characters. Don't worry that you don't know the password, just make it LONG. 9. Write down (on paper) your 24 word mnemonic seed. 10. Write down (on your phone, on paper, on another computer, wherever you want) your address and view key. 11. Switch off the computer, remove the battery if there is one, and leave it physically off for a few hours. There you go - the wallet you've created was created in RAM, and the digital files are now lost forever. If some magical hacker manages to somehow get the data, they will lack the long password to open it. If you need to receive payments, you have the address, and you have the view key if needed. If you need access to it, you have your 24 word seed, and you can now write out several copies of it so that you have an offsite copy (eg. a bank deposit box). Due to the nature of the key you can write it as part of something else - eg. write a fake love letter to your wife so that the 24 words on the left hand side are your key or whatever. Then write a bunch of extra love letters. That way, if your deposit box is ever discovered, it'll be disregarded as unimportant love letters. Thank you both! I do have a follow up question.... Smooth says "you don't even need the daemon binary installed" Fluffypony says "Copy the Monero binaries to to a RAM disk" Can you define binaries in this case because it seems like one of you are saying they are needed and one of you says they are not. |
|
|
|
As of today there are 412 addresses with over 100 SDC. Lets bump this post once per week so we can track our progress. As long as the community keeps working to help market SDC I will help as well! Our dev team has innovated and delivered again and again. Now lets help them market our great currency to the world! Think outside bitcointalk. We all have friends outside of crypto that will be receptive to our vision if we just share it with them. http://shadow.blockexplorer.cc/richlist/index.php?min=100As of today we are up to 449 addresses with at least 100 SDC. The community is growing! http://shadow.blockexplorer.cc/richlist/index.php?min=100If you do not have much SDC/BTC to donate and are not a programmer or web developer you can still help! 1. Keep converting SDC into Shadow. We need more Shadow to make future conversions (of all sizes) easy at all time 2. Take your coins off the exchange and Stake SDC! If Gox and Mintpal were not enough of a reminder then maybe Bitstamp this week will be. Handle security yourself instead of relying on online wallets and protect the PoS network by staking (while earning some small staking rewards)! 3. Keep introducing SDC to friends! While 449 addresses is more than 412 (from my prior post) we can do better! Our tech is groundbreaking and soon we will have more code reviews from top cryptographers to prove it. You are doing a favor to your friends by telling them about SDC sooner rather than later. Give them a small amount for free if you have to. Just get them to download the wallet and try it out. They will soon be hooked just as you are:) agreed. Just created a bunch of Shadows plus am staking. Great! The more people that follow your lead the better. |
|
|
|
Hello everyone! To allow the SuperNET ( www.supernet.org, MultiGateWay, InstanDEX, ...) to support this coin I would like to kindly request from you the following data: Default RPC port Minimum transaction fee Estimated block time in seconds daemon file Exact spelling of the conf file with path for Windows Mac Linux ## Example (Bitcoin) Default RPC port: 8332 Minimum transaction fee: 0.0001 Estimated block time in seconds: 600 Daemon file: bitcoind Exact spelling of the conf file with path for Windows: Bitcoin\bitcoin.conf Mac: Bitcoin/bitcoin.conf Linux: .bitcoin/bitcoin.conf ## Currently we're looking for popular coins compatible with the Bitcoin RPC. Please reply to my post here or write an email to info@supernet.org, or use this form: https://docs.google.com/forms/d/1zIxff1hXiSC3MkQRXtkBe3KOymVaAp8NYwpYyuXRYPo/viewformFeel free to send the data for any other Bitcoin RPC compatible coin you would like to see supported by Supernet. If you would like to be invited to sprnt.slack.com, our main communication platform, please send me your email address. All the best, noashh info@supernet.orgChat: chat.supernet.org I think this could be a good thing for getting ANC more attention. Does the dev team care to comment? |
|
|
|
|
Can someone create a to a step by step guide to creating a cold storage wallet for Monero?
I think it would be helpful for new investors who are uncomfortable keeping XMR on an exchange.
Perhaps separate guides for Windows and Linux with screenshots would be best
|
|
|
|
Thanks! XMR remains the best:) |
|
|
|
|
Has the CINNI rocket launch for the moon left yet? If not why not get a seat on the SDC rocket ship? Its pilot is rynomster who left CINNI for better opportunities elsewhere
|
|
|
|
Any comment on the fluffyponyza SDC code review (XMR Core Team) on Reddit? http://www.reddit.com/r/Monero/comments/2pfmds/shadowcash_ring_signature_whitepaper_released_any/"There's little substance in the code, the verifyRingSignature() method is trivially simple and isn't called anywhere else in that commit. Their proposed function, generateRingSignature(), doesn't exist and thus it's impossible to determine whether they've actually done anything of substance. The whitepaper is purposely vague in many of the important parts, and a review in conjunction with code is impossible, so we have to take it on the face of it...which is that NIZK + ring signatures + security + low space utilisation = impossible right now." "That's the commit I'm referring to - it does some trivial ring signature verification and creates key images, but it doesn't actually use them in transaction, nor does the code exist to create a ring signature." For the record I support both SDC and XMR. It would be great if SDC dev team could respond on the Reddit thread. Thanks! His first comments have no substance, he said that without having checked https://github.com/SDCDev/shadowcoin/commit/317b9b1f5121ecde162fd8d37fbd587182c45fef?diff=unifiedThe only interesting comment is this one : There's no NIZK stuff in there, at least not anything beyond what Monero's keyimages use (which is a very simple ZKP). I'm unfortunately failing to see what they've done beyond what is already in the CryptoNote whitepaper and implemented in Monero. Even if what he says was true (nothing unique compared to CryptoNote), it would not be fair, because i don't remember any CryptoNote implementation on Bitcoin base  Great point ffmad! nobody else has used elements of ring signatures on bitcoin based coins. He seems to be willing to debate exactly how much ring sig tech is used, but wont debate you on your point that it is the 1st in crypto for this codebase |
|
|
|
Any comment on the fluffyponyza SDC code review (XMR Core Team) on Reddit? http://www.reddit.com/r/Monero/comments/2pfmds/shadowcash_ring_signature_whitepaper_released_any/"There's little substance in the code, the verifyRingSignature() method is trivially simple and isn't called anywhere else in that commit. Their proposed function, generateRingSignature(), doesn't exist and thus it's impossible to determine whether they've actually done anything of substance. The whitepaper is purposely vague in many of the important parts, and a review in conjunction with code is impossible, so we have to take it on the face of it...which is that NIZK + ring signatures + security + low space utilisation = impossible right now." "That's the commit I'm referring to - it does some trivial ring signature verification and creates key images, but it doesn't actually use them in transaction, nor does the code exist to create a ring signature." For the record I support both SDC and XMR. It would be great if SDC dev team could respond on the Reddit thread. Thanks! |
|
|
|
So when are we expected to hit block 257,000?
Rough estimate would be the upcoming Sunday/Monday. I remember you being a DRK holder back in the day so perhaps this question is relevant to you.... What happens if not everyone updates to the new SDC client before block 257,000? I remember when DRK had big problems (forks, etc) when people did not upgrade as requested. I know this is a different situation (PoS vs PoW and no masternode payment issues etc) but I am still curious on how the SDC network will be impacted if not everyone updates in time. I assume at least a few people will not either because of laziness, or not being online to see the update this week. What is the worst that could happen if people to not update on time? btw I am pleased with the code I see in GutHub. Going open source sooner rather than later for most of the newest update was the right decision. Thanks dev team! |
|
|
|
I am confused. Is the present ShadowCash release opensource, or not?
Part of it is. See comment from ryno above regarding the verification code (good) Some are selling (before block 257,000) because of the closed source spend code (scary) |
|
|
|
Cloak had anon that was initially believed to be trustless until it became evident that a posa tx could be decrypted / hacked by a bad wallet (although very difficult to do so) to reveal sensitive data. It took many weeks after testing for that to surface. Now SDC is doing something different and very clever. It seems SDC is using a purely blockchain based process for issuing / destruction / redemption of Shadow and on that basis, if correct, makes the unforgeability very strong indeed. From whitepaper. Shadow can be minted, which will destroy SDC
(ShadowCash), and will output a group of Shadow tokens totaling the same value
(minus the transaction fee) of the destroyed SDC.
The obvious weakpoints in SDC anon, if there are any, as pointed out before by people raising questions would have to be the risk of cheating the system for gain. What would seal the deal in SDC is: Irrefutable proof that there is no possibility to hack the wallet to allow minting of shadow tokens without destroying SDC of same value. This is my concern as well. I plan on dumping all of my SDC quickly because of this fear (before we hit block 257,000) but will come back and buy more once I am confident in the safety of the code. Things could be great but block 257,000 and forcing a mandatory upgrade by this weekend is way too fast. We need more time and eyes to bug test the code |
|
|
|
|
Anyone want to buy SDC off the market?
I want to sell a lot of it quickly but would prefer not to crash the price. Currently there is not much buy support on Bittrex.
Send me a PM if interested
|
|
|
|
Hi all
After much planning and development, we are proud to bring you our latest release. Many of you have been involved in the testing process, and we are very thankful for all the help that has gone into this release.
The main feature in this release is ShadowSend v2, but here's a list of other improvements we've made during the development cycle:
- Anonymous transactions using zero-knowledge proofs
- Multiblock download (Thin and Full Modes)
- ShadowChat now shows unread message count instead of total message count
- Ring size suggestion for Shadow spend transactions
- HTML options page
- Transaction type display selection
- Notification type selection
- Enable/Disable Thin Mode from options
We thank you all for your patience as well, and without this community, this release would have never been possible.
Without further ado, here is our WP:
ShadowCash: Zero-knowledge Anonymous Distributed E-Cash via Traceable Ring Signatures
Anonymous ZK transactions will only work from block 257000 onwards, as to prevent too many forks in the chain.
This is a mandatory upgrade, so please make sure you are on v1.3.0.5 before the weekend. Thank you very much! I enjoyed reading the whitepaper, but admit that it raised more questions for me about how exactly the code works in terms of unforgeability and minting of shadow (along with the related destruction of SDC). Naturally BEFORE we update the new software we would like to see the code to have some assurance it is safe from bad actors somehow finding an exploit to mint extra shadow without the destruction of SDC, etc. Can you load the code into GitHub please? I do not plan on updating my software until it can be reviewed. I hope others will follow my lead. SDC could die overnight (once we hit block number 257,000) if there is some unknown exploit possible relating to the minting process. You have worked so hard on this! Please don't take any chances by forcing a mandatory upgrade on the community (at least without a vote) until the code is public and has some time to be reviewed. A mistake now could kill the coin forever which is something nobody wants. Please add the new code to GitHub. Thanks! https://github.com/SDCDev/shadowcoin |
|
|
|
@ LucyLovesCrypto Testnet has finished. Waiting for imminent release of whitpaper and new ZK wallets, which will be on github. The Dev (Ryno) can often be found in irc and is always helpful. This ain't Cloak, it's Shadow  Thank you very much! I am happy to hear this (especially the GitHub part) Once zk releases on mainnet (open source) I see some generous tips in the future for the dev team. You guys are great! |
|
|
|
I love the mobile wallet (released) and stealth addresses (released and open source) but have several questions:
1. All the marketing efforts seem similar to CLOAK (Cloaktalk vs. Shadowtalk, One Market vs Shadow Bay, similar websites and writing styles for press releases, etc). Is the marketing team for SDC the same as it was for CLOAK? (I know the dev team including Ryno and technovert is different).
2. While the current stealth address tech is open source (thanks!) the ZK release in beta is not. Is there a reason for this? It seems to me that by putting the beta code in GitHub, progress could be made faster and any potential problems before public release would be more likely to be found. While a whitepaper is great, the community needs to see actual (zero knowledge) code to make sure it works as designed and is safe.
Thanks in advance!
1. The marketing team is not the same as it was for CLOAK. Shadow have actually marketed the coin vastly different to the approach CLOAK took which was based on deadlines and a lot of hype. Shadow has survived all these months by letting the features they developed do the talking. In particular, ShadowChat encrypted chat, HTML5 PoS Lite wallet, stealth addresses and soon true anon in the form of zk transactions. 2. I'm not sure if the code will become open source straight away. The devs have put hundreds of coding hours into producing their zk implementation, if it was open straight away the tech will be copied into other coins pretty fast as happened with rynos stealth addresses. The code will likely be audited by someone reputable whilst closed, hopefully not too long after we will see open release. This seems a fair approach. I agree the tech so far has been great. I also agree with you that no hard deadlines is more healthy for the coin. My only concern is your comments about not going open source until "hopefully not too long after we will see open release" because it sounds a lot like CLOAK told people about PoSa. I also am 99.99% that CloakTalk forms were started by the same person that started ShadowTalk forums. That is okay, because this person is knowledgeable and seems to have the best interests of SDC at heart. I just with the marketing team would be more transparent about their involvement in prior projects. Some of us like what we see but still have concerns about open source of zk project and flashbacks to promises regarding PoSA and One Market. It would also be nice if the dev would pop in and give us more information about how the testnet is going. IRC is not always helpful in providing these details and not everyone can camp there out all day hoping to learn something when it could be revealed here, Reddit, or ShadowTalk much easier. Thanks again! |
|
|
|
|
I love the mobile wallet (released) and stealth addresses (released and open source) but have several questions:
1. All the marketing efforts seem similar to CLOAK (Cloaktalk vs. Shadowtalk, One Market vs Shadow Bay, similar websites and writing styles for press releases, etc). Is the marketing team for SDC the same as it was for CLOAK? (I know the dev team including Ryno and technovert is different).
2. While the current stealth address tech is open source (thanks!) the ZK release in beta is not. Is there a reason for this? It seems to me that by putting the beta code in GitHub, progress could be made faster and any potential problems before public release would be more likely to be found. While a whitepaper is great, the community needs to see actual (zero knowledge) code to make sure it works as designed and is safe.
Thanks in advance!
|
|
|
|
This is the publicity SDC deserves! Soon the world will know about SDC! Keep of the great work |
|
|
|
Enforcement is right around the corner. Messages are now propagating perfectly and we've updated enough to turn it on from that perspective. I've sent an email out to 4 bigger pools that need to upgrade their stratum, then I'll flip the switch.
We heard this month ago? lol Quite the cult you have here. So many sheeple believe anything |
|
|
|
|
Show Posts
