apparently i woke up this morning to a lot of forum reading.
My stand of view is that I would never use a cryptocurrency for buying any marijuana as it always leaves a digital signature, cash doesn't.
i completely agree with the statement above.
Due to the size of the blockchain, and the fact you don't want to be eating up the minutes & battery life syncing, best option would be a web wallet.
http://thealtcoinguys.com/web-wallets/So you should be able to use the anon send feature, but that would have to be tested.
One other point of consideration, would be Liquidity as Super has just returned to the markets, it price would probably not hold against massive selling or at least not at the current price, it will take a few weeks to see where it settles.
One possible solution would be gift cards,
http://www.cannacash.comFind Someone in Colorado or wherever MJ is being sold that will exchange super for gift cards.
That would be a start.
web wallets are the most insecure wallets out there (except those run by the professional teams meaning blockchain.info and the major bitcoin exchanges)
also a mobile wallet would be fine. bitcoin has them and the chain for bitcoin is over 60GB. so you would need to use the same data storage system as a bitcoin wallet. and no, i dont know anything about developing for mobile platforms.
Can i ask ? Why thre's still no buy orders on cex trading Sir? Thank you
It is still Syncing. They started about the same time as
https://chainz.cryptoid.info/super/ if want want an idea of how far they have gone.
not true, they finished syncing twice now but got stuck on a fork that is 10k blocks back from the real chain because someone out there is running a bad node. they contacted me about it last night and i am going to help them fix the problem with it today.
IF YOU SEE THAT YOUR WALLET IS NOT ON THE SAME BLOCK AS
https://www.blockexperts.com/super (or within 10 blocks of it) RESYNC YOUR WALLET
There is 1 official code. That is the code on the Github from Griffith. That is the code that is being followed by the exchanges. When Griffith is working on the code he will be working on it on his local computer in an developers environment. When his changes are ready to be distributed he will release a new wallet and update his Github so that everybody is able to use the newest wallets (including the exchanges). When he will release a new wallet (less memory use and new PoS rates) then he will also update the protocol version. This will make the old wallets useless because this is necessary for the new stake rates....it will be mandatory update, everybody needs to use that new wallet, no exceptions
the statement above is 100% accurate. there is only one version of the source. my local machine has some changes on it (the PoS changes) but i havent uploaded them yet because i was going to do the memory fix. however i am thinking i will put the PoS changes up tonight and make a mandatory update. then the memory update (when finished) will follow and will be optional since it is your preference on how much memory you want used.
edit: will try my best to get the website up for tonight
why don't you commit your changes to github already? Then we can see what has been done. You can commit other changes along the way. Committing a lot doesnt hurt, especially if you commit to a seperate branch, but you will know that as the dev :-) So please commit your pending (local) changes.
