Caught this thank to a new chart

nostr:nevent1qvzqqqqqqypzp963hhzdztlkunxxkcd3qtm3u3z77fzmeqct7s90v4n2dgjxzd7xqyfhwumn8ghj7ur4wfcxcetsv9njuetn9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uqzpfy87f2lazhmmaf7pjqkkg96npeugq950gezzapj030xz5ry0cres9adcr

🤦‍♂️

#Bitcoin

and updates now take 5 seconds (could still be improved) instead of several minutes

nostr:nevent1qvzqqqqqqypzp963hhzdztlkunxxkcd3qtm3u3z77fzmeqct7s90v4n2dgjxzd7xqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmwdaehgu3wdehk7mn9wvhxxmmd9uqzpqm8xzrrdsl5agvd2jx57vmt2tn4r3k7pkdnwa8apm9ak763lz0u45ah3z

getting closer to chart parity with kibo v0.5

#Bitcoin

Respect 🫡

Congrats!

and the other two are the dup txid, of course !

genesis output is unspendable, 2 to go

So close yet still not correct, have 3 too many utxos

I did:

total output count - total input count + total coinbase count - total opreturn count

did I forget anything ?

Thank you !

Yes when DCAing time in the market is very important

dca classes

lump sum vs DCA returns over time for multiple timeframes

#Bitcoin

All good !

Just wasn't obvious that you were looking at a moving average

Thanks for letting me know

Interesting, my chart is the sum of outputs per week but still shouldn’t have such a massive difference, I’ll investigate

v0.0.35

weekly sum of op_return output count

#Bitcoin

To further incentivize folks to try BRK, the latest release comes with yet another disk usage optimization.

You can now choose between eager and lazy computation.

The eager mode will compute everything and store it on disk which is the preferred method if you want speed.

The lazy mode will, on the other hand, compute data each time it's requested.

This only applies to datasets by transaction, type, input and output.

Datasets by height or higher (date, week, ...) are eager as computing them on the fly would be very costly with little to no benefit.

Right now computed datasets take 200+GB when eager and 5+GB when lazy, so quite the difference and this is in raw mode without compression.

Some numbers when fetching 10 000 values:

Eager:

txindex_to_base_size: 324.625µs

Lazy (2 dependencies, 1 level deep):

txindex_to_weight: 1.413ms

Lazy (4 dependencies, 3 level deep):

txindex_to_fee: 20.285ms (1st call), 8.968ms (2nd call)

So it's slower but not the end of the world it should be good enough for most use cases

#Bitcoin

Fish 4+ (Rust version), same reason as Ghostty, fast with great defaults

Ghostty, very fast with great defaults

Warp is peak fiat world, you have (had ?) to log in to use it