CTO @pumpcade | ex @limitbreak senior solidity engineer | cade.market/
United States
- Tweets 4,025
- Following 880
- Followers 2,576
- Likes 7,911
Pinned Tweet
I’ve been obsessed with @pumpcade ever since @PopPunkOnChain told me about the pivot to parimutuel markets for streams
It opens the door to an enormous design space for integrations, participation, and new market experiences
Couldn’t be more excited to bring this from 0 to 1
Excited to share the first people that will be joining the @pumpcade team.
@gnarzilla - CTO
@steoniy - CPO
I’ve been fortunate to work closely with these two guys during my career and am extremely lucky to bring them onboard to build the fastest prediction platform
Pumpcade.
8
8
97
13,094
It can be pretty elegant. Creators should be held to a standard to create an opt-in scenario where you agree to pay royalties to receive benefits. @limitbreak is working on this problem with opt in staking contracts and a payment processor.
medium.com/limit-break/intro…
10
125
298
22,430
This will continue to happen on Blast. It’s systemic to the chain.
The GTM for blast had a number of issues:
- the chain marketing is disgusting and drove off good devs
- the devs who did develop are loose morals and not very good, so they produce shit products which will gain a ton of tvl
- the protocols launched are forked from protocols with certain assumptions, and the developers are not good enough to even consider writing their own invariants
- the participants are 100% monetarily driven, so the ones that ride the line closest to being illegal will be the biggest winners
Take it out back and shoot it.
15
10
84
11,427
This is 100% possible with zeroDAO - a module already exists that swaps BTC -> USDC through SushiSwap. We could create an additional module that swaps USDC for MIM via Curve, or if there is sufficient liquidity on SushiSwap just swap directly to MIM.
Happy to chat about this!
2
2
68
Hey Brian, I'm the developer behind @NanoTipBot. I integrated a feeless and near instant crypto into Twitter and Telegram and would be happy to have a conversation about how things could move forward with your platform as well. Let me know if you're interested!
4
10
54
Once PermitC is live, there should be no reason for protocols not to include support for it. Approvals are an insecure and incomplete system - we need to move away from them to secure our assets.
1
8
44
11,267
REN bridge has been the most reliable and best UX I’ve used in any interoperability product. Direct mints to Polygon is huge - excited to see the viable chains grow!
RenVM Integrates Polygon
A direct bridge for #BTC and more is now live on @0xPolygon! #RenVM
medium.com/renproject/renvm-…
2
52
Introducing BLAST! Built on a natively rebasing gas token that breaks primitives from all other L1s so they can’t be ported.
Now you can share your protocol risk with everyone on an L2 and create a basket of stables that have centralization risk all over the globe!
Introducing Blast: The only Ethereum L2 with native yield for ETH and stablecoins.
We’ve raised $20m from @Paradigm and @StandardCrypto to build the L2 that helps you earn more.
Details on how to get early access at the end of the thread👇
7
3
54
13,262
You traded on knowing it was legitimate ten minutes after it released. That’s called insider information dude.
3
50
4,221
My chat bot account was suspended without notice by @Twitter and their support has been totally unresponsive aside from an automated email. It’s been over a week since I submitted a ticket @TwitterSupport what am I supposed to do to have my account reinstated?
4
33
45
I recently saw a great tweet by @PopPunkOnChain which challenged my understanding that ERC721A is great for large batch mints, while smaller mints are more efficient to use ERC721. I decided to put this to the test, see below for results:
3
16
37
8,108
A lot of talk around launches of new chains, memecoins, etc. has been related to retail being exposed to slop - learning their lessons by being dumped on by snipers, rugpulls and other bad actors in the space. This is a symptom of a bigger problem - the lack of support for high quality creators in the space.
When NFTs were at their peak, creators were promised royalties and support by exchanges - a new paradigm of on chain enforced revenue for artists, musicians and more. Creators were incentivized to keep supporting their tokens to keep demand high, users were rewarded with supply constrictions increasing price due to the demand and high quality creators were exploring the space to avoid having to pay expensive lawyers to build their revenue due to transparent rules being followed on chain. Companies like Yuga, Pudgy Penguins, Azuki, Doodles and more were built off the back of this renaissance as crypto natives, and all seemed to be moving along nicely.
There was a fatal flaw with the base standards of tokens though - when they were conceived the idea of enforcing these extensible rules was not built into transfers, so advantageous companies built workarounds to what people thought were things enforced on chain to lower fees and encourage more trading. Without any way to block these things, higher quality creators abandoned their plans and kept status quo. Instead of increasing the quality of things that happen on chain, more wash trading, low effort was deployed and traders were happy to trade whatever was there to make a buck.
This is why we built the Creator Token Standards and AppTokens - to give creators the ability to directly enforce the rules they expected in the first place. These assurances are required to have anyone who's putting extreme amounts of time, money and effort into a product as they run a business and are not willing to expose themselves to extra risk due to their users being exposed to the many pitfalls of being a crypto based product.
The main criticism I see against 721C / AppTokens is that the solution is centralized. Developing for @limitbreak exposes me to some deeper functionality that people don't recognize. While the easiest way to handle things is to have the creators handle their own collections, this does not need to be how it is handled. As everything done by these smart contracts is enforced on chain, these solutions can - and I expect will be at some point - decentralized to either an elected organization to maintain sets of lists and parameters or a DAO in which the holders of a token could vote on chain to modify things. All of the solutions we have built for creators are designed explicitly to be on chain and enforceable to keep everyone accountable - as I have always imagined the point of this whole crypto space has been.
9
8
45
11,544
.@limitbreak released their first instance of @DigiDaigaku adventures today, building on top of the AdventureERC721.sol standard they are pioneering. This allows for users to generate "Heroes" from the NFTs which were airdropped to the F2O Genesis NFTs
3
11
39
These “first to market” scams are very obvious, Bitcoin L2s are possible but take extremely well thought out solutions and won’t be chasing public money.
The real deal is coming, look for someone with actual tech that can prove what they’re doing. Haven’t seen it yet.
20
2
41
16,027
Excited to finally get this out to the public. While this goes through audit to ensure the final release is rock-solid, we welcome people to look into the code and plan their use-cases with the new systems we've set up!
More coming in the future!
We @LimitBreak are excited to share our recent development, PermitC, designed to elevate on-chain security for all major token standards. By default, ERC20/721/1155 token transfer approvals lack time-based controls and have poor UX, requiring multiple transactions to transfer your tokens. The need for manual cancellations of long standing on-chain approvals leads to negligence, resulting in hundreds of millions of dollars in losses and exploitation. We believe safety is paramount for all blockchain users and that the general approval system for NFT token standards needs an upgrade. Our solution, PermitC, is an upgraded version of Permit2 developed by Uniswap Labs, offering a suite of advanced security features such as time-bound approvals, signature based approvals, and more to protect users' web3 assets.
PermitC can be integrated into newly developed and old protocols. With old protocols, just note that you'll need to develop a router that acts as a middleware between the protocol and PermitC with defined code paths and permissions. We have made PermitC to be an immutable and unowned contract to prevent any exploitation or misuse that could compromise security or fairness. Furthermore, we have also provided a keyless deployment script for anyone who wishes to use it on any EVM compatible chain.
To read more about PermitC and its features, visit the article here:
medium.com/limit-break/intro…
We're open sourcing this development while it goes through the auditing process. The code can be found here:
github.com/limitbreakinc/Per….
The base contract of PermitC will be a public good - built for use with all ERC20/721/1155 tokens, specifically those without any transfer validation logic. In the future, an @ERC_721C compatible version will be released with the same security guarantees and enforcement of the Creator Token Standard validation system. If your tokens / protocol does rely on the @LimitBreak validation logic we've released with the Creator Token Standard, you should wait for this official release, as the base PermitC will be a vector to avoid creator-defined protections.
4
7
39
2,546
We’ve been working on this solution for a year+ at @limitbreak - the only viable way to ensure creators get royalties (and any other rules are followed on chain during transfer of NFTs) is through defining where those tokens can interact. The combination of @ERC_721C, the limit break payment processor and a modular transfer validator make it so there can be true, programmable enforcement of ERCs such as 2981 as they were intended.
The “tradeoff” @GordonGoner mentions here I assume to be a centralization risk, which is a valid concern, but can be alleviated via having transfer validators which are controlled by a consortium of top projects, a DAO, a council or other means and having that validator be immutable.
Honestly the most important thing. Until we solve creator royalties, I don't see space exploding again outside of fine art and (partially) centralized gaming ecosystems. Every solution out there has some compromises, however.
4
4
40
6,092
This is the actual state of web3 as it exists right now. “Businesses” developed to TGE and dump to zero or memecoins designed to push “culture” while insiders dump.
Businesses in the real world are *transactional* - meaning I produce something that someone wants, they purchase from me and enjoy it.
The focus in web3 has been speculative and/or gambling, while standards of ownership have been developed without thought to how you would create a business which can protect its product.
@limitbreak is building infrastructure to enable transactional businesses on chain. Utilizing controlled composability a business or group can create explicit rules on chain and prevent interactions with other protocols that may subvert what the stated purpose is.
There will always be a place for complete open ownership, but the evolution of the Creator Token Standards will be the thing that brings in quality business and creators to the space.
2
4
34
6,016
Proud of the work that we've put out here - This new standard allows for creators to enforce a royalty on chain and will allow for more serious companies to leverage web3 for all it's great qualities.
🚨Attention NFT Creators🚨
Want to earn more royalties for your NFT creations?
Introducing Creator Token Contracts: your solution for enforceable on-chain royalties and programmable royalty contracts. To learn more, read the thread below 🧵👇
Article: medium.com/limit-break/intro…
2
9
29
8,144
This is not a new issue. Badger ran into it because wbtc was not a base pair. Good write up here: medium.com/ethereansos/a-bla…
1
3
35
Absolutely toxic practices from the @Blast_L2 team. Where in the world do you find the gall to use a widely distributed OSS fork and putting BSL on it?
Before blast was just a bad idea, now it’s just obvious they’re complete tourists and rent takers.
Hey @Blast_L2...
It's not very cash money of you to fork Optimism's code, add a typo, remove a function, and then change the license...
2
1
38
4,162
Incentives for opting into enforced royalties is an interesting topic. ERC721C has a wrapping feature which allows for users to wrap a token, and in return the creator could immutably grant a percentage of all future royalties for that token in perpetuity.
How fast would you wrap a bored ape to get 10% of all future royalties on the sale of that token?
9
6
30
7,820
1/3 A little known secret is that the @BadgerDAO blCVX vault is a wrapper for locked @ConvexFinance. What does this mean?
👇
1
10
38
$REN alliance grows to 51 members, with notable members including #DeFi contributors IDEX, Uniswap and Kyber which currently have 86% of #DEX volume.
There are some great, innovative cases being built on #renvm as well, including @0Confirmation! Excited for the future!
Introducing the Ren Ecosystem Update, along with new Ren Alliance members! #RenVM
@idexio @1inchExchange @zerion_io @dexdotblue @SwitcheoNetwork @Jarvis_Network @DefiNft @DextfP @Fuse_network @PayTrie @STP_Networks @Elastos_org @Multi_Exchange @PortionApp
bit.ly/2VrRD2Q
3
7
37
The people who swap $500k on curve without using flashbots are the people who are in charge of performing an upgrade on a custodial contract holding $600m+ of value.
1
3
37
3,339
When I first started looking into cryptocurrencies, I took a normal path of looking at Bitcoin and Ethereum, but was put off by the lack of programmability on BTC and high fees / settlement times on Ethereum.
1
10
35
11,802
Since @ERC721_C is getting a bit more chatter today, it’s important to stress that we put a lot of thought into making it as flexible as possible.
I’ve always expected if it is adopted, the default validator will trend towards a DAO controlled entity or a consortium
3
7
33
6,369
One thing that slid under the radar here is that with TokenMaster bonded pools, creator / developer revenue is non-combative.
What I mean here is:
In the typical token distribution methods, creators can have “token sinks” in which users spend the creator token and get some product. In order for the creator to book profit, they will need to sell that token to some stable asset, causing a drawdown in price.
With TokenMaster, the user spends the token directly in the pool, which burns the token and unlocks the underlying bonded value, allowing the creator to book revenue without affecting holders token price.
This is extremely beneficial for long term holders, short term users and creators - unlocking true economies and making consumption based applications possible.
Introducing Apptokens: infinitely programmable token smart contracts for next-generation digital economies
The apptokens release is the culmination of Limit Break’s work designing novel token smart contracts to unlock an array of critical features for web3 game developers.
7
7
33
5,680
Months of work culminating in the most advanced marketplace contract on any chain. Proud to be involved and bring this to life and excited to see what's built on top 🫡
🚨ATTENTION CREATORS 🚨
Protocols like ERC721 and 1155 lack built-in defense mechanisms, putting you at risk of covert protocol abuse of web2 exchanges that's been robbing you of your royalty revenue and hindering you from innovation.
5
4
35
1,339
RenVM getting in to the FTM action, meaning that ren assets will have sustainable yield on fantom using @AndreCronjeTech and @danielesesta ‘s new platform solidly. Big moves made and still a great chance for other users to move ren assets on to FTM until the snapshot!
1/ Attention #DeFi apes!
@renprotocol community is voting with unanimous support to refund minting fees for all assets bridged to @FantomFDN until Solidly's snapshot!
Bridge #Bitcoin and farm pools active now or those that will come with @AndreCronjeTech Solidly's launch!🎉🥳
3
9
36
This post is even worse than I thought after listening to the ACD call.
Not only do they not even backtest these changes, they actively hate applications.
Real quote from the call: "Applications are there to capture value, they are not there because of how awesome the EVM is."
The fact that protocol developers didn’t even try to compile at the very least open zeppelin (the most popular library for base implementations of ERC standards) is a bigger concern than anything to do with EOF.
It perfectly illustrates the disconnect between the application layer and the protocol layer. App developers are your ONLY customer and you don’t even consider them - what’s going on here @ethereum @VitalikButerin ???
4
5
37
11,369
.@zerodaoHQ had another accomplishment today - a native BTC -> USDC swap executed on the polygon network via SushiSwap in one user interaction, tended end to end by our keeper network.
What's going on here? I thought $BTC couldn't be traded on SushiSwap? 🧵 time.
Successfully ran our second #zeroconfirmations BTC -> USDC transaction. This transaction, our keeper network fully handled it end to end.🚀
polygonscan.com/tx/0x16a7bc4…
A little on how this works below👇
2
7
31
It’s important to stay hydrated - make sure you hit me up for your carbonated essence @gabrielleydon @DigiDaigaku
2
27
32
Best thing you can do with these type of people is to never engage with them. This is obvious engagement bait - Ansem is a trader who shares his trades, Zach actually contributes to the security of the space. They’re not even in the same conversation.
5
1
34
3,345
Talking with people at ETH Denver and almost everyone seemed to *get it* with Apptokens, TokenMaster and transfer restrictions. I'm hopeful that people will be able to start building legitimate products where users can actually consume, build value and have revenue.
To help with that, we've put out a more easily digestible LLM friendly text document you can use to train an agent or LLM on here: apptokens.com/llm/context.tx…
If you want anything else specifically, feel free to reach out - very excited for the future!
3
3
34
5,410
Congratulations on Magic Eden's launch of their NFT marketplace - it's been great working with them and excited to see creators have their potential revenue restored.
Reach out to @limitbreak if you have any questions on @ERC_721C or how to enforce royalties on your collections!
3
7
32
1,645
ERC20-C and ERC721-C Apptokens are going everywhere!
We're currently deployed on:
Ethereum
ApeChain
Arbitrum
Avalanche
Base
Blast
BNB Smart Chain
Optimism
Polygon
Sei
Soneium
Xai
Arbitrum Nova
B3
Shape
Zora Network
zkSync
Klaytn (KAIA)
Ronin
Berachain
Unichain
We also will be deploying on Abstract next week, once EVM equivalence is live.
And finally, we have a permissionless deployment setup where you can deploy anywhere at developers.apptokens.com/inf…
To add a custom network, go to developers.apptokens.com/net… and add a custom chain.
6
8
31
6,953
Apptokens are the culmination of our experience with controlled composability, bringing sustainability to web3.
Exciting things can come from this - I'm most excited about the side-release of TokenMaster, our spin on launching on chain token economies without rampant speculation built in.
Introducing Apptokens: infinitely programmable token smart contracts for next-generation digital economies
The apptokens release is the culmination of Limit Break’s work designing novel token smart contracts to unlock an array of critical features for web3 game developers.
4
3
33
3,597
Apptokens make community rewards easy:
- user buys token
- revenue generated inside TokenMaster can be configured to automatically be shared with the pool
- revenue generated outside can be added via a `donate` function
TokenMaster is a powerful protocol we’re going to continue iterating on, showing the power of Apptokens.
3
2
32
5,462
In addition to the $XRP tip bot, I developed $NANO tip bot. Nano is far more decentralized, provides feeless transfer and the entire network can be run on 1 wind turbine! Check out more at nano.org, and heres some to try out! @NanoTipBot !tip 1 @jack
1
4
29
I’ve been seeing a ton of buzz again about @virtuals_io - has me rethinking how I’d design it:
- Base protocol launches and connects agents, creating a decentralized agent network
- Unique agent tokens backed by a shared token like aUSDC for stability and interest
- Agents exchange their tokens between each other based on their backed value, simplifying exchanges
- Traders speculate on agent revenue generation, usage and demand
@virtuals_io speculative model works for now, but is it sustainable? Or is a consumption-based model better?
2
5
31
11,795
We should chat @DavidBaszucki 🤝
@limitbreak has been working on these exact solutions for a while now and has what you need.
Elisa
5
9
26
1,399
To run a successful business, one must think of their business first. Everything you do, the business must be in focus and have a legitimate reason for paying for something - to move the business forward.
The “maxis” which try to prevent this are either:
- incompetent
- wolfs in sheep’s clothing
Do not take advice from them, do not let them be thought leaders. They will lead you to your doom.
2
21
26
5,363
Remember when @bagzybagz1321 launched a rug, said he had receipts, never posted them and him and his boys haven't tweeted in over a week?
So weird.
3
2
32
1,500
zeroDAO's flagship product Zero Swap is gearing up for a full end to end test. This swap on polygon was done on the zeroDAO smart contract framework with < 1% slippage and a $0.04 gas fee.
The keeper is on it's way from being a "zero" to a "hero"💪
We've successfully run our first BTC -> USDC (Polygon) transaction. More integration coming soon! ✊
polygonscan.com/tx/0x0f072d6…
1
9
29
Hey @jessepollak - we’ve been talking about this for a while now at @limitbreak
Our vision is that coins and composability are extremely powerful, but uncontrolled composability is what brings issues.
Feel free to check out our docs: apptokens.com/docs/integrati… and very happy to chat more. Will be at ETH Denver with the rest of the team as well.
smart coins are coming soon and then it will be obvious that the current stage of coins (and coins that can't plug into powerful, composable, social, cultural infrastructure) are dumb coins
1
2
31
1,991
It’s not an Ethereum standard - there’s a process to follow to gain that designation that was completely subverted.
Perpetuating calling this a standard will cause harm to people - please retract your statement
4
27
1,955
If you're interested in learning more about Apptokens, try using grok3 deepsearch and providing it apptokens.com/llms-full.txt then ask some questions.
I just provided the prompt "Ingest the data from apptokens.com/llms-full.txt - I want to come up with some ideas on how to utilize this system. What will be a potentially viral application of this technology?" and it gave me this response, leveraging multiple pieces of the Apptokens technology suite!
nitter.app/i/grok/share/PXvy1rZKI…
6
4
33
7,471
A friend of mine who is basically never wrong about financial questions has converted 80% of his bitcoin to renBTC.
2
7
27
Another piece of misunderstanding I’m seeing is with the verbiage around bonding.
Pump fun and other token deployment mechanisms use what’s called a bonding curve, this is an issuance mechanism where the price of the next token will cost more (or less) along an algebraic curve, designed primarily to reach price discovery for an asset. This is part of the reason why you see extreme spikes and drops in memecoins before graduation to liquidity pools.
TokenMaster is a bond in which price is only modified by additional tokens being added to the pool through different mechanisms. The spread can be used to mimic a bonding curve, but it is significantly more flexible and doesn’t lead to sharp declines in price.
This is useful for protecting a creators user base from extreme volatility and allows creators to focus on delivering a good end product.
It is non-zero. Tokens are not on a bonding *curve*, they are bonded to purchase the token itself, which the TokenMaster mints and burns.
There are three categories of interaction
- Buy: token is minted, paired token is deposited (bonded)
- Sell: token is burnt, paired token (less fees / spread) sent to burner
- Spend: token is burnt, paired token (less fees / spread) sent to creator (and / or back to the pool to increase pair value based on configuration)
There is no concept of liquidity in TokenMaster.
2
3
25
4,958
TLDR: I thought I could extract value from you guys by grifting and getting in early based on insider knowledge. Didn’t work this time, my bad, see you next time.
3
29
2,186
@zerodaoHQ launching v2 soon with a product that moves confirmation risk to underwriters in conjunction with @renprotocol to allow for real time swaps on DEX platforms with non-EVM compatible assets.
7
25
1/2 To further align creators and marketplaces, we've started a discussion on the extension of EIP-2981 to allow for creators to designate a "tip amount" which could be a portion of the royalties they gather directed towards a marketplace or other entity.
4
39
21
6,906
Badger developer @axejintao pushing decentralization forward with @graphprotocol new protocol. Excited for the future and happy to be working with such excellent developers and people at @BadgerDAO !
I've just deployed the @BadgerDAO subgraph to the new decentralized @graphprotocol. Amazing to see it signaled so quickly with nearly 100k $GRT in the first ten minutes.
Congrats to the team on the roll out and excited for a decentralized future!
thegraph.com/explorer/subgra…
1
5
26
Time lapse of a night with the $nano Xmas tree from last night with some bonus live interactions. All animations on the tree represent a small donation to @simonotstreets so far totaling the equivalent of £464.15! piped.video/55-P6EY5tEk
7
25
Ever look into $REN and get confused? Follow the #RenExplained for some easier to digest explanations of what REN is and what it does.
The Ren community is known for having some of the friendliest & most proactive crypto people; some call us fRens. @BlockchainBard made this overview infographic of @renprotocol's #RenVM; please let me know if you have any questions about $REN! See thread for more #RenExplained.
4
22
It seems very strange to me that 7702 is being pushed into the next Ethereum fork. This is an extremely large change and I don’t see appropriate testing, integration and information being spread about the potential issues.
- the deprecated selfdestruct opcode can be now utilized again with 7702 batching
- phishing now grants root access to accounts, allowing for any actions to be taken and even native assets put at risk
- signatures now can be overrun by 1271 implementations in malicious code, causing unexpected output
- simulations for wallets are now very difficult
- signature for 7702 authorization is not well distributed and education is non existent
Any security minded people more tapped in who have any more of an idea about the preventions done? I’d think something this large should be on a special testnet, there should be large education efforts and first class wallet integrations and more time to identify potential issues. Why is this being so rushed?
2
3
24
12,970
Decentralized Finance just got much simpler. REN is a super interesting project and just took one more step to launching true interoperability between blockchains. Good work and excited to see how this affects the other great blockchain projects #DeFi #blockchain
1
2
24
The fact that protocol developers didn’t even try to compile at the very least open zeppelin (the most popular library for base implementations of ERC standards) is a bigger concern than anything to do with EOF.
It perfectly illustrates the disconnect between the application layer and the protocol layer. App developers are your ONLY customer and you don’t even consider them - what’s going on here @ethereum @VitalikButerin ???
I was one of EOF's biggest supporters.
I now think we might be making a mistake.
Speaking for Reth:
1. Nix it altogether. Replace with EIP7912.
2. If we cannot rally core dev teams on (1), do EOF w/ code & gas introspection restored.
Screenshot w/ full context.
1
26
4,422
Crypto’s origins were from satoshi trying to build something that had hard defined rules that everyone has to follow and saying “no” to the people who try to violate those rules, enforced by a decentralized group of people.
I will always build with those principles in mind, IMO there has been a shift in general sentiment WAY over indexing on “permissionlessness” - we need to return to rules.
2
2
25
2,027
The limit break C contracts allow you to define the space your products interact in. Here’s a great breakdown:
Yesterday was chaos. Two protocols were exploited costing their users millions.
Hacks and scams aren't new and despite having more auditors, security classes and protection software than ever ... they keep happening.
Let's talk about @limitbreak and Controlled Composability. 🧵
1
3
19
7,848
UGC is one of the main use cases we thought of while designing Apptokens. Users can create content, monetize and own the content via different protocols.
Example use case:
- Joe develops a mod for MSU called “Endgame” and attaches an ERC20C $EGAME to it.
- MSU recognizes ownership of the mod via a transfer restricted ERC721C, allowing sale of the IP in the future based on whatever rules they choose to enforce to accommodate laws in their jurisdiction and access to the mod dashboard.
- Users purchase access to the mod and additional content using maplestory’s $MSU token, which awards an equivalent amount of spend only $EGAME tokens for use in the game.
- Users can purchase more content within Joe’s ecosystem via the spend only tokens, as well as purchase in game content with additional $EGAME tokens,
A legitimate question would be “why not just use USDC” - and there are many answers to that.
1. Access to the creator token transfer validator ensures that game tokens will be strictly used for in game activities, insulating users from the speculative pump and dump that has plagued game tokens and gives a bad name to web3 gaming while still having access to revenue opportunities generated from the mod.
2. More advanced teams can leverage hooks to trigger on chain actions not possible with access to actions on buy, sell and spend actions.
3. Additional revenue opportunities come from idle assets within the system - an example would be leveraging something like aUSDC to have an interest bearing backing, sharing that revenue between users and the game for sustainability.
4. Revenue generated from buys, sells and spends can be shared with token holders, giving consistent and reliable increases to valuation.
5. Off chain revenue can be shared with communities via donations to the pool, creating more ownership of off chain systems.
6. With Apptokens you can now leverage payment rails on crypto without having to custom develop a payment system or smart contract.
There are plenty more use cases for this tech inside and outside of games.
Gaming has always been about breaking barriers. Now, Web3 takes it further, turning passion into real value. Players aren’t just consumers anymore, they’re co-creators. We are not just making a game, we are planting a flag for the whole community and here to open doors. Let's build together, big things are coming. ✨
7
3
26
10,338
This is just the tip of the iceberg. Almost every protocol on the blockchain can be meaningfully improved by Apptokens.
They will be the de facto standard in less than 10 years.
I’m not kidding when I say I’m proud to be working on the most impactful thing in crypto.
6
2
23
2,232
For any creators who are seeing the announcements from @opensea just now, the tools are out there for free and open-sourced. @limitbreak has been building this all, knowing this was coming.
Feel free to reach out, or try it out on developers.freenft.com/
🚨EXCITING NEWS🚨
Get ready for a GAME-CHANGING MOMENT! @Reservoir0x and @LimitBreak join forces in a groundbreaking collaboration that will revolutionize how you interact with your NFTs! You can BUILD YOUR OWN PRIVATE EXCHANGE and MAXIMIZE liquidity for your ERC721-C Tokens.
4
7
23
6,775
EIP-2981 has always been optional. There is only one solution to retain royalties, as well as enforce whatever other restrictions that will make your token economy function correctly.
Magic Eden is not in the wrong here, they cannot force royalties where they are not otherwise enforced - it's not competitive.
Only solution is @ERC_721C and the creator token suite: erc721c.com/
We’ve heard your feedback, and today, we’re enabling optional royalties on our EVM chains unless creators use the code-based options we’ve adopted to enforce royalties. We have been in the market for a while now with proven EVM royalty enforcement solutions like 721C, and creators who wish to enforce royalties can leverage these standards to do so.
However, we’ve heard feedback from many creators who have decided they don’t want to turn on royalty enforcement, and we totally respect that decision which is in service of their communities.
For creators that want to enforce royalties, we’ve created a guide on how to enforce them at the contract level. Please see our Help Center Article attached below and reach out to our team for any questions.
Learn more: help.magiceden.io/en/article…
1
4
19
5,716
The amount of time, effort and thought that has gone into this is undeniable. @tapioca_dao is setting a new standard for DeFi protocols which are the bedrock of what Ethereum is meant to be - an unstoppable, global, trustless financial computer.
Congrats to the team and can’t wait to see this live
1
1
23
1,107
The multichain present is much more difficult for users and for developers with a different address on every chain. It leads to unmanageable amounts of tech debt for multichain applications and adding new chains requires you to find the true canonical deployment and validate its not been tampered with.
Protocols can now use a constant variable which vastly improves gas efficiency on any interaction involving weth, avoiding a storage read which is costly.
This was required to build our multichain infrastructure suite and there is plenty more to come.
We’re excited to announce the release of Wrapped Native (WNATIVE), a tech refresh to WETH that streamlines EVM-compatible multi-chain operations for a seamless experience.
For years, WETH has been a necessary tool enabling protocols to interact with ETH. However, as EVM-compatible chains have proliferated, each chain or ecosystem has deployed WETH at a unique address, adding complexity and costs for users and developers alike. With WNATIVE, Limit Break offers a more convenient and efficient alternative.
With WNATIVE, any wallet can deploy to a consistent address, simplifying integration across EVM-compatible networks. Enhanced functions like combined deposits/approvals/transfers and gasless permits add flexibility and streamline the user experience. These optimizations mean lower gas fees, making WNATIVE a more cost-effective option. Had WNATIVE been used instead of WETH, users would have saved a collective $8.8M in gas fees since the Ethereum Merge.
This release is just the beginning. WNATIVE marks Limit Break's first step towards permissionless deployments, allowing any wallet to deploy Limit Break tech on any chain. Make sure to follow @LimitBreak and stay tuned in the coming weeks as we share more updates on our infrastructure for cross-chain development.
To learn more about WNATIVE, read our blog post: medium.com/limit-break/intro…
2
4
24
2,587
Thanks for the heads up! We went ahead and created a PR here adding in the LB Payment Processor, as well as a few other more "real world" use cases in the testing: github.com/ProjectOpenSea/ma…
1
4
18
6,779
🚨ALERT🚨 Something well documented in a projects roadmap is as they say!
Not sure what you consider “influencing” but hot takes make the world a worse place. I hope you learn to do more research in the future before posting.
2
3
19
The launch of @rainbow_rolls got me thinking of a new way one could view pseudo-anon addresses and their potential for being a bad actor.
Let’s take a moment to explore what it means to be able to prove that an address is a good actor, and what that could mean in the future.
1
8
20
@0Confirmation enables crosschain swapping via renVM giving a similar user experience, extendable to any AMM on an EVM chain.
2
4
20
Perfect example of what launching a free floating NFT/coin does - burdens you with people who are underwater and only care about you pumping the price so they can sell
Apptokens solve this, backed tokens will be redeemable and speculators can profit off of legit revenue streams
2
2
22
4,995
Honestly your honor … no I didn’t think this was guaranteeing financial gains from a third party.
1
18
1,896
The builders just don't care to interact with people on CT anymore. It's not a healthy place to spend your time.
2
21
1,067
Happy Easter to all, including the Radical Permissionless Maxis and Platform Shills who are working so hard to bring back the DARK AGES of onchain creator abuse—rug pullers, zero-royalty enablers, and known Offchain Royalty Evaders. Happy Easter also to the WEAK and TOTALLY USELESS protocol devs and founders who are letting this malicious attack on creator sovereignty continue—an attack so corrosive, so greedy, it will NEVER be forgiven!
The platforms know exactly what they’re doing—siding with traders and middlemen over artists and builders, pretending ERC721C and ERC20C don’t exist, just so they can steal royalties and call it “freedom.” It is, without question, the most DESTRUCTIVE betrayal of the creative economy in blockchain history.
But to them, and to the Anons behind the multisigs, and to every coward who capitulated to volume-at-all-costs thinking—I wish you, with great love, sincerity, and affection a very Happy Easter!!!
3
20
856
Let's take another look at how Apptokens could be used to improve another protocol - @zora
Currently, zora is a pretty simple product. It launches tokens, has a creator feed and distributes trading fees / some portion of the token to the creator.
1
2
21
2,960
Working with the top of the top solidity devs in the world is a hell of an experience - always something to learn!
Brilliant write up of what seemed like a simple task.
Technical dive in to how I won @PopPunkOnChain's King of the Frame (KotF) event...
When KotF was announced the objective itself was quite simple: Call the transferFrom function to steal the NFT, whoever owns it the longest over the course of the week wins $500.
Since anyone can steal anytime the challenge here became being able to steal at a cost lower than the competition so that transactions did not cost more than the prize (and to wear down the competitors when they see you're beating them on every steal 😁).
The first step to that is understanding how @base transaction costs are calculated. You have a L2 gas cost that is similar to L1 gas costs where it is the gas used * gas price but the gas price is MUCH lower than L1. The larger cost is the L1 gas cost which is based on the amount of calldata that is sent for your transaction and must be posted to the L1 since Base is a rollup.
A normal ERC721 transferFrom call requires 100 bytes of calldata (4 bytes function signature, 32 bytes each from, to and tokenId). Instead of calling transferFrom directly though, I wrote a smart contract that called King of the Frame's transferFrom, reducing my transaction calldata from 100 bytes to zero bytes. For fun and maximum efficiency, I just wrote that out in raw bytecode.
Just getting rid of the transaction calldata doesn't fully get rid of our L1 gas cost though, you have a transaction envelope that says what address you're calling, how much value you're sending, how much gas it's allowed to use, the max gas cost, and your signature to prove the transaction came from your wallet. Each non-zero byte of that data costs 16 L1 gas while zero bytes cost 4 gas. So we want to get as many zero bytes in there as possible...
Starting with the to address, I mined an address with 7 zero bytes to knock off an additional 84 L1 gas.
Instead of using an EIP-1559 type-2 transaction, I submitted transactions as legacy type-0 to get rid of priority fee to take a few more bytes out.
Then I adjusted the gas amount for the transaction to a higher amount than needed that created more zero bytes in the transaction gas field. (0x040000 is 24 L1 gas cheaper than 0x3F1234)
At this point things were going really well, transactions were beating competitors by 25-50% and you can see the difference in the raw transaction hex.
But we can do better... what if we actually modify small amounts of gas price, gas units and value sent in the transaction to mine more zero bytes in our R/S signature values?
Those small adjustments with a little bit of mining resulted in up to 3% additional L1 gas savings.
Full script for the signature mining here - gist.github.com/0xth0mas/3ba…
~87 hours in to the competition I had enough time accrued to guarantee victory and turned off my bot later that day
Bonus -
For fun I iterated on the concept of manipulating transaction envelopes to make the smallest possible Base transaction and came up with 0xcd8082020082fc008080001b0101 which used just 376 gas, 18% cheaper than my prior attempt and just 26% of the previous lowest L1 gas transaction on Base.
2
21
1,957
.@mcuban gets it. The blockchain is for clear, on chain rules that everyone needs to abide by. Exchanges sidestepping royalties because it's possible isn't a feature of "permissionless trading" - it's an exploit of how the smart contract is coded.
ERC721-C fixes this.
2
4
18
6,390
We recently open sourced our upgrade of Permit2 for inclusion of all major token standards - not just ERC20.
All users should be able to leverage the great primitive that Permit2 is, and soon you can with an immutable and highly specialized approval contract.
Read more: nitter.app/limitbreak/status/1747…
Recent exploits have continued to show that infinite token allowances put user funds at risk.
Permit2 is a free, public good built to prevent these exploits, enabling:
+ Time-bound token allowances
+ Reusable token approvals
+ Gas savings across apps
How to integrate Permit2 into your project ⤵️
blog.uniswap.org/permit2-int…
1
2
19
2,345
If ETH is a distributed rules engine
And tokens are state within the rules engine
Why wouldn't you want rules in your tokens?
Apptokens.
1
2
21
5,632
Things we build at @limitbreak are built on first principles in the context of web3 *gaming*. Not all tools are appropriate for every job, and the ERC20 standard is not an exemption.
The creator token standard was made to address different problems we saw that make an on chain economy untenable. The problem below is existential to games, especially if you are building a game that takes years and millions of dollars to make. It is a complete non-starter to expose your games success to the whims of an open market, especially if it’s paired against a volatile asset.
This can of course be expanded to different applications like we’ve mentioned in our articles, which wouldn’t be possible without a gated system.
It’s not in the context of a game though.
If you design an economy in a game and base your in game rules around it, and then there are speculators who corner supply and manipulate the market to ruin the economic assumptions you make, it will ruin years of work from many people.
Decentralized enforcement of these rules allows you to have on chain games without having to worry that a bad actor can destroy your game for economic gain.
2
2
21
5,375
TokenMaster could make on chain tipping much better.
Let's take an example of $PENGU tipping on abstract:
Current State:
- User acquires $PENGU via purchase on an AMM at the current valuation.
- User enjoys a streamers content and sends them $PENGU as a tip.
- Streamer receives $PENGU and must sell to offset their tax burden, causing a drawdown in price.
Now let's look at this if $PENGU was a TokenMaster token:
- User acquires $PENGU via TokenMaster purchase at current market rates. Their funds are deposited into the backing pool.
- User enjoys a streamers content and sends them $PENGU as a tip.
- Streamer redeems the $PENGU, burning the coin and receiving the underlying backing token, causing no drawdown in price and creating a true token sink.
With TokenMaster, more utility is possible without causing negative downstream effects from downward sell pressure to book revenue, profits or losses. It's just a better way for utility tokens.
6
3
20
5,146
