STOIC Rhys - $HOSKY rugpool CSPA CNC ArmAda

I just registered as a DREP: drep1rsmldjj7vg9a9r5lqsegynzw03yyfhzdqwfs8fq3ctsk2rwjlfy I will not support burning the treasury, I will not support using the treasury to fund native VCs I will support open source tooling that will help teams and projects launch on Cardano

AFAIK the Gerolamo proposal is the lowest in ask between the alternative nodes It covers 1 year of development for 3 highly skilled FTE dedicated to the project. Among all the alternative nodes, it is the one with the highest potential in decentralising applications

I had lots of help from these nice people also, I hope the book does their work justice 🙏 @MicroProofs @rvcas @_KtorZ_ @StoicPool @YetAnotherAiGuy

I just voted no on net change because it is too high. It’s easy to put large withdrawal requests in when there is a large budget. We need to manage OUR treasury responsibly or we will end up with a more expensive Catalyst, with little to no results

@ChristopherSeuc @masatoalexander You’re right on point there 💪 it’s good to do a mix for balance as each hand position recruits muscles differently, but wide overhand is more lats

@masatoalexander Not for your back...hands wide hands facing the bar...squeeze that back....but iunno too much better get @StoicPool to weigh in.. HEy Rhys!

was asked if I can do any pullups. don't really do them (and prefer chinups) - most consecutive i recall doing was something like 3 or 4, so decided to give it a shot. looks too fast and maybe too much kipping, my bar is pretty low so have to keep legs bent, any of these count?

@itzdannyADA @levvywifhat_LWH @aiken_eng It’d be so easy to make it able to gift any value, even multiple NFTs 🔥

@levvywifhat_LWH @aiken_eng @StoicPool just ada currently, maybe we need a V2👀

my first @aiken_eng contract on cardano. just a simple gift card where creator locks funds and mints NFT, NFT can be sent to anyone and then redeemer burns NFT to unlock the ADA. huge shout out to Rhys from @StoicPool for all the help you've given while I've been learning. if you want to check it out, site is here: next-auth-mesh-sdk.vercel.app code is here: github.com/itzdannyada/ne…

Good afternoon!!! São Paulo theater 🎥 We should be using #nft as tickets @StoicPool

@jonahkoch @bobasfk @elraulito Better to look at the Aiken course done with CF as this is PlutusV2, but this does cover transaction building too so still helpful

@bobasfk @elraulito @StoicPool has good videos on YouTube. youtu.be/GiKnbrKHDkg?si…

whats the best place to learn how to start coding on cardano? a friend is interested, gave him @elraulito github, what else?

@MicheleHarmonic Ah what a muppet 🤣

@StoicPool Wasted opportunity to call it DEEZ

With all this talk about programmable tokens recently on Cardano, with various designs and specs coming out, I was thinking of a simple way to implement/develop this concept that can allow more flexibility across different assets 👇

@elraulito Totally agree Yeah it requires handling assets instead of having a ref input or separate account script per user, either way some calculation is required offchain. I’m going to build out examples of 113 & 143 to compare complexity & efficiency so we can understand tradeoffs 🙏

At the end of the day the approach is similar but different implementation You propose to put the ownership in the assetname instead of the stakeCredential of the utxo I think it's easier for current defi to have tokens with same name otherwise you should handle a lot offchain handling, thinking about a batcher dex that gets DEED.DEX from the pool and send DEED.ALICE DEED.BOB DEED.CHARLES to the users It's way easier to keep same logic and wrap it But the idea behind is the same and didn't think about it In the end you want 1) Have the ownership of that somewhere that's not the datum (stakecred, assetname) 2) the token is always inside same ScriptHash 3) allow whatever programmable things from the datum of the token

Anyway I put this idea together in a very simple example just after Christmas after reading CIP113 & CIP143 There might be a very good reason that this wouldn’t work, or some potential exploit that I didn’t think of in the couple hours I put the draft together

@BobArchangel Happy new year @BobArchangel hope you’re doing well mate 🍻

@StoicPool Yes, I read the whole thing. I know some guys.

This can be combined with withdrawal validators or ref scripts as needed to have arbitrarily complex logic for individual redeemer cases/monetary policies and the only standing rule would be that: Sum all DEED inputs == Sun all DEED outputs

We can have multiple user accounts to enable multi threads because a user can just mint that extra account beacon, as long as we have the appropriate rules in outputs to force 2 assets: (empty asset name > 0 && pkh asset name = 1)

So if we need to blacklist accounts or we want to enable clawbacks in our particular asset, we can set those rules and tag accounts via the datum

Doing it this way means we have freedom to set datums and redeemers according to the particular programmable needs and provides a simple way for wallets to discover various user accounts according to the token registry -> this might be a negative for infrastructure 😅

The root beacon can have a matching policyid & asset name to id it as the supply beacon DEED.DEED So the initial supply mint will look like this: DEED: { “”: 100,000,000, DEED: 1, } Or more readably: DEED.”” : 100,000,000 DEED.DEED : 1

So any given utxo will be easy to find and will have all the info within it to manage spending those programmable tokens But where does the initial mint go? If it has a fixed supply, we can do so with a one shot param, but that doesn’t satisfy the location of the assets …

But what about user accounts? We can create a user account for that specific asset, which can have an asset name of the PKH, meaning they need to sign to spend from that account utxo, without having to know that credential in advance DEED.pkh