Good luck everyone! Thanks again for the game micgoossens! Will keep my fingers crossed for JimboToronto to win.  |
|
|
|
The monthly update:  Guess we're in despair now. I've had to ignore more members in the last 30 days than in the 330 days before.  |
|
|
|
... Zur Frage nach der Rückzahlungsquote: Sehe ich es richtig, dass bisher ein Drittel verkauft wurde? https://www.cryptoground.com/mtgox-cold-wallet-monitor/Wenn die Verkäufe nun zum Erliegen kämen, was angesichts der kurz bevorstehenden CR nicht unwahrscheinlich wäre, dann könnten wir noch so um die 17% unserer Bitcoins zurück erhalten. Grob geschätzt. Weniger als 10% sollten es nicht werden, denke ich. ... Von den ursprünglichen 202185 BTC wurden wohl "nur" 35841 BTC verkauft. Also sollten noch 166344 BTC und damit ~ 82% vorhanden sein. Die im April und Mai bewegten BTC wurden angeblich nicht verkauft. IMHO wurde nie bekanntgegeben, wieviele BTC beim Insolvenzverfahren geclaimed wurden. Wieviele im CR geclaimed werden, wird sich zeigen. Gehen wir von 850k aus, können es ~ 19% werden, bei 700k ~ 24% etc. Also ja, nach Abzug aller Kosten würde ich mit grob 15% "rechnen". Besser als die ~ 7%, die man sich mit Fiat aus dem Insolvenzverfahren hätte zurückkaufen können beim aktuellen "Kurs"... |
|
|
|
A new game! Well, I have no idea what the bottom will be. Guess it'll be around 4979, that's my magic number as of now. Thanks micgoossens! |
|
|
|
They will be trained to... seize Falcons, invade, um, the ISS and nuke planet earth from there in order to colonize it? Not sure, sounds like fun. |
|
|
|
Au contraire. The almighty BaFin just confirmed (more or less) you need a banking licence in order to install a BTC-ATM in Germany. Why do you think there is no BTC-ATM in Germany? I guess the initial costs for a banking licence (100k € or something like that) are the root cause... Most (all?) of the German BTC related "exchange" businesses went to other countries, years ago.  |
|
|
|
Not as entertaining as ChartBuddy, but for your monthly convenience:  Not sure why some thought the USD was superior to BTC this May.  |
|
|
|
Shall we buy Italy with bitcoins? a part of it? They have excellent food over there.
Joking aside they are in a very shitty situation, they basically don't have a government!
no government does not sound like a shitty situation to me I can confirm this assumption. Last autumn and winter Germany had (technically) no government for some months. It was refreshing, the amount of political bullshit discussions has been halved. Anyway, they're back in business and weirder than before. |
|
|
|
thanks a lot ... Just saw these new posts. I could be wrong but wouldn't circulating supply be the current top block? At any rate, I'm not the dev and not quite sure what you are asking? (I am sleep deprived right now which isn't helping..) The question goes to one of the several core devs who showed up here and worked on extending the code, long ago. They changed the block reward, and my post further back explained how I reflected that in the block explorer mined/supply totals. But the last update/s are not included yet, so I am asking for the exact block number/s at which the block rewards were changed. It won't cost me much time to include that information into my block explorer code, I just need to get the numbers right. Not sure it was the latest build, but these source lines might help? https://github.com/martymcfly2015/go-soil/blob/master/params/protocol_params.go#L35 |
|
|
|
Talking about death... one of my Ledger wallets have died. It has a burn mark near the LCD (deforming the plastic case) as if it had internally shortcircuited or something....
Anyone knows if there is some warranty replacement or something?
Has it happened to anyone else?
There is no guarantee of money back, but if you fill out the linked form they might talk to you about the problem. https://support.ledgerwallet.com/hc/en-us/articles/360000608113What to do if my Ledger Nano S has screen, buttons, USB port issues If you have issues with your buttons (stuck buttons, broken buttons…), damaged screen or pixelated screen, or a loose USB port, then please fill out this form. There is no guarantee of a refund or exchange, but this form must be filled out in order to begin the process. Well, I guess I have nothing to lose to try. Thanks! And if they are not willing to replace it  , you might send the dead body for an autopsy and sake of education to Dave, he might be interested. Move your coins to another Ledger first, of course. |
|
|
|
...Stepping back and looking at longer times frames indicates we are right on the edge of a substantial growth period. My recent frustration with short term price action has made me realize that I am emotionally over invested. Time for a break and to do some sailing. dyor and ymmv. Peace.
Well, last month was not that bad. And the near-term future looks fine, if history repeats.  Enjoy your break!  |
|
|
|
New version. Mandatory update.
Thank your for the quick update.  I've updated my node. |
|
|
|
Mich würde interessieren wieviel Bargeld zusammen kommen würde wenn er nach und nach alle Bitcoin Cash/Gold verkaufen würde...
Um die Fiat-Gläubiger zu bedienen: wohl genug. Die bis jetzt* anerkannte Summe beläuft sich auf ca. 45,6 Mrd. Yen. In der Summe sind allerdings die Forderungen der BTC-Gläubiger zum von ihm festgelegten Discount-Preis inkludiert. Wenn 50% dieser Summe den realen Fiat-Forderungen entsprechen (was IMHO viel zu hoch gegriffen ist), hätte er die 200k BeeCash/BTG für ca. 1000 USD unter's Volk bringen müssen. Alle Fiat-Gläubiger wären zu 100% (!) bedient und man könnte sich endlich um die Verteilung der BTC kümmern. Roger & Co. kaufen solche Mengen BeeCash bestimmt zu diesem Discount-Preis. * bla, ongoing investigations, lawsuits until 2033, bla Nunja, BTC-Gläubiger zu bedienen war nie der Plan. Mr. Kobayashi und MK werden sich 2034 auf ihre Inseln zurückziehen und dort den Lebensabend genießen.  |
|
|
|
Something wrong was with time.windows.com server. I found that one of my computers set to 1 hour ahead since yesterday.
Just set computer time and restart wallet, soon all start working.
PoS (with current time) and the pool seem to work again. Thanks for checking Grand Nagus. |
|
|
|
Curiosity question: to my untrained eye, won't the client fix also require forking/checkpoint from where the problem happened (181997?) since currently the UTC timestamps of all the blocks since then are wrong? Trying to conceptualize how miners with the correct time could get back on the current longest chain without kludging the client to mess with how timestamps are agreed to.
Good question, don't know why some nodes seem to run 'one hour in the future' and nodes on the correct time accepted 'future' blocks. Guess to fix this without some kind of update, all nodes have to sync their time and disable PoS/PoW mining for one hour... IMHO it _should_ fork as the blocks from that point are obviously wrong and only 'cheaters' profit.
Indeed, it should have forked, but did not. |
|
|
|
i'm noticing new blocks arriving consistently 1 hour into the future the last couple days.
Just found this in my debug.log. Yes, seems to be an issue with timestamps: CheckStake() : new proof-of-stake block found
hash: 782039806d45cb037e7b07e74ec1637058a8b5959b2d5d2fe348847a5a21b840
proofhash: 0000014da281be708a96c9d89efb2c1707cb6bd7838eb97b8312cac76282e3fd
target: 00000fa8ee0e0000000000000000000000000000000000000000000000000000
CBlock(hash=782039806d45cb037e7b07e74ec1637058a8b5959b2d5d2fe348847a5a21b840, ver=6, hashPrevBlock=74a4e46d294ce8880ab4f52e36a8239f55f5a28b9f3ad1b8439aa5f3de298bfd, hashMerkleRoot=ddc9251240bd996c2fca910c2992d73ad3fafe54012923bfd44a87079e616799, nTime=1524503117, nBits=1d00b1c6, nNonce=0, vtx=2, ...)
...
ERROR: AcceptBlock() : block's timestamp is too early
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: CheckStake() : ProcessBlock, block not accepted Yeah, guess there is something wrong with nTime/ntp.cpp? The following workaround 'fixed' my 'issue', but it's really... shady. 1) Close the UnitedSciFi client. Sync your system time. 2) Disable time syncing and set your local system time to current time + one hour. 3) Enable the NTP server on your local machine: https://www.interfacett.com/blogs/creating-standalone-ntp-server-windows/4) Start the UnitedSciFi client. PoS worked again. |
|
|
|
|
Show Posts
