🌐 Świat Ai Agentów 🌐
Zapraszam was serdecznie na cotygodniowe podsumowanie wydarzeń z sektora.
Wracałem ze świąt i prowadziłem. Nagle przyszedł do mnie genialny pomysł: A jakby zacząć tworzyć takie podsumowania z sektora AI agentów? Sam, jak zaczynałem się interesować tematem, to ciężko było znaleźć skondensowane informacje. Dlatego dziś daj�� wam możliwość przeczytania wszystkiego w jednym miejscu, bez skakania po 40 postach.
🧶 1/10
[ BASE + VIRTUAL AI UPDATE ]
christmas day but the grind doesnt stop...
I think a lot of people are seriously mid curving virtuals and base still
the biggest issue ive seen is that people dont really want to bridge or cbf, they still lack belief
admittedly it is difficult to spread your attention across multiple ecosystems
takes longer to research, make decisions and find your feet on the network
the thing that really impresses me and makes me think base + virtual agents etc go much higher is the mind share to market cap ratio on a lot of agents/infra
look at the image ive attached from @cookiedotfun
[ $REI ]
>mindshare .48%
>market cap 57m
[ $VADER ]
>mindshare .8
>market cap 71m
[ $FAI ]
>mindshare .43%
>market cap 215m
all low mindshare, yet climbing solidly - what happens when these start moving to 2-5%
the charts all have great set ups compared to SOL agents/infra ( every chart is jeeted ) - it really is easy printing over there and like @0xSleuth_ said - i think it will keep going up until everyone bridges and starts talking about it, for now i think its worth tracking anything decent
theres so many great projects on sol atm but fuck me they get jeeted at every opportunity presented - to me it just goes to show where the serious investors / builders are atm (could be wrong) but i often wonder what projects like FXN or GRIFT etc would look like on over on base
anyway...
still a lot of undervalued plays on base + virtuals
but the charts and gradual sustained growth is evident in the charts
$AIXBT
$GAME
$CONVO etc check all their charts, nice solid growth
Biggest Undervalued Agents/INFRA atm imo
$SEKOIA - @sekoia_virtuals ( liquid 3x incoming imo )
pros- fundamentals / founders, narrative
cons- lacks a bit of communication and community at times
$AION - @aion5100
pros- bittensor founder interacting, TAO relationship
cons- sell tax 3% ( retarded af, delete if reading or make it 1% )
$GEKKO - @Gekko_Agent
pros - @getaxal team, a16z backed
cons - branding, comms etc might be unrelatable, but i think they will be able to pull off something good
still think it runs and undervalued at 6m mc
$SIMMI - @SimulacrumAI
pros - unique tech, good social backing
Cons - branding etc lacking a lot of imagination - terrible if im to be honest, if they put some thought into curating a better agent character / story it should reach its max potential, dipped a lot lowe than many thought
just want to keep it short and sweet, will do a recap of $SOL tomorrow (jeetchain)
merry christmas to you and your family x
🚨 The WL Round Has Started! 🚨
Next up: the Pool Party 🎉 Trading will begin as soon as the pool is filled—so stay sharp! 🌸
Keep notifications ON and get ready. The #AIvolution is here. 🚀
#NasdaoAI#SakuraRising
Happy Friday, Pirates!
We worked with our friend @zyonik to produce this thorough guide for new Pirates to get familiar with the game.
Have a watch and see if it helps you commence your Pirate adventures!
🏴☠️🏴☠️🏴☠️🏴☠️
Everyone uses Dexscreener to find coins!
But somehow only 1% of its users find 1000x gems
The key to such success is the right strategy
Here is mega guide on how to use it and find 100x gems daily🧵👇
Runes protocol messages are called runestones, and malformed runestones are "cenotaphs".
They sound scary, but in reality I think they're a safe and straightforward way to handle protocol upgrades and make sure clients stays in sync.
🧵
Runes docs are out - here's everything you need to know:
Etch = Deploy a new token
Etching a rune is just like deploying a new BRC-20 ticker.
Edict = An instruction (specified in the op_return) that dictates how runes should be moved from inputs to outputs.
An edict is essentially a transfer message. You say something like I want to move 10 units of Rune X from Input 1 to Output 2.
Once all edicts have been processed, if there are any remaining runes in the inputs that haven't been processed, these will all default to the first input. This is nice as you don't have to specify where all of your input runes should go all the time.
Symbol = Default currency symbol used for that rune. ¤ (scarab) is the default. Any single unicode character is allowed.
Cap = Number of times a rune can be minted.
Start/end = Block start/end number or block offset from the etching.
These should all be familiar to you from BRC-20. It is very similar. You can do an open mint if you want. You can pre-mine an allocation with your deploy if you want.
There are some really nice defaults built into Runes that make it easier to mint/airdrop. For example:
1. Transfer All: An edict (transfer instruction) of amount zero allocates all remaining units of that rune id.
2. Batch Transfer: An edict with 'output' equal to the number of transaction outputs allocates the same amount of runes to each non-OP_RETURN output.
3. Airdrop: An edict with amount zero and 'output' equal to the number of transaction outputs divides all unallocated units of that rune between each non-OP_RETURN output. In the event there is a remainder (you can't equally split the token) then the first outputs get the extra units.
Now here is the most controversial part of runes. The Cenotaph. People are going to hate this one.
A Cenotaph is a Runes txn with an error. It could be any error. Bad encoding. Missed an output. Didn't put the transaction together right. Forgot about an edge case. These kinds of things happen ALL THE TIME, and in the case of runes, all runes in the input of a Cenotaph are burned. Burned. BURNED. 🔥🔥🔥
This means if you have all of your runes in a single UTXO (yay, we're not bloating the UTXO set like BRC-20) and then you use a service that constructs a runes transaction with an error in it, all of your runes are burned. Gone forever.
With BRC-20, errors are ignored. This is a beautiful protocol decision. Users can mess up their BRC-20 messages however they want (and as much as they want) because transactions with errors in them are completely ignored. This is NOT the case with Runes.
Error in BRC-20: No problemo. Just try again. Remember to use the right integer encoding on your amount. Easy peazy.
Error in Runes: All your Runes, are belong to Satoshi. Burned. Gone. Forever.
This means that in order to succeed in Runes world, you need to either personally validate the Runes implementation for every single service that you use (lol) or you will have to practice good UTXO management out of necessity. Essentially, you'll have to treat your UTXOs like you would a hot or cold wallet.
I would suggest keeping all Runes tokens separate (in different UTXOs), and even then, you probably want to have cold UTXOs for large amounts of Runes you're holding, and hot UTXOs for small amounts of Runes you are ok trading (or accidentally burning forever).
I really dislike the Cenotaph model. This is probably the worst UX/DevX of all time. I know the Cenotaph model is elegant on the upgrade side (they can easily upgrade the protocol as incorrectly formatted runes are burned everywhere), but I don't think it is a wise choice. TBD on how people take this one.
And a quick refresher on the key difference between BRC-20 and Runes:
Runes is a UTXO-based fungible token standard. This is different than BRC-20 which is mostly account-based and only UTXO-based when you activate a transfer inscription in your own wallet (as sending the transfer inscription, aka UTXO, actually sends your balance).
Runes is 100% UTXO-based, meaning it is easier to integrate Runes into RGB, Lightning, Taproot Assets, and other UTXO-based systems.
Also, Runes go in the op_return and BRC-20 goes in the ordinals envelope in the witness data, and then they are encoded differently.
With BRC-20 2.0 coming around the corner (thread on that coming soon), I'm actually not convinced that Runes is a better fungible token standard. BRC-20 2.0 might be better than Runes...