|
The website and FAQ says it is regulated by an Ethereum smart contract. But where is the source code of it? That's like to buy a pig in a poke. Even if the contract is public and many people reviewed it, it is possible that it can be hacked, as the DAO fiasco demonstrated. But if only a few people know the contract, chances are much higher that there are some hidden flaws in it, either intentionally or just bugs, which could lead to a total loss of all coins.
|
|
|
|
Would love to try it but I would need some detailed noob instructions. I have a 500 gig drive that had 32 BTC on it, so you see why I would want to give it a try  . Merry Xmas to you.  Wow, that's some serious money, like half a million dollar, and even like $90k for Bitcoin Cash, if the Bitcoin was there at August 1st. First you should turn off the PC immediately, if you are still using the harddisk. Install Windows or Linux on a new harddisk. Then add the harddisk as a second disk, from which you don't boot. You can then scan the second harddisk. If you are using Linux on your new harddisk (I used Debian Linux), you can see how the disk is labeled with the "dmesg" command (executed as root), e.g. /dev/sdc. Then you can use my program with this device name, which will create the wallet files, and then you can scan each file as described. If you have problems, I can help you by PM, or a private room on https://hack.chat (my spoken English is not so good, better chat), and/or Teamviewer. If I'm successful, would be nice to get one of your Bitcoins, this would really motivate me  But any good computer professional with Linux experience could do the same for you. Just watch him/her not to steal your 32 BTC when found, so best someone on site. For 32 BTC it could be even worth to try more advanced rescue functions, like if the wallet is fragmented, if the harddisk was very full, to try analyze the sectors and NTFS header entries in depth with a program or even manually for a few days. Also you could try first to use RStudio and a full disk scan (there is a free trial version, with which you can see if it finds anything, and you need the full version to rescue the file). If you are lucky, you don't need anything more special. As always, install it on a new harddisk and don't write anything on your old harddisk, and don't boot from your old harddisk. If you try other rescue programs, make sure they don't modify the original disk, but restore files to a new harddisk (RStudio is very professional, it does this). Might be also a good idea to backup the full harddisk first with a program like Ghost: https://www.wikihow.com/Ghost-a-Hard-Drive If in doubt, get the help from a professional before you lose the coins forever. |
|
|
|
Why didn't you just use pywallet to scan the drive from the start? Was there an advantage to using your program first?.
I don't think that pywallet can do a low-level scan of the harddisk, it expects a wallet.dat file. And Python would be very slow anyway compared to my C program. |
|
|
|
|
I already cashed it out. Now I'm syncing the Bitcoin Cash wallet and then importing the private keys to this wallet again, because of course there was Bitcoin on it at August 1st this year. Current exchange rate is 0.2 BTC for one Bitcoin Cash. Probably I will convert it on Poloniex and hold it as Bitcoin then.
|
|
|
|
BTW, I would have expected that the 0.05 BTC I donated to the brainwallet (with the Bitcoin address 1AF6eZBqwP4cStwJtfSPDTtqsjd6PXMFNA) would have claimed by now. Maybe read my second post in this thread again Note: in case someone already imported the private key, you should really transfer it to another address, before someone else does this. |
|
|
|
Anyone still around? I lost access to this account (and I still have no access but seems that it stayed logged on this pc) besides that my life has turned around a bit. We still have over 10% of the supply for developement purposes and I have few fresh innovative ideas so we still searching for developers.
Cool, you are back, too. What do you think about integrating gambling into the blockchain itself, with the possibility to create and destroy coins by gambling? |
|
|
|
BTW, I guess I'm drunk, but I'm so happy that I found my Bitcoins, try the last chant line from my posting as a brainwallet in https://www.bitaddress.org for a surprise  |
|
|
|
Two years ago I formatted my harddisk and installed Windows 10 on it. Before this I did a backup, but unfortunately the backup was broken. So I lost my wallet.dat, with a few Bitcoins in it. I could restore some files with RStudio, and I had older backups for the rest, but seemed to be that the latest wallet.dat was already overwritten, and I frequently add new addresses. So I gave up, not a big deal, maybe $200 lost. But I didn't use the harddisk and bought a new one. Fast forward to December 2017: Now a few Bitcoins is some serious money, so I decided to give it another try. I tried any option I could find in RStudio, checking the dozens of filesystems it reported after scanning it for hours (only a few where valid from previous installations), but I couldn't restore it. Ok, this needed some more work. My assumption was, that the file headers were broken, so I wrote a small C program myself, which scanned the whole harddisk for the wallet.dat signature (testing for the first 16 bytes). The filesystem was NTFS, which has 4k sector sizes and a file starts always at sector start, if I understand it correctly, which makes things easier. Also usually if there is enough space, contiguous sectors are used to save a file. My hope was that somewhere I could find old version of the wallet.dat, but not too old that the new keys were missing. This is the very simple and straightforward scan program I hacked together: #include <stdio.h>
#include <stdint.h>
#include <inttypes.h>
#include <string.h>
uint8_t buf[4096];
char filename[1000];
uint8_t search[] = {
0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x62, 0x31, 0x05, 0x00
};
int main(int argc, char** argv)
{
uint64_t pos = 0;
FILE* f = fopen("/dev/sdd", "rb");
FILE* w = NULL;
int walletNumber = 0;
int walletIndex = 0;
uint64_t max = 1000000000000ULL;
while (1) {
int c = fread(buf, 1, 4096, f);
if (c != 4096) break;
if (!w) {
if (memcmp(search, buf, 16) == 0) {
sprintf(filename, "wallet%i.dat", walletNumber++);
walletIndex = 0;
w = fopen(filename, "wb");
printf("found: %" PRIu64 "\n", pos);
}
}
if (w) {
fwrite(buf, 1, 4096, w);
walletIndex++;
if (walletIndex == 256) {
fclose(w);
w = NULL;
}
}
pos += 4096;
}
fclose(f);
return 0;
}
I used it on Linux as my host system and the old harddisk was visible as /dev/sdd (you can see this with dmesg). I compiled it with "gcc -O3 scan.cpp -o scan" and started it with "sudo ./scan", and a few hours later (it was a 1 TB harddisk) I got a wallet0.dat to wallet9.dat, each 1 MB in size (it doesn't matter if there is crap after the wallet data). This was a nice start Then I tried to copy it to a wallet.dat of a current Bitcoin installation, but most of the time it said the wallet was corrupt, once it even crashed at start and when it said it could salvage some information, no keys were in it. My rescue was https://github.com/joric/pywallet This program could decode all files and output it in JSON format. It needs the wallet.dat in a bitcoin-qt installation in the .bitcoin directory. I knew one of my old addresses, so I wrote a script which did test all files (actual key changed) : for i in $( ls wallet*.dat ); do
echo item: $i
cp $i .bitcoin/wallet.dat
./pywallet.py --dumpwallet --datadir=.bitcoin | grep -i 12QDRXssT63Pv5KTGBN2kyAvfLW3s7jxBs
done
The output looked like this: item: wallet0.dat
item: wallet10.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
item: wallet11.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
item: wallet1.dat
WARNING:root:encrypted wallet, specify password to decrypt
item: wallet2.dat
item: wallet3.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
item: wallet4.dat
Traceback (most recent call last):
File "./pywallet.py", line 1706, in <module>
main()
File "./pywallet.py", line 1683, in main
read_wallet(json_db, db_env, True, True, "")
File "./pywallet.py", line 1556, in read_wallet
parse_wallet(db, item_callback)
File "./pywallet.py", line 1287, in parse_wallet
for (key, value) in db.items():
bsddb.db.DBPageNotFoundError: (-30986, 'BDB0075 DB_PAGE_NOTFOUND: Requested page not found')
item: wallet5.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
item: wallet6.dat
WARNING:root:encrypted wallet, specify password to decrypt
"addr": "12QDRXssT63Pv5KTGBN2kyAvfLW3s7jxBs",
item: wallet7.dat
WARNING:root:encrypted wallet, specify password to decrypt
item: wallet8.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
item: wallet9.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
So the address was in wallet6.dat, success! I then used "/pywallet.py --dumpwallet --datadir=.bitcoin --password=mysecrectpassword > keys.txt" and I got all my keys back. In the bitcoin client I could import it with importprivkey (don't forget the "false" parameter as the last parameter, to avoid rescanning after each import, if you import multiple keys) and after the final rescan, I got my Bitcoins back. One day work for like 2 Bitcoins, which I already sold, that's a nice hourly rate  Maybe this will help some other people as well. In case you rescue a lot of Bitcoins, I would really love it if you would send me some to 1ieKggPzp2DfroFBNie4ib77kHKNbJMkw. Marilyn wishes you a merry Christmas, a merry Christmas, And a happy New Year! |
|
|
|
AntShares looks interesting. But might be difficult to read the source code, it is literally all Chinese to me https://github.com/neo-project/neo/blob/master/neo/Core/Blockchain.csand it is written in C#, which is not well supported on Mac and Linux, unlike Java, which runs everywhere, even on Android phones. But maybe the WAVES block time can be reduced to 15 seconds or even lower, it is only a constant in the source code. But I'm still not sure, if it is a good idea, if a win or loss creates new coins and destroys coins. Maybe using investors would be better for the coin? |
|
|
|
Basic ideas of the coin: 1. fixed number of coins 2. proof-of-stake concept (PoS), without reward, except for the transfer fees So the idea for the integrated gambling, really simple, easy to implement: 1. you place a bet, which is recorded on the blockchain 2. a few blocks later, the hash of the block is used 3. next block, the win or loss is transferred, which is decided by the noted hash of the previous block Two ideas how you can win and lose coins: 1. the coins are created on win, and destroyed on loss 2. there are investors, and 1% house edge (all investors are the house) The idea without investors could be a bit dangerous, because it is possible that someday no coins are left anymore, but this would make the coin really interesting, because the value compared to other coins on exchanges would be very interesting as well What do you think? As previously suggested, I would clone the WAVES platform for the new coin, because it is easy to modify and very secure, because it is written in Scala (compiled to the Java-JVM), so things like buffer overflows etc. are impossible with this language. Possible attack for the gambling algorithm: The gambler has also a lot of coins, so the probability is higher that with the PoS he creates the next block. But if the outcome doesn't win, he would just discard the block. I think this is no problem, because then just another one creates a new block, and the hash would be as random as the first one, but this time the creator doesn't care, if the gambler wins or loses, so the bet will succeed (either win or lose). Drawback compared to online gambling sites like justdice: the bets are slower. With WAVES there is one minute per block. To avoid attacks by blockchain forks, there should be a few blocks after the bet block and the transfer block, maybe 3? This would mean every bet needs about 5 minutes. Would you still use it? |
|
|
|
|
Any news on this project? I might have some more time now, so I could work on it again and try to implement a first version. Might need a bit longer, but should be possible for me to work on weekends on it and clone some existing coin and add some features (I would really like to have integrated gambling instead of traditional mining or PoS), maybe finished until August.
|
|
|
|
|
Thanks, Nxt looks like an interesting coin.
|
|
|
|
|
So would you use such a coin? Sounds like a fun project, I could try to create one, e.g. based on the Wavesplatform.
|
|
|
|
|
Is there a coin, which allows encrypted messages from user to user or to a group? This could revolutionize eMails: If you want to send a message, you have to pay a low fee, so there would be no mass spam. The message could be integrated in the transaction with the payment. And encrypted with the receiver public key, so that only the receiver can read it. With another type of transaction, possibly a bit more expensive, a user could register a clear name to a coin address. If you want to send bigger eMails or attachments, the content could be stored somewhere on the web, and only the (encrypted) link to the (encrypted) content would be sent.
|
|
|
|
|
I'm sorry, I'm out of this project. I thought I could do it, but not enough time, because too many other projects and personal things. I gave all my darkclam to andu, other programmers can take over now.
|
|
|
|
Hat hier eigentlich noch irgenwer einen Full Node am laufen?
Ja, habe ich. Mit meinen 10k ist allerdings kein Blumentopf zu gewinnen. |
|
|
|
Is it possible to create e.g. a Bitcoin asset for Ethereum, then transfer real Bitcoins to it and back to the Bitcoin network? Once it is an asset on Ethereum, a contract based currency exchange could be implemented, without any need for a central server. I think this could be implemented with proof-of-burn: On the Bitcoin blockchain, send it to an unspendable address. On the Ethereum side, tell a contract the address and sign a message with it. The message could be the asset address where the bitcoin is sent to. This might work without modifications of the Bitcoin and Ethereum network and clients, but to validate this, maybe this would mean that every server which runs a ethereum node bitcoin node needs to run a bitcoin node, too, and some enhancements of the contract language. The other way, from the Ethereum Bitcoin asset to the real Bitocoin network, would be more difficult. I guess it would require to implement some kind of special transactions, which checks proof-of-burn transactions on the Ethereum blockchain. |
|
|
|
The MS issue can be substantial. Clam will take a hit when somebody wins big on JD. What about a constant MS increase with an automatic sterilization mechanism for large wins and losses. It can also be adjust for velocity, too.
What is "MS"? Plans have changed a bit. Andu wants to have a normal Dice fast, so I think a good idea is if I start with cloning WAVES (because it has nice and clean code, and I know it already from the WAVES bug bounty program). This means we will have one minute transaction time from the beginning, but no anonymous transactions. I'll read how Dash implemented it and will reserve some bytes or type flags or whatever in the blockchain transactions for it, if necessary, so that it can be implemented later. And I really like the ClamSpeech feature, which I will add to the WAVES clone, that's easy. This will include the Clamour voting system, which will help later for deciding what new features should be implemented, like my realtime network based Dice idea with masternodes and the network itself as the investor. The first clone with ClamSpeech should be possible for me to do in a few weeks instead of a year for a full port of Dash. I suggest that the DC coins from Counterparty can be transferred later by signing a message with your Counterparty address, and then a website allows to transfer the real DarkClam from the genesis account to a new DarkClam address, with the signature proving that you own the Counterparty DC asset. This avoids additional Bitcoin transfer costs for the Counterparty assets, e.g. for a proof-of-burn concept. But if you lost your Counterparty account and you can prove that you own the JustDice account, we can transfer it manually, too (if the Counterparty asset for this associated JustDice account was not already sold of course). |
|
|
|
|
Show Posts
