Trendaavat aiheet
#
Bonk Eco continues to show strength amid $USELESS rally
#
Pump.fun to raise $1B token sale, traders speculating on airdrop
#
Boop.Fun leading the way with a new launchpad on Solana.

Matsu | 松 🧙🏿♂️
On-chain data analysis|Tweet|Full-stack development|@3PDAO
A way to wrap labitbu's UTXO into an inscription
Because labitbu is also indexed through the ordinal protocol - Tracking via ordinals theory, a "wrapped" function can be achieved by constructing an inscription under the same sats, which can display the pattern of the labitbu and it is also a correctly minted labitbu
Wrapped inscriptions can now be traded on @Satflow_, but the risk of trading is that the index of @lifofifo is not guaranteed to be correct, and it needs to be confirmed after the official index and collection (i.e., the index is not necessarily in the collection) is officially launched. And the collection on satflow is also added through the following index, and it should take some time to be added to the package inscription collection after packaging
Although it is a trading plan before the official indexer comes out, it is not recommended to wrap up technical novice and trade on it~
3,48K
The newly added Mint OG and Mint Sleepy seem to distinguish different styles
I can't understand what 😭 it's for



Matsu | 松 🧙🏿♂️2.8. klo 12.39
What happens in every process of playing labitbu?
Long warning, certain knowledge of cryptography and bitcoin trading is required
Labitbu is a small picture of the Bitcoin mainnet starting at 2 a.m. today, unlike previous inscription or quasi-inscription protocols, it relies on the taproot protocol to store load information
The project was developed by @stutxo, the second winner of this year's @PlebFi hackathon, and it seems that the hackathon has the participation of devs from Bitcoin Wizard and Ordinals, and it still has a certain gold content
github repo:
There are three steps when casting a website:
1. Connect your wallet and generate a random labitbu.
2. Transfer to the P2TR address starting with bc1p, the website will transfer 10,000 sats to this address by default;
3. Complete minting, fill in the bc1p address corresponding to the wallet public key in the input box and submit the minting transaction to the chain.
First, connect to the wallet to obtain the public key of the bc1p wallet, and then generate Labitbu based on the public key. According to the json file in the repo, it can be known that there are 8 styles for each labitbu, and the biggest difference is the color. But if it's a 10k NFT collection, the color doesn't seem to be enough to distinguish many labitbu?
Since each labitbu is generated based on the wallet public key, theoretically all labitbu minted by each wallet will be the same style (but occasionally there will be a case where the wallet is minted in a different style during the actual minting in the early morning, which may be due to some omissions or fainting 😇 in the morning)
After the previous step, the generated labitbu is converted into a byte data payload, and the web page builds a control block based on this payload. It's called build here, and the actual control block is [control byte] + [index public key] + [image payload].
In the actual taproot script, the control block is [control byte] + [internal public key] + [Merkle path], and labitbu uses the image payload directly as the Merkle path.
taproot control block related content:
After using payload as the Merkle path and the wallet public key as the lock script, a P2TR address can be generated, which is the BC1P address on the web page, and the process of sending BTC to this wallet can be regarded as a commit in the inscription protocol.
Finally, you need to fill in your bc1p address and wallet to complete the final minting operation. In this process, the front is unlocked with the image payload as the control block, and the public key lock script is used as the output of the redeem script, and the wallet is used to sign and send the final transaction, which is similar to the reveal transaction in the inscription protocol.
The above is the technical content in the process of casting the labitbu protocol, the technical details of the construction of the taproot script and the generation of addresses are not written, interested friends can check the information and take a look
The minting process of labitbu is more similar to inscriptions, but the advantage of inscriptions is that the commit of the minting process does not need to generate a new address as a relay, and the entire minting process can be completed with a single wallet, which is more convenient to a certain extent. However, there is a limitation that the control block size is 4kb, which limits the size of the image load that can be stored.
In GitHub, dev uses a fixed internal public key for minting for easy indexing, so it can be seen that dev also plans to carry out the next step of indexing, and whether it can be implemented for transactions can only be waited.



