|
If 1GB RAM isn't enough, I'll probably just give up the VPS and stop running a node. That would be a shame.
|
|
|
|
I've been running bitcoind on a VPS for a few months. A few days ago it crashed. Since then every time I restart it it runs out of memory within a minute or two. The VPS has 1GB of RAM and I'm not running anything else. Here is exactly what it says: ************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in AppInit()
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
The last time I was successfully running it I had version 0.9.1. When it wouldn't restart I upgraded to 0.9.2.1, but the same thing happens. Can anyone help? Thanks! |
|
|
|
|
Wow. I didn't expect so much drama when I decided to catch up on this thread.
I'll bet those mathgate.info people are glad their treasure hunt sucks. Having a successful treasure hunt looks like it just invites problems.
|
|
|
|
|
I tried something based on the information before the palindrome hint. It didn't work, but might give one of you a good idea.
The string z69JZqlJn862D1ndx7oLVEMmV0lP1zewEeUCrsI7Roahzpeny7P
as a base62 number (0=0,A=10,a=36) gives the base 10 number
2544602690811658317353678523595957659918682616065482344224953077374885296327773 7222433136147
or in hex
C7DDF8E4AD3B8CE425A8DB02114895F6F8FB6E6E3C49CB4EA505D3A7330B90049DED51B3DE13
This is a 304 bit number, i.e., 38 bytes. The sha256 of these 38 bytes gives a 256 bit number (32 bytes):
E1527C1694D54D96DF96D6B735AC8AB0781CF214DCDF2F6C8F44B7B9EB331999
The sha256 of these 32 bytes gives another 256 bit number (in hex):
9F673A96065872003EC70BF2C43B77DD64F4E63C9321EAA05548070DBB972D9A
This 256 bit number (like most 256 bit numbers) is a private key. The WIF version is this:
5K2VKhkQPvPKX6sKDsMBZSPeN6iBRyfynK2wtV4HoYEzcmiUdQP
The corresponding address is not the one we want:
112nVF5b2NPKbVqDLYQDzcP5hZvFFuXC1t
|
|
|
|
Update 6/28:
Do not rely solely on Users for solves, double check solves for user errors: #checkuser404
OP made no mistakes.
confirmed:
- Public Address has been solved: 1HXUobwcB19cGDrghuh42HDdJdJvrJUEra
- embedded morse code: "They cannot attack what they DO not see," has been solved.
No more clues. Good Bye and Good Luck.
Oh god. This shit is getting tense. Where is this message from? OP, it has been updated. Thanks. Based on the checkuser404 clarification in the update, I'm even more skeptical of my YT/Snow Crash hypothesis. Oh well. Given that I'm now seeing Cody Wilson and Amir Taaki when I close my eyes, maybe it's time I stepped away from this for a while. |
|
|
|
Update 6/28:
Do not rely solely on Users for solves, double check solves for user errors: #checkuser404
OP made no mistakes.
confirmed:
- Public Address has been solved: 1HXUobwcB19cGDrghuh42HDdJdJvrJUEra
- embedded morse code: "They cannot attack what they DO not see," has been solved.
No more clues. Good Bye and Good Luck.
Oh god. This shit is getting tense. Where is this message from? |
|
|
|
|
Hmm. The thing is: I recently reread Snow Crash because it was mentioned by Patrick Byrne (of Overstock) in his Amsterdam bitcoin conference speech.
Near the end ...
Oh, possible spoiler alert in case you're planning to read the book for pleasure.
.......................................
Near the end, Hiro Protagonist uses a program he wrote so that his "avatar" in the "Metaverse" is (effectively) invisible. He does this to avoid being attacked.
This lines up very well with "You can not attack what you do not see."
I'm a bit skeptical still of a real connection to Snow Crash, but looking again at the image I'm finding ways to spell the words "snow" and "crash". Enough letters are there to spell it on the first three lines (sort of).
|
|
|
|
Who keeps adding all this money to the prize? Someone has some deep pockets I'm guessing  Pretty cool puzzle though. I was wondering the same thing. This is a huge prize. Who us funding it? And why? Just for fun? (not complaining hehe just curious) Why? I'll bet a lot more people are familiar with this artist and her work than were a week ago. If that was the goal, it's clearly been successful. |
|
|
|
Alice, FFS girl, can't you see we are dieing for another clue? Pleeeeeezzzzzz Thank You  We Love you I'm fairly certain that we are "Alice." The artist is YT. To be more precise, the artist's username here started with YT and I think YT was her twitter handle. YT is also in the image in a way that can be interpreted as a signature. The "CHCKUSER" message made me wonder: perhaps the name YT is relevant. My guess is that it's taken from a major character in Snow Crash. (That's why I mentioned Hiro Protagonist in my first post in this thread.) In Snow Crash, YT stands for "Yours Truly". I hope this helps. |
|
|
|
The following addresses have all received coins from 1BoRHtJva2L9YyqB1aS1zqgFUjjftNuZtJ:
1sosB9wN5ij84GKfo6Xxx8FWyh5fPXVXu
1rEDGrNbuqqtbJU12XiU4hvmfM4XaQVcD
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz
-snip-
404 5 1 O 9 # CHCK USE 404! DOB BBD DO NOT DHTTP
thanks for adding From what I can tell Alice is telling us is not a URL? Also, I have not made clear what PB stands for but then again maybe it doesn't matter. I think some of this is wrong. 0.00100001 should be !, not B. 0.01000010 is B. Again, I got [0.00404][0.005]@O[0.0009]#CHCKUSER[0.00404]!DO!!!"DONOT"HTTP |
|
|
|
|
[0.00404][0.005]@O[0.0009]#CHCKUSER[0.00404]!DO!!!"DONOT"HTTP
This is the message I decoded from the transactions from
1PBsAHYQoczQh6mufENsR4tCkKToQKjMzz
The values that I couldn't convert to ASCII are the ones between the brackets [...].
Does anyone know how to interpret this?
|
|
|
|
I also meant to give the lisp code I'm using. Again, it's the bip0032 implementation available at github. (I gave the link earlier.) Then in lisp (sbcl) I do this: (defun check (k)
(multiple-value-bind (x y) (smulp k xg yg) (when (equal (btcaddr x y) "1HXUobwcB19cGDrghuh42HDdJdJvrJUEra") (format t "I'm rich! ~d~%" (btcwif k)))))
(defun f (x)
(format t "Trying ~d~%" x)
(multiple-value-setq (k c) (master x))
(let ((dl nil))
(dotimes (j 10) (multiple-value-setq (privj cj) (ckd k c j)) (push (cons privj cj) dl) (check privj))
(dotimes (j 10) (multiple-value-setq (privj cj) (ckd k c (logior (ash 1 31) j))) (push (cons privj cj) dl) (check privj))
(dolist (d dl)
(setq k (car d) c (cdr d))
(dotimes (j 10) (multiple-value-setq (privj cj) (ckd k c j)) (push (cons privj cj) dl) (check privj))
(dotimes (j 10) (multiple-value-setq (privj cj) (ckd k c (logior (ash 1 31) j))) (push (cons privj cj) dl) (check privj)))))
(f "S7ovY8tcakz3CmiuN2rh5OP4iDcIxbMy2nLi31nmtHdEhirLbwb5yufe3TCSvjwoAUrk9FzRe7aeJ62YTo6ABDiFt")
|
|
|
|
I had a new thought. Dark Wallet uses HD Wallets/BIP32 according to the Dark Wallet FAQ https://wiki.unsystem.net/en/index.php/DarkWallet/FAQ. It's possible that the address is in one of the chains starting from a certain master seed as described here: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#Master_key_generation. It might be this master seed that we're looking for. I took the string consisting of (what I think are) the non-dot characters without the address characters: S7ovY8tcakz3CmiuN2rh5OP4iDcIxbMy2nLi31nmtHdEhirLbwb5yufe3TCSvjwoAUrk9FzRe7aeJ62 YTo6ABDiFt and used this as the seed. I then looked at the first 10 addresses at the root level and then at one level deeper. No luck. I also tried some variant master seeds, but have had no luck there either. I haven't tried using the information in the colored dots, and I don't have an idea how to use them. My guess is that the colored dots are not important, since there are colored dots between the characters of the address and they play no role there. I suppose it's possible that the dots give some information about where in the HD hierarchy to look, after you start from the right master seed. |
|
|
|
This has roped me in today too, but I'm hitting a dead end. Clearly I'm no Hiro Protagonist. Here are some notes in case it helps someone. Since the address was given in a fairly direct way (1HXU...), my first thought was that the private key is given in WIF/base58 format somehow using letters and numbers in the picture. However, there's evidence against this. There are characters O (capital o) and I (capital i) which do not belong in base58. A WIF private key would start with 5 and, if I'm not mistaken, would continue with H, J or K, and be 51 characters total. There are two fives in the picture but neither is near an H, J or K. One of the 5s is near a small h and a small k, so I considered reversing the capital and small letters (unless it leads to a letter which is not a base58 character). Doing this makes it possible to get started with something that might be a WIF private key (e.g., 5KAH...), but at that point it feels like I'm grasping at straws to force there to be a WIF there. I'm using some lisp code to test whether something is a private key. It's my implementation of bip0032: https://github.com/kronarev/bip0032sbclIt doesn't actually have a function to check if a string is a proper WIF key, but this can be easily defined after loading the relevant files: (load "config")
(load "secp256k1")
(load "hdw")
(defun checkwif (w) (let ((x (frombase58 w))) (and (= (ash x -288) 128) (let* ((k1 (ash x -32)) (sh1 (sha256num k1 33)) (sh2 (sha256num sh1 32)) (sh24 (ash sh2 -224))) (= sh24 (logand x #xFFFFFFFF))))))
I also looked at the sources of the jpg itself and the file she linked to as being relevant. (It said view source on all files.) I didn't find anything though. No onion links and nothing that said "Hey, here's the private key." It's of course possible I missed something. I suspect there must be something in the source. I haven't tried taking colors into account. Good luck everyone. |
|
|
|
|
I think this is an interesting idea and would like to try it out. I'm having trouble getting it to work under Debian/Tails. I got the source code, but ran into trouble trying to compile it. I don't want to spend a lot of time on it, so I'll just check again in a few weeks and see if it works then.
I don't think there is anything nefarious about the idea though. On the contrary, it's probably the most fair distribution of a proof-of-stake coin to date.
|
|
|
|
There's also a way to have your own "metablock chain" containing arbitrary data that is timestamped and secured by the Bitcoin block chain. It uses standard transactions (no OP_RETURN), does not destroy coins and does not increase the number of unspent transactions. I explained it in January here: https://bitcointalk.org/index.php?topic=411974.0 |
|
|
|
|
I will be there. Looking forward to it. I've neglected to get on the forum lately, so I now realize I missed a few posts. @daybyter and @Rakete4: It was good to meet you guys last time. @daybyter: Hope you can make it today. @Rakete4: Hope to see you in June.
|
|
|
|
Hallo! Werde am Sonntag auch erstmals zum Stammtisch kommen. Gruß bis dahin,  Rakete4 Sehr gut! Es klingt wie heute ein Gut Stammtisch mit neu Leute wird. Sehe alle in wenige Stunden. |
|
|
|
Ich weiß leider immer noch nichts neues, aber ich hoffentlich kann ich kommen - bin nämlich schon gespannt auf Trevi... Hoffe bloß, daß die anderen es auch finden
No news (yet) but hopefully I can make it, I am excited to check that Trevi place of yours... I just hope the others will find it as well
Edit: Oh, Freude! Sieht so aus, als ob das doch mit mir klappt. Hurra!
Oh joy! Looks good, can be there. *yay* Great! See you in a week. |
|
|
|
|
Show Posts
