Permissionless Software Foundation Technical Steering Committee, 3 Feb 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: PSF TSC Meeting - 02-03-2021

Description

Agenda:

https://github.com/Permissionless-Software-Foundation/TSC/issues/3

PSF specification for attaching mutable data to an SLP token:
https://github.com/Permissionless-Software-Foundation/specifications/blob/master/ps002-slp-mutable-data.md

PSF Telegram channel:
https://t.me/permissionless_software

A

Okay, it says it's live, but we're gonna wait a minute.

A

Okay and I got a link- that's.

B

Great there's some little little participant there.

B

What's that this one joey's kit, maybe oh, oh some interest in bitcoin, maybe yeah.

A

Okay, so for those watching on youtube hanging on for a minute just doing some bookkeeping, we'll get this started shortly.

A

A

Just tweeting out the links for anybody, who's.

A

A

There we go tweeted out the link.

A

Okay, I think we can get this started. um I'm gonna go ahead and share the agenda share. My screen.

A

There we go just a web browser this time.

A

Okay, everybody welcome to the permissionless software foundation, technical steering committee meeting. uh This is the agenda that we've got today on our screen um before we get started with that. Actually, let's go ahead and just do a round of introductions. I'll start my name's chris troutner, I founded the permissionless software foundation and fullstack.cache.

A

um I've been an active bitcoin cash developer for the last three years and yeah I'll leave it there. I don't need to go into detail david. You want to introduce yourself.

C

Sure, uh david r, ellen um assisting with business development for the permissionless software foundation been around for a while.

A

Daniel you want to introduce.

D

Yourself, hey, my name is daniel gonzalez. I've been working with chris and the permission slower foundation for the last two years and it was my first introduction to bitcoin cash. But I love.

B

It on right on uh stoyan, you want to introduce yourself. uh My name is stoyan jakov, and I worked for some bshgs bounties uh for the maybe uh last even not a year. Last couple of months.

A

It's all yes right on right on and appreciate you staying up so late to make this meeting yeah. I always find you, you add a lot of valuable, ask some valuable questions in these things, joe, you want to have a minute to introduce yourself.

E

Yeah sure so I'm joey king, I'm a developer for bitcoin abc I'm currently working on a wallet web app called uh cache tab and that's a browser extension and the web wallet and it uses bch api as its backend.

A

That's awesome, yeah, I'm hoping that our next meeting in two weeks joey can do a demo of the browser extension, because that is something that has been highly desired in this space is a um an improved uh browser extension, uh but a lot of what we're going to talk about today is going to be bchjs and some of the the changes that have been made and the changes that are coming up.

A

uh Let me share my screen again, um so this is going to involve me doing a lot of talking, because most of this is work that daniel and I have done and um but feel free to interrupt me and ask questions guys.

A

uh I love I love asking questions um and also I think these discussions work better if they're actual discussions, um and not just me on a soapbox uh but to get started, uh there's been a few features rolled out to bchjs in the last couple weeks, mostly these two biggest ones at the top sort all transactions and sort confirm transactions.

A

They are new methods added to the electrum x library and what they do is so this is the documentation for bchjs at bchjs.fullstack.cache.

A

You can get the api documentation, you can also get there by going to full stack, dot cash, slash documentation, and um so what these new features do is uh electrum x has an endpoint or has had an endpoint for getting transaction history of an address. So you give it an address and you get all all the transactions associated with that address.

A

So what these do is they return? They sort them.

A

um They don't always come back, sorted uh and and what they do is you can basically pass that output from electrum x into these to ensure that they're sorted by block height and then you can, you can add an argument either ascending or descending, it's descending by default, and this isn't terribly interesting for confirmed transactions that the main value this ads is for unconfirmed transactions, where uh bchjs will look at what the next block is going to be, what that block height is going to be and assumes that any unconfirmed transactions are going to make it into that block.

A

So then, you get a list back of all the transactions sorted by block height, and so you just just have one nice output and everything is sorted by block height and it includes confirmed and unconfirmed transactions.

A

uh So nice, nice little- these are little value, adds for for building wallets.

A

This next one get tx data vn okay, so when you get transaction, when you ask a full node for transaction data, um it will give you back an object that uh has the inputs and the outputs of the transaction and the outputs have addresses. But the inputs do not- and I don't know you know what the history is of- why it, the full nodes were defined that way. So this new function uh get tx data. So the that, though, uh that raw uh transactions class is historic.

A

This is the the class in bchjs that is used for getting transaction data and sending transaction data, and so I added this new get tx data method to it and it's exactly the same thing as calling git raw transaction, um but it it looks back one transaction at the parents of the of of each input and and extracts the address for for those.

A

So when it gives you back the transaction data, both the inputs and the outputs have addresses associated with them, and this has been a common problem for a lot of wallet software, so um I've hold I've heard it from multiple people like like. Why? Why don't the inputs have addresses? So I thought this would be a good value. Add to add this method.

A

It's probably also worth mentioning that I there is, I don't have any documentation for it yet, but there is an extension that I I prototyped to this. I can show that you guys where the code is, if you're interested, but it does the same thing where, after it gets the addresses for the inputs and outputs, it will then run each uh input and output through a hydrate utxo call. So if it's a token transaction you'll get the token amounts for each input and output as well.

A

So if you're doing a token based anything that involves tokens, that's really helpful um to you know from from a wallet application.

A

Standpoint uh before I move on, does anybody have any questions about these functions or application or use or suggested.

A

Improvements, okay, um so the next one on the agenda here is uh uh what I'm planning to do coming up and joey. This is where I'd I'd love to get some feedback from you is um I'm thinking about creating. So if you look at the bchjs uh documentation, it's broken up into its its sub components. It's subclasses there's an address class, a bitcoin cash class, a blockchain class.

A

And I don't think, there's a transaction class and there's no utxo class, so I'm thinking about adding a transaction class and a utxo class and as well as a math class and moving, I started a few months ago. I started this bch util library and it's got four or five different functions and um they're. Just sort of these handy macro methods that that uh that I use in all different sorts of of applications like rounding, rounding, uh the you know you get back like a bitcoin cash balance or a token balance.

A

So I just have a handy function to round that to two decimal points around it to eight decimal points, so that would go like in the math class and then there's like this find biggest utxo. That's a common like need, anytime you're trying to spend some bitcoin. uh You need to. Usually the most convenient thing to do is just find the biggest utxo in that address and then spend that. So that's a handy function that gets a lot of usage.

A

um This chunk chunk, 20 method is like, if you give it an array of any given size, it'll return. You back an array of arrays and each element is 20 elements long and that that corresponds to some of the api calls that let up to 20 elements. So it's a it's a really good way to like basically prepare your data before you hand it off uh to bch api. To like do something like give me the balance, you know say you have 100 addresses.

A

You would chunk that up into a bunch of 20 element arrays and then you would hand each 20 element array off to the vch api, and it would give you back the data on those 20 addresses. If you go above it, it's going to throw an error. So that's why that's why you want to do it so anyways, I'm thinking about move like basically deprecating this bch util library and moving these handy functions into bchjs.

A

It just seems more appropriate that they should live there um and uh and there's also some similar functions in minimal slp wallet, which is sort of the the wallet engine behind wallet.fullstack.cache.

A

um There's just some similar things like preparing handling um one of the utxo handling methods I want to bring in is, basically you can give it an address as input, and it's going to give you back uh the utxos um one.

A

That's all bitcoin cash uh utxos that are safe to spend one, that's all token utxos and one that then sort of an indeterminate if if utxo comes back and it can't be validated for whatever reason it can't be, can't be like explicitly determined if it's a token utxo or bch utxo, it would just sort of get thrown into this third bucket. That's like the indeterminate utxo array.

A

Does that sound valuable to you, joey.

E

uh Yeah so I mean, ideally, everything should just be in bchjs. uh The minimal slp wallet I think as well. Just the issue, at least from cashton perspective, is that we need one of the libraries to work in the browser and right now, there's some functions that you know we can only get from minimum slp wallet because of how it's how it's built, I believe, but as for the utils yeah like a chunk, 20 makes a lot of sense because otherwise app developers always have to write their own right.

A

Right: okay, good! Thank you! It's valuable feedback, yeah, there's certain things so yeah you're right, you brought up a good point. Their minimal slp wallet is targeted for the browser it's compiled with browserify. It includes a copy of bchjs in it. So anything that you know you want to do with bchjs.

A

It's there in that wallet and it's been nicely prepared for for front-end browser-based applications. um So this wouldn't really change any of that, and I also look at minimal slp. While it is sort of the next level of abstraction like bchjs. Are these primitives, whereas a minimal slp wallet has very simple functions for for doing real wallet things like what's my token balance, send a token.

A

uh You know real high level commands.

A

um Okay is the anybody else have any comments on that before we move on.

A

Okay, uh the next, uh the next thing that I also have a question for you. There joey is um the ecash and abc prefixes. My understanding is that the bitcoin abc uh has implemented support for both of them. That's a question, and then I I'm wondering if you have any insight into I I haven't even looked at this code. I need to just dic bchjs: has this prefix support for both bitcoin cash legacy and slp address format?

A

So I really just need to add these new two formats and I haven't really looked at them, but can you confirm.

E

A

These are implemented.

E

It's not urgent, I think, since this is still kind of up in the air, the way.

A

I'm handling right now.

E

With cash tab is I support ecash, but then, before the transaction is broadcast to bch api, it just converts it to the bitcoin cash prefix and since it's unlikely, anything else will change about the address format. That's always going to be possible.

E

So once we have some more clarity on this, I think you can worry about it, then, but otherwise I don't think there's any need to try to prepare for it. Since who knows maybe it'll change uh and it's also really straightforward to still have bch api work with whatever prefix you want, uh with a minor tweak on the app developer side, but yeah we'll need it hopefully, but it doesn't.

A

Okay, that's good to know um yeah, it's mostly it's not really! Actually under the hood under the hood.

A

I'll probably do the same thing convert everything to either legacy or bitcoin cash, but it's this conversion between uh prefixes that I'm mostly worried about, and it's not so much about bchjs as it is on, like wallet.fullstack.cache I'd like to be able to, um depending on which blockchain you've got that application pointed to whether it's bitcoin cash or bitcoin abc uh uh just have it automatically sort of natively use the prefix, because what I'm getting a lot of feedback from users and users from is that they don't understand that there's two blockchains that use the bitcoin cash prefix, and so I'm seeing a lot of what happened the other day, someone I I don't know, but it's been happening a lot lately where people are interested in bcha and they don't understand that you know they send bitcoin cash to an address.

A

It's on a different blockchain. It's it's incredibly confusing.

E

And so it's just.

A

E

The current systems- pretty careful, so that's true- it's possible to configure any web facing wallet app, though to just display any cash address or abc, address right now and still use bch api. um I forget what the library I'm using that does. That is called, but I think it's just the cache address library on npm and it'll accept a bitcoin cash prefix address and split it into its parts, and then you can give it any prefix. You want and it'll do the right, checksum. So we're able to use that now.

E

uh You know that that could be added at some point to bch api, but the whole point.

A

E

The prefixes is that, uh like you're saying, there's one that means one blockchain and one that means stuff like to prevent this ambiguity and since bcha hasn't really landed on one yet um trying to add anything to bchjs doesn't really solve the ambiguity problem. So it's.

A

E

Still a developer issue right now. There are tools that can solve it, um but unfortunately, there's not really a standard. So it's kind of up to the app devs.

A

Right, yeah, so that's why my plan is to support both that way. You know people can use either one um I mean at some point: we'll have the whole point right of having prefixes.

E

Is that there's only one or that it's that's not ambiguous right, so if we start supporting a bunch of them and it's like well, why do you even have prefix, and so some of the issues I think ideally like bcha- needs to just have one and it will no longer support the bitcoin cash prefix.

E

Unfortunately, that's not the world. We live in right now, so it's an issue. It should be flagged. I just I just don't think we have enough information yet to really put this into bchjs or dch api.

A

Okay, good good feedback, good feedback.

A

um Okay, does anybody else have anything else on that topic.

B

It will be- maybe I think, very difficult to implement these prefixes because most of the low-level conversion libraries will stop working like sop to bitcoin, address and legacy to something something most of them does not support anything else than bitcoin right.

A

B

The house, the changes, can go very deep inside to some like low-level libraries. You need to become too difficult to change everything.

A

Oh, that's a that's a that's! A good concern stoin. um So the these prefixes are actually a pretty shallow implementation. When you really get down into the guts of it like bchjs and and even lower uh uh libraries that make up bchjs, almost everything gets converted into a legacy address under the hood.

A

So this is really just a change at the wallet level, and so that's that's my I probably shouldn't have put it under the bch js uh bullet point here, because it's really something that concerns wallet.fullstack.cache more than it concerns bchjs or bch, api, okay! So yeah! It's really just a you know it's it's it's it's that final last mile, where you're presenting information to the user in a user interface.

A

That's that's where this is really concerned and then, um regardless of all the prefix, whether you use simple ledger or bitcoin cash or ecash or abc prefixes, they all ultimately get converted to a legacy address um when you're actually like creating a hexadecimal transaction. You know and interacting with the network at a low level.

A

uh So the next uh item on the list here message.fullstack.cache- this is just more of a psa or a public service announcement. um We use ipfs heavily on the message.fullstack.cache web application. It's used for sending end-to-end encrypted email for lack of a better word. It lets you send it to any bitcoin cash address and- uh and it does end to end encryption using the elliptic curve, cryptography, that's built into the bitcoin protocol, um but that encrypted message has to live somewhere uh until the recipient can can get it.

A

And that's the interplanetary file system, that's ipfs! So we had a company named temporal uh who recently went out of business uh and that's really unfortunate because they were providing a really valuable service.

A

um But I think, with file coin, coming out some of the things that uh protocol labs uh is doing the wins, sort of shifted for them and I don't really know the full story, but for whatever reason, they're they're no longer in business and uh but at the same time, this company textile, uh which I encourage people to check out because they're just they're really at the cutting edge of all of this ipfs and filecoin technology.

A

They have a concept called buckets which is very similar to s3 buckets um and it's they're a similar pinning service. It's it wasn't a drop-in replacement. Daniel did the the lion's share of the work here, but we've got it implemented, and this is also we've got functions in bchjs.

A

There is an ipfs class and these have also been updated. uh Where you can, I don't have these very well documented. So if anybody really wants to play with these reach out to me, but there's a web implementation that file server web and then there's file server, which is the node.js implementation that slightly different, how you handle the data, because node.js has buffers and web browsers don't um and uh but that's what lets you upload a file and pay bitcoin cash uh to have it hosted on the ipfs network?

A

And so that's how it's implemented in message.fullstack.cache.

A

Message.Fullstack.Cache also just has arbitrary file hosting there's a section where you can go there and just upload any file, and you pay one penny per 10 megabytes and it will just be hosted on ipfs for you, uh so that so big shout out to daniel uh great job uh doing that implementation and uh really glad that we kind of had to scramble there because temporal did not give us much of a heads up and- uh and so I'm glad that we didn't have a you know very much downtime with.

A

Message.Fullstack.Cache, um okay, so next item is uh wallet.fullstack.cache, is now available as an android, apk and joey. I wanted to point this out, for your sake really um daniel. I don't know how we discovered it. It was part it was through this hackathon, but daniel really dove into it. I have also like uh copied his work so that I understand the mechanics of it.

A

It's actually really slick you can take any gatsby app and just with a few steps, convert it into an android apk or an ios binary, whatever that's called now getting them into the play stores. That's a whole another problem, but uh it's pretty common um in the android world, the side load, apk files, um particularly in the crypto space, and it's pretty slick uh I I gotta say this whole and then and then the app like we didn't have to do anything. It just came out and worked pretty much flawlessly as a native app.

A

um So that was really surprising to me. I'm not used to things working that well um so anyways, just heads up, you should check into it. um Even if it's not you know a good fit for what you're doing um it's a good. It's a good thing to look at.

E

Cool yeah sounds great I'll check it out. I haven't heard it before so useful.

A

I think that we're going to um so one of the ways that I've I've learned from talking with you joey is that one of the ways our workflow is different than than maybe other other companies that would want to use our tools.

A

Is uh everybody struggles with this dichotomy between web browser, javascript and node.js javascript, and mostly it comes down to buffers this idea of binary data they're handled differently in those two worlds, and so there's webpack and there's browser five. Those are the two uh industry leading tools for moving between these two browser.

A

Node.Js worlds, webpack does not handle buffers very well, and but that is the preferred tool set for gatsby, which is our preferred tool set and so to solve this problem, we build the libraries on the node.js side and, and that way we can build really thorough tests.

A

We're trying to achieve 100 percent test coverage in in all these libraries we're building uh and uh and then we compile them for the front end with browser fi and then add them using unpackage as an external javascript library on the front end and it's sort of a circuitous route like a lot of I've, had more than one developer. Look at that workflow and be like why I don't get it. Why are you doing it that way?

A

um And but it has worked really well and that's one of the things that I liked about capacitor was that it it it adopts to this workflow, just fine, um so yeah, I just thought it'd be worth pointing out for you and for posterity for people who might watch this later sure I'll check it out.

A

Okay, well, that's the agenda. Does anybody have anything else? They want to talk about.

A

uh Well, actually, you know if you guys have anything interesting that you're keeping your eyes on this would be a great time to bring it up.

B

You think about uh a small uh extension to the wallet dot fullstack.cache about the nfts, who was just talking briefly on the twitter yeah. Thank you for bringing that up. It's.

A

B

Big change: it's just how to see a better view to the tokens.

A

So yeah yeah, the under the hood, there's really nothing to change. It's just a visual representation, yeah.

E

A

I really liked about your idea so for for people who are not mean stoyan um stoan, and I had a little bit of a discourse on twitter about this story has been doing some excellent.

A

um You know pushing for trailblazing with the whole non-fungible token idea in bitcoin cash and um he's had a couple great uh hackathon entries uh on that subject and- and uh so he's he's had a lot at this point story, and you have a lot more personal experience dealing with nfts than I do, and so he was suggesting that, rather than throwing nfts into the token here, so we're talking about wallet.fullstack.cash, it's got a section for tokens and he's.

A

He was suggested that, instead of just throwing the nfts in there with all the other tokens, the nfts should really have their own area and also one of the subtleties of nfts on bitcoin cash. Is that there's this idea of where you you create a group token like swords?

A

And then you use that to create child nfts like excalibur or the green dragon or like a specific sword, comes out of a group and so that that architecture naturally lends itself um to a lot of different things, and that's what stoyan's been exploring and also visually, it should probably be represented differently than a normal. Slp token would be represented. Did I capture.

B

That stoan! Yes, yes, because how to see this uh nft tokens, the the last hackathon was uh big hard to see. There was not much interest. I didn't get any hot sea people attracted to my project but outside of the hackathon.

B

This. uh If you know uh this uh a guy joy from the sop foundation.

A

Oh yeah yeah, I know who you're talking about he.

B

Created the waifu waifu faucet, it's a very utaki style, but this thing is generating, like uh hundreds, hundreds nfts per day, so they it start to how to see to gain some moment and, for example, this zapit wallet. Last day last update was especially about this wifey uh tokens.

B

They created a new uh like I was proposing a new page named collectibles, okay, because the the current uh wallet uh it's just for the tokens it's displaying, some like it, does not displaying uh the media, attach it to this nft, which is the most how to see attractive about any of these like these wi-fis. They have a connected icon on some server.

B

So when you get one of this thing, you look on some pretty animation girl connected to these nft tokens and you can send them to people so.

A

I haven't looked into this enough. The the the artwork that's associated with that nft is that.

B

A

In the document url, uh that's why.

B

How to see uh it's still very uh work in progress uh in the moment, there's maybe two main types, the one that I like is just to attach ipfs hash in the in the token uh document url this thing started with qm and it's pointing to to the some data in the uh ipfs, but especially this wi-fi guys, uh girls, uh their icons are getting generated, uh some from some ai on the fly.

B

So it's on some of this uh guide server. So if you go to the the usual explorer, you will not see them. If you go to simple ledger dot info explorer, you will see them. Okay,.

A

B

Cozy, so if you want to support this kind of tokens, it's easy just check if the the type is rifle and the warrior is like decided it's on this server, this one name. So it's just to have some if logic in this one if the class is rifle, get them from there, if not get them from ipfs.

B

So it's not a big deal to support these tokens, including and the one that will be maybe on ipfs, just very simple check.

D

B

The for the type but yeah it will give a great uh like uh visual on the these specific nft tokens. So most of the people will be attracted to use wallet.fullstack.cache because they can see their wife is there because there's still not many words that support it in the moment, only this zapie and I think other guys are working on this, like sign up dot cash. He also was uh announcing in the group that soon there will be support for them in in his wallet or their wallet.

A

So, oh some unsigned.

B

Yeah, uh it's like poker, poo, poker.

A

Yeah poker yeah yeah yeah, so this is this whole like that's. The thing is: there's no standard around this, like my hat's off.

E

A

Pushing forward, um I just put a link in the permissionless software uh telegram channel. uh There is actually a specification, it's still incredibly rough. I I've had talks with uh joey and james and jt about about this specific problem of how do you attach like, like art or some sort of piece of content to a token, and then the the second level problem is: how do you change that content down the road?

A

uh You know if you like, because tokens once you make them they're like everything on the blockchain they're immutable, um so there is actually like. This is great. I I don't think I have the bandwidth to focus on this, but I wish I did because this is an important problem to solve and we need to develop a standard around attaching artwork to an nft, but then also the bigger problem is mutable data data that can change over time.

A

So I have a very, very rough specification that captures a way to do that that I've explored with james and joey and jt. So I'd love to see someone work on this. I I don't really have the bandwidth to do it myself, but but this is an important problem someone's going to solve it and uh there's good ways to do it and bad ways to do it.

A

B

But one then very simple and quick step can be adding this hotseat collectibles to the to the web wallet like a gatsby extension. So you don't need to to include it in the distribution of the main source, but everybody can install it on their gatsby wallet.

A

Yeah yeah yeah daniel. Let's talk about this at some point um because it's largely a visual change. What stoyan's uh uh proposing and I think it would add a lot of value to wallet.fullstack.cache if we implemented it.

D

Yeah that could be, that would be a nice feature to add and we can discuss. How can we represent represented visually from the example that you did with the sword and the child, so it could be a cool good feature.

A

Cool yeah yeah. Thank you stoian for for championing that, because I you're right, I mean you. Your your intuition here is is totally right. No, it's very healthy.

B

Very hot topic: that's why, like I don't know it's, nobody still don't have it nicely done. Everybody is trying so why we can also try. Maybe our way will be better yeah.

A

Yeah, well, you know, maybe we can. uh Maybe we could get a bounty uh put together and fund it and maybe maybe you could do it.

A

All right, we'll we'll explore that uh we'll definitely explore that.

A

Okay, um I thought there was one other thing: oh yeah, so one other thing that's worth mentioning to this group is uh don. Wonton has been funding the development of an slp token bridge, which would let us move slp tokens um between blockchains between the bitcoin cash and bcha blockchain and the avalanche blockchain.

A

They have their own native token protocol that work is uh progressing very quickly. uh We've uh we're we've, got the bitcoin cash side of things completed and we're, uh probably in the next couple weeks we're going to have most of the avalanche side of the library completed, so you'll be able to burn and mint tokens on the bitcoin cash side and burn and mint tokens on the avalanche side and then that'll be like an npm library and then the next step from there is we're going to retrofit or refactor the token liquidity app.

A

So the one that's actually live in production on psfoundation.cache that won't change, we're going to fork it and create a new app. That's based on it and add this new library, and so just how the. If you go to psfoundation.cache, you can send you can interact with that token liquidity app by exchanging either bch or psf tokens you'll be able to do the same thing where you can create a token on the bitcoin cash side and a token on the avalanche side.

A

And then this app will be like an automated market maker and uh and allow you to move tokens between chains, and uh I think that's going to be pretty cool it'll. Let businesses move between chains. You know not completely frictionlessly, but I mean that's just not something that's possible today, so be nice to do something new.

B

There was also some guy announcing yesterday or today in the uh this bitcoin cash groups, about the bridge between the ethereum and bitcoin cash. This also will be interesting to take a look at. Is it really working.

A

Yeah, um anastasia and her team in the la in the coin party hackathon built an ethereum bridge um that lets you wrap slp tokens yeah on ethereum the same way they do with like btc. I.

B

I look, I look on their code, but it was.

A

It's just yeah, it's it's.

B

Oil and water- I know I had a hard time with.

A

It too yeah it.

B

Was not finished, I I couldn't.

A

B

Well, it's working yeah, I'm not sure. If it's the the same group, I don't think it was. It was some single guy announcing.

A

It yeah there's a lot of people working on this idea and and that's the thing is like it's just not my field of expertise, so I'm excited to see people working on the whole wrapped token concept, because that's gonna complement the token bridge that we're building really nicely and avalanche is uh their main focus right now is, is bringing uh is their c chain, their contract chain, so being able to take any code that runs on ethereum and just drop it right onto avalanche and have it work?

A

And- uh and so I think, between that technique of wrapping tokens and this token bridge that we're building there's going to be multiple um ways to move a token across blockchains, whether it's ethereum or avalanche or bcha or bch. Like um I imagine like a company like tether, who already has tokens on every blockchain that they they don't actually move them like like what we're proposing it's.

A

um You could actually just have a token that that you know you could use like the ethereum smart contract for actually creating and managing a token, even if, like the main use, is on bitcoin cash, where the transaction fees are lower, and so it lets it would let a business like use the blockchain. That's the most appropriate for the specific use case that they need.

A

Okay, well, I think we can wrap this up unless uh there's anything.

A

Else, right on, I appreciate you guys making it today um we'll have another meeting in a couple weeks and um yeah. I really appreciate you guys being here and your input uh really love how this community is shaping up.

A

Thanks chris cheers: everybody.