 the public testnet. So this is similar to our recent discussion on Robson. So if we create a public testnet like this, and even if we set the difficulty to something very long, then anyone can actually start mining on this and try the difficulty very quickly and first trouble. So will we limit the block miners by IP or by adding some signature and extra data? One of the two we have to do. Or just restart it every. Yes, my suggestion is to aggressively restart the chain. And move it every time you restart. So yeah, I guess I would like once we have a solution for Robson, I think, and we've tested it on Robson, I would be fine moving it there. But just in the meantime, till I get this out ASAP, I yeah, I'd also be in favor of restarting the chain more frequently. Then trying to solve this problem as like a blocker to getting this tested out. Yeah, I agree. We're starting the chain here as like we cannot restart the Robson, but we can restart this testnet. So there should be no attack or maybe if it starts being a problem, then we can do something. Yeah. Yeah. Probably good to just have a simple process that allows the people who involved to easily coordinate for where the new chain is, because you have to be able to find it and you don't want the attacker to be able to automatically move. So he's want some just human process that you just all agree. Okay, we'll post it in this private channel or whatever the chain idea. So we can. We can use the 1559 discord. And if that becomes a problem, we can use a chat between just, yeah. Yeah, just something that's not easily automated for the attacker to automatically follow. Like they have to be a human, paying attention, sitting around. Good point. Yeah. So let's start with the C market channel. And if, if that gets compromised, we can find something more robust. Sure. Okay. And yeah, then, sorry, go ahead. Yeah, I have a question about JSON RPC. So do we need to expose traditional fields on transaction structure on eith get transaction by hash endpoint? Yes, this is a plan. Yeah, I will write those for AAPs. I already wrote AAPs for the block data, and I will write AAPs for the transaction data. Yeah. Yeah, we expose that. But we checked it with on the so and on the so it's returned the old. Yeah, yeah, we still not have implemented. Oh, okay. Get transaction by hashing. Yeah. Yeah, yeah. Okay, anything else? No. Okay, cool. Yeah, so on the test nets, we have the POA, we said we'll finish that we've, we've tested, I think we did do this, right? Abdel, like we did run like the basic one and we yeah, yeah, okay. So this one's done. And then these two were basically combining into the fork of main net. Yeah. And then, I guess, yeah, other testing. So that's the mind you mentioned, you're using 1559 as part of a client network. Filecoin also has 1559 near protocol also has it. I should link the there a bit had the had the write up about it. And then from CELO. Yeah, they're also working on 1559. And they mentioned they can kind of help for testing with our work if there's overlapped, but their implementation is slightly different from Ethereum's. So I'm talking with them to see if there's, you know, anything where there's there's a lot of value for them to contribute. If people have ideas about testing that is kind of falling through the cracks and we're not having exactly the same implementation can be valuable. Please ping me. And then, yeah, just on the R&D side, I guess, in terms of theoretical analysis for the EAPs. Since the last call, the biggest change is Vitalik put together some slides about 1559 that were quite good. So if people want to have a look at that, they give a good overview. And then, yeah, in terms of comparing 1559 with the alternatives, I link your notebook here, Barnaby. And then Barnaby, in terms of simulations on the last call, you mentioned a couple more things. So I've just linked them there for people to be aware. And then the final bit is the community outreach. So we shared already, we've done a report with the catheters about people's thoughts on 1559. We're continuing to do more outreach, mostly around wallets and exchanges. It's going a bit slower now. So I'm not sure exactly when we'll have an update on this, but it's kind of happening in the background. And that's basically all I had on the agenda. Is there anything else that people feel we should bring up? Okay. So I'll share, well, I guess we'll have a full transcript for this. I'll share an update on Twitter today. And I guess the big things are just continuing to work on the tooling, getting the work started on the test net and trying to specify this transaction pool behavior. We have another call scheduled in four weeks. Does that seem reasonable in terms of timeline for people? Yes. Okay. Cool. Well, yeah. Thanks everybody for joining. I appreciate you all taking the time. Thank you. Bye. Thanks.