Topic: MaryJanecoin LLC The Bitcoin of the Cannabis Industry and Community - page 161. (Read 338837 times)

dev,you want to create the super mary?

i am not worried about it. i trust c-cex plus we can view te address at any time so not a issue. looking forward to 10k plus

I took care of him. The 99 coins is well worth the community being able to see that this is not fud and an issue that needs to be resolved (and should have never happened, but once it did could have still been resolved fairly quickly)

Thanks for the write up oc.

Once the fork is done and the new wallet is released, then the coins will be stuck there forever and we can put this whole thing behind us.

for the fifth time:

https://www.youtube.com/watch?v=I4EwdRWopmk

where video? please link

uh i did not want to steal them, i'd be glad to return them to you mate, send me your address.

I appreciate it, Thanks bud!!  This is a problem they can come back from, but I just wonder how many other ICO were done this same way?  Maybe before MaryJ spreads to too many exchanges the Dev's should do a 1-1 exchange to a new blockchain. Premine 1 block with the total coins valid right now, and ask the exchanges to help do a v1-to-v2 similar to how bluetrade help html to html5...

Just a though.  Like I said earlier this is my first IPO and I am really trying to understand the whole process...

I dont know how often I need to explain this again and again but i'll try it one more time:


1. Why Burning by sending to a Mammoth/Other Wallet Address is a bad idea:
When you create a Mammothcoin address you create a valid address and a wallet.dat containing a private key
of that valid address. You send the funds from Coin A to a valid address which is ACCEPTED by Coin A's Wallet but generated by Coin B'. That means literally nothing - just that Coin A and B share the same Address encoding AND that Coin B would accept a Coin A address and vice versa. Every address - as long as you have the private key - generated by coin B is also valid for coin A and vice versa as there is no "address delegation" or so in the network. There is no postoffice where address must be registered - you simple create a network address by calculating a privkey and a pubkey - think of the coin address like a abbreviation for you pubkey. So if you send the coins to this abbreviation in either networks - as long as you got the privkey to decrypt the abbreviation - you got the funds. On BOTH networks.


2. Why you should send to a special BURN address when burning coins:
Coin Addresses are for the coin wallet valid looking addresses WITHOUT a known privkey. You are just fooling the wallet to accept a address which you type in your wallet. So you do NOT create an address, you simply invent one like "MaryMaryBuRnBTsGFTCyw7E5brMVHLcyiR" and send the funds there. The coins are now "stuck" in a for the wallet valid looking address - but no one knows the pub or privkey of that address and even the NSA would take about a thousand years to calculate the privkey of that address .. remember a privkey's length.
Of course the invented Address must match the coin's hash (this can be calculated with a vanitygen for example)


So why did they do the show with the video if it is that easy ?
They probably did not know what they were doing...


Are the coins burned yet ?!
Currently not really - someone, in this case C-Cex, could lie to us and simply re-import the privkey and have the funds - I doubt they'll do that as they would hurt their reputation even more, but for peace in mind you could simply invalidate all transactions from this address by doing a wallet update/fork.

Coinmonster,

I am sending you maryj to replace the ones you put up for the experiment.

Did you notice in the video of the "burning" the mammoth wallet was already open and the address used was already created.  How are you sure that the person making the transfer video didn't "dumpprivkey" before he started the video.

If anything this should cast further doubt as to what is really going on here.  I hope you guys don't get burnt by this, Bittrex is one of the last decent places left to trade.

Thanks richie

You guys are wrong and I hope that Ocminers experiment has convinced you of that.

_IF_ a public key for COINA is compatible with COINB, there is a high likelihood that COINA private key can be imported into COINB.  This is the process we have to go through every time someone sends their ARCH coins to their ARCOIN wallet for example.

That said, as long as the private key for the address that the coins were sent to has been destroyed, this shouldn't be an issue.  My original concern was the fact that the blockexplorer hid the burn address.  I have since verified the burn on both the original explorer and the one ocminer put up.  At this time, we have removed the warning with the understanding c-cex has destroyed the coins along with the private key properly.

Thanks,
richie

Sorry, you are too late, i grabbed them already:

TX: https://chainz.cryptoid.info/maryj/tx.dws?49f5fcb0ab71508aad58068b71370d2677da9f206d4ce042efa958982379dc1b.htm
Old Address: https://chainz.cryptoid.info/maryj/address.dws?MGCquKviY3j3BTsGFTCyw7E5brMVHLcyiR.htm

I hope you guys will finally wake up now ...

Thanks for the free coins man

next stop 2000 - 3000 sat 

Excellent, quick and efficient solution. Perfect
(I just wish you would have listened a couple of days ago when I first brought the issue up and this could have been completely avoided)

Just a note. Bittrex has removed the warning, and Richie will be posting here shortly. The accurate current supply is listed on https://chainz.cryptoid.info/maryj/

However, in order to increase confidence, we will be forking the code to ignore the address the 36 million burned coins reside on as soon as possible. Thank you for being patient.