please be aware of this report summary from Bitcoin Optech, with link to the original source:

https://bitcoinops.org/en/newsletters/2025/06/06/#quantum-computing-report

for a discussion of the state of quantum technology, potential risks for Bitcoin, and, most important, some practical recommendations.

I think the most important piece is to immediately begin a discussion about how a general consensus should be reached on how to implement a quantum-fix when it becomes necessary.
It wouldn't help if there are technical proposals available, but a prolonged civil war about how to implement would delay them, possibly beyond a real quantum attack.
Remember the blocksize and segwit discussions? QT could make a lot of progress in the amount of time it took to resolve these issues...

Recommendation of the authors is:
within 2 years, develop a technically sound short-term fix, and reach agreement within the whole ecosystem on how to implement it quickly in case QT progress makes it necessary.
within 7 years, have a quantum-resistant Bitcoin fully developed and deployed (they expect a possible quantum threat between 2030 and 2035)

While one can debate the author's timeline assessments, I think it makes a lot of sense to at least begin to prepare the way to implementation right now.

With this issue still not resolved, and Core 29 release candidates already out there:

Where is the proper place to look for immediate notification when a new Core version (main or update) is relased?

seems like the anser is no longer "here"....

Several Swiss banks tried just such a scam with "unclaimed" Jewish assets from the time of the Holocaust. Didn't end well for them.

DannyHamilton just explained that there is no universal timestamp.

And even if I went your way, it would only make the mystery much deeper: If really most empty blocks are found within a second, and we have about 1% empty blocks on average - that would mean the probability to find an empty block within 1 second is 1%. Not 1/600th of the average block time of 600s.

Do you imply that different mathematics of difficulty apply to empty blocks?
If yes, why would any miner "waste" 99% of his computing time on finding full blocks, when mining empty is so much easier?

I was not looking at the timestamps for my estimate. If average block time is 10min (600s) , then a quota of roughly 1% of empty blocks found points to an average "empty block mining time" of 6s. Rough guesstimate, of course, but still way beyond the actual "assembly time" for a full block header.

From the previous answers (thanks!) I get that many widely varying economic factors come into play for a pool's decision on how long to keep mining the empty block.

Hi,

maybe someone can shed light on a question I am wondering about.

Empty blocks are usually found very quickly after a "normal" block. The explanation I have heard most is that miners will start mining an empty block while they still assemble the tx and merkle roots for the next "normal" block. Sometimes they get lucky in this short time.
The frequency of empty blocks would suggest this "short time" to be around 5 seconds, plus/minus 50% or so. This sounds like an awfully long time to get the normal block preparation done.
Is there something I am missing? Is the chance to catch the block reward with an empty block good enough to always mine on it for several seconds?

thanks for any insights

Hi, hope someone here can help me.
On bitcore.cc, I claimed the BTX from one of my bitcoin addresses to an invalid payout address (in fact, I copied the message signature there by accident). I got an error message about the invalid address. When I try to claim again, the system tells me that these BTX have already been claimed , right after I enter the original address. Is there anything I can do to "reset" or edit this claim?

Danke an alle,
ich hatte auf einer Börse noch etwas Waves-"Kleingeld" , das ich jetzt als "Lösegeld" auf das Waves Lite-Wallet geschoben habe.
Sollte für die Gebühren reichen, falls ich die Incents doch mal flüssig machen will...

Danke für die Antwort, aber hier spricht ein Waves-Anfänger.

Was ist mit der Waves Exchange gemeint? Google zeigt da mehrere Alternativen...

Das Waves Lite Wallet habe ich, kann auf dem aber keinerlei Orders platzieren. Kriege immer ein besonders hilfreiches "ERROR Order was not placed"
Kann das daran liegen, dass fees immer in WAV angezeigt sind, ich aber Null WAVs im Wallet habe? Nur die ICO-Incent und IncentCoffee...

Muß ich da erst WAVs auf einer anderen Börse kaufen und überweisen, oder bin ich völlig auf dem falschen Gleis?

Noch will ich nicht aussteigen, aber mich zumindest mal informieren, wie das denn überhaupt geht.
Meine mit Waves beim ICO gekauften Incents werden mir auf https://www.incentloyalty.com/ico angezeigt.

Aber was kann ich dann mit denen machen? Wie kriege ich die verkauft oder auf eine Börse (zB openledger) verschoben?

Ich finde da keinen Knopf dafür auf dieser Seite...

I know, I should have mentioned this, but I'm on Windows... forget reliable symlinks there...

EDIT: tried it, it will read the data throug a link when first opened, but then write out data to the hard-coded %APPDATA%... again instead of through the link.

thanks for 1.1.0 and a feature request:

I like to keep my cryptocoin data directories on an encrypted drive, so it would be nice if byteball was flexible in where it puts it's data directory.
A start paramater like bitcoin's -datadir=... would be just fine for a start.

Judging by the zero replies, I assume that, at this point in time, there are no byteball-based applications or services.
Any announcements I may have missed, anything in the pipeline? Not that I can find anything on byteball.org...

Shouldn't (early) applications play a role in the discussion of potential value and distribution schemes?

Maybe I have missed this,

but is there actually already a way to spend Bytes and use the database?

I don't mean trade - I mean, e.g., I totally trust this thing to be around for the next 50 years, and want to store an important document (say, my will, as a 1MB PDF-A) in it's database instead of paying a notary.

How would I have to go about doing that? The whitepaper describes what kind of data structures to create, but what are the actual steps to do so, where do I send them (from the wallet??) and to whom?...  How would I keep a local documentation of the database entry, how could someone (after my untimely demise and loss of my computer passwords) retrieve or verify this document?

The distribution scheme seems to promote holding (or trading) the coins, so does the discussion here.
Totally understandable, but I am also interested in it's intended use...

Done, and gave it some tyme to sync - didn't change anything, though...

I am running 0.7.1

Hi,

am I just too dumb to find the toggle switch or did I not receive Blackbytes?
this is my balance from the original distribution, no other activities were done on this wallet.

any hints about what I can do?

https://s28.postimg.org/ctu04b7x9/image.jpg