4,63K
What happens in every process of playing labitbu?
Long warning, certain knowledge of cryptography and bitcoin trading is required
Labitbu is a small picture of the Bitcoin mainnet starting at 2 a.m. today, unlike previous inscription or quasi-inscription protocols, it relies on the taproot protocol to store load information
The project was developed by @stutxo, the second winner of this year's @PlebFi hackathon, and it seems that the hackathon has the participation of devs from Bitcoin Wizard and Ordinals, and it still has a certain gold content
github repo:
There are three steps when casting a website:
1. Connect your wallet and generate a random labitbu.
2. Transfer to the P2TR address starting with bc1p, the website will transfer 10,000 sats to this address by default;
3. Complete minting, fill in the bc1p address corresponding to the wallet public key in the input box and submit the minting transaction to the chain.
First, connect to the wallet to obtain the public key of the bc1p wallet, and then generate Labitbu based on the public key. According to the json file in the repo, it can be known that there are 8 styles for each labitbu, and the biggest difference is the color. But if it's a 10k NFT collection, the color doesn't seem to be enough to distinguish many labitbu?
Since each labitbu is generated based on the wallet public key, theoretically all labitbu minted by each wallet will be the same style (but occasionally there will be a case where the wallet is minted in a different style during the actual minting in the early morning, which may be due to some omissions or fainting 😇 in the morning)
After the previous step, the generated labitbu is converted into a byte data payload, and the web page builds a control block based on this payload. It's called build here, and the actual control block is [control byte] + [index public key] + [image payload].
In the actual taproot script, the control block is [control byte] + [internal public key] + [Merkle path], and labitbu uses the image payload directly as the Merkle path.
taproot control block related content:
After using payload as the Merkle path and the wallet public key as the lock script, a P2TR address can be generated, which is the BC1P address on the web page, and the process of sending BTC to this wallet can be regarded as a commit in the inscription protocol.
Finally, you need to fill in your bc1p address and wallet to complete the final minting operation. In this process, the front is unlocked with the image payload as the control block, and the public key lock script is used as the output of the redeem script, and the wallet is used to sign and send the final transaction, which is similar to the reveal transaction in the inscription protocol.
The above is the technical content in the process of casting the labitbu protocol, the technical details of the construction of the taproot script and the generation of addresses are not written, interested friends can check the information and take a look
The minting process of labitbu is more similar to inscriptions, but the advantage of inscriptions is that the commit of the minting process does not need to generate a new address as a relay, and the entire minting process can be completed with a single wallet, which is more convenient to a certain extent. However, there is a limitation that the control block size is 4kb, which limits the size of the image load that can be stored.
In GitHub, dev uses a fixed internal public key for minting for easy indexing, so it can be seen that dev also plans to carry out the next step of indexing, and whether it can be implemented for transactions can only be waited.



23,55K
Finally waited for $FSPK to come out of the market, which is the only project 😭 that has made money recently


SparkSat - wallet, tool for spark9.7.2025
Today, the Sparksat trading market Beta is officially launched.
Currently, $FSPKS and $SNOW tokens are supported, and more tokens will be supported successively.
The market is in its early stages, and there will definitely be some issues or instability. Please try not to exceed $1000 per order to avoid order delays caused by RPC or other transfer reasons. Have fun.

731
So what was 🤡 my previous 1 sats/vB merge

CG ◉ #3456621.6.2025
Blessed are the users who didn't merge the abandoned Satoshi before!
Transactions with sub-1sat/vB rates are becoming popular, especially good for merging the discarded UTXOs that are occupied in the merge wallet, the previous 1sat/vB rate, which required a gas fee of about 20%, can now be reduced to 10 times the cost of withdrawing and merging.
For example, merging 1000U of abandoned occupation Satoshi used to require 200u of gas fees, but now it only costs 20U with a 0.1sat/vB rate!
And it is said that UniSat is working on low rates~
5,16K
Johtavat
Rankkaus
Suosikit
Ketjussa trendaava
Trendaa X:ssä
Viimeisimmät suosituimmat rahoitukset
Merkittävin