On Amsterdam afterparty - venue squared away between Spruce, Ceramic, WalletConnect, CyberConnect. Need to get the invoice for the bar to pay it out.
Coworking - We have additional tickets available for the coworking space.
CASA Onboarding
[Juan] - Should we have a mailing list (#17).
[Rocco] - I'm down to just do a Discord channel.
[Pedro] - I'm not a fan of email but some folks might find it useful. If we ask for emails, and people submit them, maybe we create one. You want to convert the emails from the ticketing to a mail list?
[Juan] - Just thinking about it for PR reviews. Can GitHub do something like that in terms of blasting reminders for new PRs?
[Pedro] - You can follow an organization - you have to consent to it and you can tag someone as a mention and it'll force people to get a notification unless they unwatch it.
[Juan] - Need to find the authors of particualar namespace CAIPs.
[Ligi] - We can call them out at the event. At some point they really want to get their chains in. Maybe we copy over what is there to the namespace and leave it in draft. I don't think we have to push people there.
[Juan] - Maybe we find the emails on their websites.
[Pedro] - I doubt these folks might show up at the event so it might be a good idea.
On the CASA community call
[Perdro] - Should it be something we don't necessarily post - or do we see a PR mature and once we see it mature we send the person to the call.
[Rocco] - Call is once a month so it's not too bad - so possibly where folks that are contributing get the form to sign up to the call.
[Pedro] - Bad issues are still good because there's a marker for it. Especially now that we have the GitHub up and mobile.
[Ligi] - Let's move around Google Forms and see if people can do it via the original process.
[Juan] - Maybe we should have a issue template where people drop their contact information.
[Pedro] - The more that we lean on the GitHub the better because it creates a foundation for everything else. We can always poke people to be active on GitHub. It's not that we're curating, we're just setting the standard for communication.
[Juan] - Ligi can you add Rocco to the form? (Adds)
CAIP Review
[#99 - Open] - Whether we're so chain agnostic that we can talk about things that aren't blockchains or DAGs. The great debate.
[Pedro] - We had very few that were non-blockchains, right?
[Juan] - Radicle
[Ligi] - Let's have the big debates at the event. Let's clear the low-hanging fruits. I merged the eip-155.
[Juan] - Going to close with comment because those are so well written that they can be copied over without changing anything.
[#94, #95 - TBD] - Hive Blockchain Reference
[Ligi] - Hive is the testing tool for Geth. I think they mean something different there.
[Juan] - I haven't even looked yet.
(putting on hold)
[#40 - Merged] - CAIP-25 Correct YAML
[Ligi] - Can be easily merged.
[#53 - Last Call]
[#50 - Converted back to draft] - CAIP-50 Multi-Chain Account ID
[Pedro] - People wanted a better CAIP-10 so it almost worked as unique addressing. Takes advantage of multi-format that IPFS uses. Even if you have the same namespace and then you change the reference and you have the same address, it comes out with a different address encoded and makes it easy to identify. It raises a number of questions and we're not sure if it's useful because it sits in the middle of machine-readable and human-readable. Not sure if it gained a lot of traction. It could be merged as a draft. I published an NPM package to execute this one.
[Juan] - I'm confused at what it does that multibase already doesn't. It's for addresses not keys? It's like a multi-format way of uniquely encoding addresses?
[Pedro] - Instead of namespaces being written out, they're indexed. The references uses variable ints. and they let you have the length which makes it more compact. In order to do that, you need to go to the multi-codec table and add it. But then this was at the same time there was a conversation around reordering the params. of CAIP-10 - at that time nobody wanted CAIP-50.
[#24 - Ready for Review] - Add Chain Agnostic RPC
[Juan] - Feature discovery is a cross-chain building block.
[Pedro] - I realized that when you go through CAIP-5, there's a PR that was on the multicodec table and it did get added. So it did get added.
[Juan] - Now we have to do that work.
[Ligi] - Would be useful to rekindle relationship with MetaMask.
[Juan] - This is a CAIP I'd like to contribute to.
[Pedro] - This is something I personally think will be a conjunction of JSON RPC standards. The particular example that Dan mentions is that they would adjust the prefixes to have chain IDs. Is that the repsonsibility of methods to encode chain IDs because then you would have to interpret the method. CAIP-7 provides a method that passes a chain ID side by side. Much better approach than hijacking the method. JavaScript API for JSON RPC like Ethereum has but for chain agnostic is something we'd work on. I definitely would like to focus on that specific one.
[#104] - add namespaces CAIP and templates to match.
[Juan] - If folks come to evangelize a chain, we can point them to the namespace template rather than open up a CAIP.
Namespaces PR Review
[#3] - to add bip122
[Ligi] - We can merge this one.
[#4, #16, others] - to add Hedera, Solana, Polkadot, Cosmos
[Juan] - Someone is coming to Amsterdam to evangelize. Solana, Polkadot, and Cosmos are ready to go. We can merge the status quo ones quickly and leave open the more controversial ones.
[Pedro] - Someone wanted to use WalletConnect v2 with Stellar.
[Juan] - I just need the thumbs up on these for folks that dealt with it in the past.
Other Matters
[Juan] - We can create a page similar to EIPs for CAIPs where it auto-generates.
[Ligi] - We should add a "Help Wanted" label on the issue for that, which shows up in special pages on GitHub and draws more attention.
biggo thanks to @obstropolos for scribin':
CASA Meeting
2022-04-07
Agenda
Amsterdam
CASA Onboarding
On the CASA community call
CAIP Review
Namespaces PR Review
Other Matters