Things to do in dec:- - Build a multithreaded project in Rust. (Parallel worker-queue processor) ✅ - Create a simple blockchain (similar to Bitcoin). - Complete my Aurx project. - Get a strong grip on solana contracts.

Vs code is the best IDE that ever existed.

Vs code is the worst IDE that ever existed.

done with all x header designs

The moon is actually more important than the sun, since the moon gives us light at night, when it's dark. The sun gives us light in the day, when it's already bright.

AI is shitt I was working on an IoT project, was asking AI for help from the past 3 hours, tried chatgpt, gemini, still didn't get the correct answer. Then, went to youtube, searched for the topic, found a good video on it, got the concept, prblm solved. It took me 20 mins.

Is dhurandhar a family movie? Is the language too abusive?

Now I’ll spend some time, ig until 10 p.m. learning Blender. Idk why, but it’s pulling me in. After dinner, I’ll get back to working on this project.

I’ve been coding for the past 7–8 hours on my blockchain project. I started at 11 a.m. and only took a half-hour break for lunch. Now I’m overwhelmed, the blockchain is getting more complicated as I keep coding, and it will probably take me another 3–4 days to complete it.

Axion update:- I'm currently writing the CLI to talk with my blockchain

Make this comment section a Vibe-coder search history.

If you're a regular viewer of Indian cricket matches, you'd notice that today's streaming quality is comparatively better. It's not due to the cameras, the rsn is, match is being played in Dharamsala, where the AQI is 160. #INDvSA #Cricket

i messed up a bit it this, each miner should be able to mine multiple blocks, so now the block is an Option and i added one more fn to create_block. now the flow is: create_block -> gets_tx_from_mempool -> verifies_tx -> adds_tx_to_block -> mines_the_block

after inputs are consumed and outputs are created, the transaction is officially added to the block. at this point, the block contains only verified. the miner finalizes the block by mining it. this is where proof-of-work is applied.

next, new UTXOs are created from the transaction outputs. for each output, a new UTXO is added to the store and linked back to the transaction ID and output index. this is how ownership of newly created coins is tracked.

once verified, all transaction inputs are spent. each referenced UTXO is removed from the UTXO store, preventing double-spending and ensuring coins can only be used once. this step enforces balance correctness.

before a transaction can affect the chain, it must be verified. the miner checks the transaction’s signature using the sender’s public key to ensure the transaction is authentic and authorized. invalid transactions never touch the UTXO set.

mining begins by pulling a transaction from the mempool. the miner requests the next pending transaction and removes it from the pool so it can be processed. if no transaction exists, nothing gets added to the block.

when a new miner is created, it initializes: - a fresh block using the block index and previous hash - an empty utxo store - a new mempoolthis sets up all the state needed to start mining.

the miner is built from three core components: - block – the block currently being constructed - utxo store – tracks all spendable outputs - mempool – holds unconfirmed transactions

completed this just now now the miner gets_tx_from_mempool -> verifies_tx -> adds_tx_to_block -> mines_the_block thread for in-depth explanation: