It’s my anniversary with my wife this weekend; and I’ll be tied up all next weekend too.

I’m thinking I might find some time tomorrow to review the code base. Maybe mid-week next week if not. Have to balance the fiat job too 😵‍💫

Once I can see how the equations are being used then I think we can really make some headway on all of this.

So with regards to cumulative nonce temperature, my postulate is that like Bitcoin’s 21M, Kelvin is bounded by Planck Temp, think of it as the Planck “supply”.

So we can measure time a few different ways with Bitcoin, the accumulation of energy, the accumulation of information and the accumulation of Kelvin. Each block is finite addition. The nonce temperature is supposed to represent Kelvin that is irreversibly committed to block. So long as the block persists, the Kelvin remains pegged to that block of time. As we sum up the chain of accumulated blocks of Kelvin, the sum of the relative temperature should never exceed 1 and if we measure it in Kelvin, the sum should never exceed Planck Temperature (think the sum of all Bitcoin should never exceed 21M).

This is a postulate, if I am wrong, I will need to reconsider the meaning of the nonce temperature. It looks like from your graph it does exceed 1, so I will have to speak with Nick to see what he thinks here. It might not make sense to do the cumulative.

I wish there were more people here to discuss the physicsc, mechanics and equations with.

“Mempool sampled at 100 rate” can you explain what you mean by this?

Nonce temperature also appears to be wrong.

At Genesis pBlock =1, ln(1)=0, so UBlock=0 despite Tblock=1.

When we plug in 0 for Unonce, the only valid temperature to produce 0 is 0 since difficulty is 1.

This is interesting nonce temp=0, block temp=1 at genesis. Bitcoin starts its time at a 0 energy state. This logically checks, no POW was done for genesis block since it was premined. No time had accumulated yet a Block 0 (Genesis). It’s defining the anchor for all future state transformations.

Just a heads up, it appears you are missing the Genesis Block, t=0.

U=0 (internal energy) , Temperature = 1 and time=0

@Michael Dunworth Hey Michael, what do you think of this so far? Any feedback?

Yes we are observing the genesis of a computational universe. I wouldn’t call it a big bang, but a structured beginning. We are observing creation from the opposite side of the temporal boundary. Bitcoin is a conserved bounded totality of time. We are the architects.

Once we have the energy of each block we can compute the mass of a block of time using Einsteins E=MC^2.

We can also compute the gravity of time from each block’s mass.

From there you can get the chains total mass, ect.

Those can be added as you see fit. I’m currently writing something as we speak, so this is all I can give you for now🧡

Nonce Tempersture would be wrong if anything upstream is wrong since it’s the last computed value in the order of operations.

We don’t know the nonce Tempersture until we calculate the Shannon entropy of the block, the block temperature and the block energy.

Then by conservation: block energy = nonce energy, we can use the nonce entropy to solve for the nonce Temperature….hope that makes sense.

The nonce temperature will also be a relative measure of temperature between 0-1, if you want the nonce temperature in Kelvin we will need to multiply the nonce temperature by Planck Temperature.

Both the Nonce Temperature and Block Temperature are relative and dimensionless scalar ratios btwn 0-1. If you want the domain specific measure, multiply by TPlanck or Bitcoin Supply.

Charts are starting to look good. I haven’t had a chance to review the code yet to see if the equations are being referenced correctly.

I can’t make out what is going on with the block temperature. It should always produce a value between 0-1; 1 being the genesis state since it’s always measured versus the supply of satoshis.

Each block has a subsidy value, a fee value and current supply. The subsidy is the floor temperature which cannot be breached, fees are the additional heat above the floor.

Mentally, I find it easier to start with Genesis and work forward in time since early blocks have few transactions if any.

When I was trying to build charts originally I was using a CSV and found some errors in my data, so I quit trying that route and needed to do a full node integration which I’m still working on.

Here is an example of a chart I came up with using Jupyter + the csv 😵‍💫 you can see a few errors, but this is what the chain temperature should look like. Spikes from the floor are fee spikes.

Keep up the good work! Keep pinging me as you can. Nick and I spoke last night and we’d love to have a conversation with you to see how we can help.