Will Papper pfp

Will Papper

@will

486 Following
5961 Followers


Will Papper pfp
Will Papper
@will
@raihan has it!
0 reply
0 recast
0 reaction

Will Papper pfp
Will Papper
@will
If you're at Edge City prior to Devcon, come to @syndicate's Introduction to Metabased Sequencing! We'll be doing a live workshop + a walkthrough of how @metabased sequencing works. @sheldon and @gustavoguimaraes will be leading the architecture overview and hands-on coding! https://app.sola.day/event/detail/10928
1 reply
7 recasts
26 reactions

Will Papper pfp
Will Papper
@will
Cloud Run is excellent if you’re willing to take the time to set up a VPC. If you’d rather avoid that, Render makes external and internal service creation very easy
0 reply
0 recast
2 reactions

Will Papper pfp
Will Papper
@will
On the fragmented liquidity side, these arguments were also made about L2s. If a use case needs deep liquidity, it can still attract that via sequencing or bridging mechanism designs. Rewards can go a long way in making these use cases attractive. L2s found the same playbook here, with Optimism directly incentivizing bridging for example. A "many L2s and L3s thesis" already has a precedent to follow, with Superchain making shared liquidity easier every day. Worst case, as is true of L2s right now, you can always get deep liquidity from the underlying layer. In the long term, apps will be able to stand on their own without requiring deep liquidity. But in the near term, this will look pretty similar to how L2s look today, with the Superchain as an important solution.
0 reply
1 recast
9 reactions

Will Papper pfp
Will Papper
@will
I of course have a point of view here, but only because it comes from a deeply-held belief that communities should be able to own their chains. On the integrations side, people were saying the same thing about L2s being more difficult to integrate than ETH Mainnet. Ultimately, fee reductions and the subsequent user demand led the infrastructure providers to add multi-chain support, but it assumed a few large L2s. Now that we're seeing the proliferation of many L2s and L3s, infrastructure providers will need to evolve again. Just like how L1 -> a few big L2s required some work to operate smoothly, a few big L2s -> many L2s and L3s will require work as well. So where does the user demand come from? In my opinion, it's things that are impossible on large L2s. Ham putting FID data onchain is the perfect example. Only a tiny fraction of the world is onchain. If we don't pursue L2s and L3s, we will hold back the space in its onchain potential. Moving more communities onchain is why many L2s and L3s must exist.
1 reply
2 recasts
8 reactions

Will Papper pfp
Will Papper
@will
Are you in SF for @ethglobal San Francisco? If so, drop by our @syndicate @metabased happy hour on Sunday late afternoon! Come chat about L2s, L3s, and the potential of rollups with us https://lu.ma/wczdbxk5
0 reply
4 recasts
25 reactions

Will Papper pfp
Will Papper
@will
I trust any dev tool recommendation from the username @git
0 reply
0 recast
1 reaction

Will Papper pfp
Will Papper
@will
Ah I love Render but avoided it because it’s stateless and I need state here. Seems like Railway is better at handling state - will check it out! Thanks for the pointer
1 reply
0 recast
0 reaction

Will Papper pfp
Will Papper
@will
👋
0 reply
0 recast
0 reaction

Will Papper pfp
Will Papper
@will
gm
0 reply
0 recast
0 reaction

Will Papper pfp
Will Papper
@will
I spoke too soon, now I need to handle inheritance in Dev Containers for specific services and everything is painful I feel like most GitHub tools are amazing in a single service but terrible once you need to extend them to multiple services (GitHub Actions is the same way)
1 reply
0 recast
18 reactions

Will Papper pfp
Will Papper
@will
I absolutely love Dev Containers and I wish that I started using them earlier Makes new dev environment setup super easy. Supported by most major IDEs + GitHub Codespaces, feels completely native. All of the upsides of containers (automation, trivial to rebuild) without the DX downsides of interacting with them
1 reply
0 recast
12 reactions

Will Papper pfp
Will Papper
@will
Some artist friends are seeking feedback on their candidate prop! https://www.nouns.camp/candidates/glitch-%3C3-nouns-7e6ce11bee2ab7f84ef0d1955ce1f546d897ab98 GLITCH was funded last year for its artist residency and wants to build up a bigger initiative around public goods. Feedback is very helpful on this!
1 reply
0 recast
4 reactions

Metabased pfp
Metabased
@metabased
Today's the final day to submit an application for the Metabased fellowship (11:59pm PST). We're looking for folks building the future of communities with crypto tooling. Fellows receive: — Mentorship from industry leaders — $20k stipend — Early access to Syndicate's newest tech https://airtable.com/appmZFbdGEFBBrDCo/page3DoSykqP2LqE2/form
1 reply
1 recast
8 reactions

Will Papper pfp
Will Papper
@will
👋
0 reply
0 recast
0 reaction

Will Papper pfp
Will Papper
@will
Could be coupled with the @neynar or @openrank spam datasets
0 reply
0 recast
1 reaction

Will Papper pfp
Will Papper
@will
Here are some examples! https://syndicate.io/blog/metabased-economic-mechanisms Auctions, staking, memberships, MEV sharing. But we know there’s many more, which is why we’re excited about the fellowship!
0 reply
0 recast
1 reaction

Will Papper pfp
Will Papper
@will
Are you a Solidity dev or mechanism designer? If so, are you excited about potential sequencer revenue models that go beyond gas fees? If so, apply to the @metabased fellowship! Get paid $20K to design new sequencing mechanisms with feedback from some of the leading investors in the space. The fellowship runs for eight weeks. You do not have to be full-time -- participating alongside existing roles is perfectly fine! https://warpcast.com/metabased/0x1c7f35f2
2 replies
5 recasts
27 reactions

Will Papper pfp
Will Papper
@will
Finally a channel for people who also hate using right-handed scissors
1 reply
0 recast
20 reactions

Will Papper pfp
Will Papper
@will
I majored in philosophy and it definitely made me a better writer. That being said, I only did it because I knew how to code. Otherwise it would have been a much higher risk decision Anecdotally, 1/3rd of my philosophy cohort went into law or PhDs, another 1/3rd went into tech, and the last 1/3rd is in nonprofits
1 reply
0 recast
14 reactions