The sats become ya(ch)ts …
I didn’t say it’s different from the rest of the scams. I said I personally consider hard wallets insecure and don’t use them.
btw my friend is a smart guy and at least average in crypto usage. If he can be scammed like that, lots of other users can be scammed the same way, too.
I moved some of my ZEC to a Guarda desktop wallet, and some to a bitpie Android wallet. It doesn’t meet my security standards but I don’t like to lose the YEC that will come out of it.
btw, in the guide, I read:
Is there indeed a pre-fork transfer deadline set by Guarda and bitpie? And if yes, where can I see that?
SafeTrade Will have Ycash credited on the account automatically.
SafePay, Copay-based wallet - is just a few easy steps. safepay.safecoin.org
You can create a Ycash wallet with the same private key by simply using a “long press” on the Ycash logo in your Zcash wallet.
As posted by mr hloo earlier in a link in this thread. (he calls this this advanced way, I call it the safe way)
These are the only two methods which will not allow anyone potential access to your zec by trying to claim yec (the are essentially the same thing just in a different order, and ordering is important)
my method is safer and the only one that guarantees to stop anyone potentially deshielding your zcash transactions via ycash privkeys
EDIT: the ycash foundations advice is fine to follow if you are transferring off an exchange. My advice is if you run a local node/wallet and already have possession of your private keys, and want to keep using those priv/pub key pair.
Things to note, 100 blocks after the fork you transfer all your zec to a new private key. then use your old key in the YEC software. - This imho is bad advice unless it is 100% necessary to do it like this. (see edit at the top about transferring of an exchange for the sole purpose of getting yec, then will transfer back onto the exchange before you try to claim your YEC)
If you have a public ZEC address and want to keep using it and claim your YEC without compromising your current ZEC privkey.
My method (trying to use the ycash foundations terminology)
- tried and trusted mechanism for any fork.
- This protects against nefarious wallet creators. (they can only steal your yec and have no potential to deshiled your zec transactions, nor zec or future zec that may appear.)
Now there is no correlation between YM1 and ZM1
@hloo feel free to update your instructions with this info. It could be useful for people that want to keep their ZEC pub/priv key pair and have potential deshielding concerns.
This is a better method than giving the old privkeys away which could be a security concern if they could scan the yec blockchain to see what historical spends that privkey had done on the zcash blockchain. (the ycash blockchain is identical up until that point)
Please follow my method and generate a new zec pub/privkey pair for this, if you value your privacy.
As for air gapping and computer hygiene there is a thread for that over here
If you don’t want to read through that at least go to the EFF and look at their stuff
Is it possible to run a YCash node simultaneously on the same Linux PC currently running a ZCash Node…nm…looks like you can…
Does the ycash node require a different port to be open to receive more connections than 8 like with the ZCash node? Does it use the same one as the ZCash node? (important question).
perhaps we can say that this is “dually noded” lolo
Different port number (8833), different ‘everything that matters’.
They’ve been very careful to make sure nodes play nicely together, which has been nice to see.
Edit: More importantly, whats the car on your background?
did you think am run???you have to think clarity…i donate all why??look and read all community…zcash is gone.they op"rate again etc.how many day…i do have 'self ineteresting of conpany…did you think i have a power right now to dicide???
Ycash is now supported by ModernWallet, SnowGem multi-currencies full node wallet: https://github.com/Snowgem/ModernWallet/releases/tag/1.0.8
You beat me to the punch. I wrote a blog post yesterday (but haven’t published it yet) in which I describe the alternative strategy of making the transfer before the fork, in part to address the exact concern that you raise: the user has ZEC addresses that will likely still be in use after the fork (for example, a public donation address).
The suggested ticker symbol for Ycash is YEC, not YZC.
Are there going to be any custodial wallets for android/iphone allowing the export of private keys and using both Z and T addresses? (Y and S, if you will).
At launch, the answer is no.
Question: Are there any Zcash wallets that fit your description? Perhaps Shielded Guarda?
I like the idea of an ASIC-unfriendly coin with ZCash’s privacy features. But the fact that only closed source miners are available is disappointing. It leaves the ecosystem at the mercy of a few mysterious developers, and requires a user to run code they can’t audit. So it would be great if there were an open source miner for Ycash. Are there any efforts in that direction, for example porting djezo’s CUDA miner to (192,7)?
I agree that a highly performant open source miner for Equihash(192,7) would be fantastic. With that said, our priority is to fund the work to change the Proof of Work algorithm (to ProgPOW or RandomX) rather than fund development of an open source Equihash(192,7) miner.
Thanks for clarifying your priorities. Although I don’t think it would be all that much work to tweak and test an existing open source Equihash solver, prioritizing a better overall PoW is certainly understandable.
But I sure hope the eventual PoW has a good open source reference implementation. I can’t see the project retaining much credibility if it depends on magic binaries that may or may not be malicious.
Something worth noting here is that until mining on mainnet starts and the Ycash Foundation starts receiving a portion of block rewards, @hloo is bankrolling everything personally. (Correct me if I’m wrong there, Howard.) I think it makes sense to ruthlessly prioritize, get the project up and running, and then allocate capital toward everything else once there’s capital to allocate.
Hey everyone! Here’s an FAQ/Guide that condenses the information should any of your friends need to know what’s happening, and quick!
Feel free to let me know if you find any issues with it, or if anything needs amendments!