I'm surprised you're so sour at Maidsafe when that error seemed to be the genius that was templar77. His thoughts don't suggest anything about Maidsafe as a project.

So, perhaps you've seen the post above by user:maidsafe

Obviously, there is a difference between those claims and perhaps there is more evidence as background to these that might help resolve this?..



No, I just don't jump to conclusions.

You can see the number of coins allocated in the spreadsheet for BTC payments and the transaction id's noted there are progressing as they work on those. I guess when just depends then how far down the list you are.
https://docs.google.com/spreadsheets/d/1r4fv57JDNkW55P5dnwPmHF3rOhdt1Jn5I2DZFuZfmfU/htmlview?pli=1
If you made payment with MSC then lookup is https://masterchest.info/lookupadd.aspx?address=ADDRESSGOESHERE

You have it back to front. This isn't the usual pump and dump scam copy coin that needs people to persuade anyone. Do a bit of research and don't be lazy expecting other people to compensate your ignorance. Do a bit of reading and wonder why people are looking to support this - it's not dumping money in a hole; it's an opportunity to move the area forward. http://scholar.google.co.uk/scholar?hl=en&q=maidsafe&btnG=&as_sdt=1%2C5&as_sdtp=

@RawDog - Be nice to noobs. Rage at the trolls, if you want.

You need to know which public address you sent from. If you can find the transaction id from the history of transactions, perhaps searching that on http://blockchain.info/ will show more clearly which address you sent from. SPT will be credited to the same address by return. If it's not clear the address can be a reference address for BTC; MSC; XCP; and now MaidSafeCoin SPT.. and that's still the BTC blockchain, though others like DVC use the same addresses on a different ledger==blockchain.

To make any action with SPT in future, you will need to know your private key relating to the address.. the private key is everything. If you didn't send from one address that you control the private key for then you can usually export those, though some shared web wallets don't allow that, software like bitcoin-qt perhaps will but you might need commandline for that.

You will need to know the private key of the BTC|MSC address you sent from.
Perhaps email info@maidsafe.net - address from bottom of http://www.safecoin.io/

That's not how reality works! You can't expect other people to do the hard work for you. Also, proving the negative is never possible. Prove that it is the case, don't expect others to prove that it isn't.




You can see the number of coins allocated in the spreadsheet for BTC payments and the transaction id's noted there are progressing as they work on those. I guess when just depends then how far down the list you are.
https://docs.google.com/spreadsheets/d/1r4fv57JDNkW55P5dnwPmHF3rOhdt1Jn5I2DZFuZfmfU/htmlview?pli=1
If you made payment with MSC then lookup is https://masterchest.info/lookupadd.aspx?address=ADDRESSGOESHERE

ITT and every other one it seems, there are noobs calling scam at every turn. "Done no research but got an opinion, derp."

There's no evidence that Maidsafe project is a scam. There are always third parties looking to take advantage and always sore losers grumbling on the sidelines.

 

So templar is a self proclaimed 'genius' and now famous but again where is the evidence that the address is necessarily MtGox? If MaidSafe and others are to act, they need to know the basis for that. Repeating speculation, isn't going to help here. Obviously, it's possible templar is correct but it's also too common for people to jump to conclusions.

The challenge is suggesting this address is MtGox : https://blockchain.info/es/address/1Drt3c8pSdrkyjuBiwVcSSixZwQtMZ3Tew
I'm not trying to prove that it isn't. The challenger must provide their evidence, it's not for others to prove the negative.

If you're to make a case, you need to provide all the steps to proving the point; I can't see the source, proving that address is MtGox. As noted above, anyone can tag Blockchain address wrongly.

Blockchain is just foolproof; it's trivial to export the private key to a single address that you choose to send from. QT perhaps chooses whichever address has sufficient funds; so, I don't feel in control of QT and consider it is a mix of multiple addresses. If you're confident you are sending from the address in qt or the daemon and you know the private key to that address, then go ahead. When you look to move SPT later you'll need to know the private key, that's all.

I'd like to see the source proving it as MtGox too..

I think, leave it to the pros .. https://bitcointalk.org/index.php?topic=582731.msg6372180#msg6372180

Yes, the transaction is on the Bitcoin BTC blockchain and the address then holding BTC can also hold other coins like Mastercoin MSC; Counterparty XCP; and now Maidsafecoin SPT. To send those maidsafecoins once you receive then, you need to use a wallet that can work with those, which I expect for now will be the mastercoin wallets.

You need to know which address you send from.

You can check the madesafecoin balance currently allocated to your address at https://masterchest.info/lookupadd.aspx?address=ADDRESSGOESHERE

The SPT will be sent to the address you send them BTC from; so, easier to do this from blockchain and control which address is used. Obviously, to send SPT later on you'll need to use a Masterchain like wallet that can work with that, rather than just the BTC in that address.

Not sure where you got that address.. the MSC collection address was https://blockchain.info/address/1ARjWDkZ7kT9fwjPrjcQyvbXDkEySzKHwu
 but obviously don't use this address now..

0.05555 mBTC received there relate to the MSC transfers.


@superresistent try looking at academic works and patents rather than github! http://scholar.google.co.uk/scholar?hl=en&q=maidsafe&btnG=&as_sdt=1%2C5&as_sdtp=

You can still buy safecoins by sending BTC to the BTC address. http://www.safecoin.io/ suggests it's open until they've received 7341BTC.. see current total at https://blockchain.info/address/1KHfLixa2idRnZXMUfEisBati1vpywaH6E