chaserene
chaserene
1. indeed it doesn't use EdDSA. I seriously misunderstood something about the current proving scheme. now I read up on scriptless efforts that may be compatible with CLSAG and [found](https://eprint.iacr.org/2022/744)...
@Gingeropolous > you should indicate that 2 versions of the tx-pow exist. The one where PoW is block inclusion consensus (which requires a fork), and one that requires a PoW...
@tevador that's an attractive idea. I've added it to the OP. ~~I'd just suggest another term, since "transaction weight" is already used in the penalty calculation. I'll use "transaction fee...
> the new weight would also apply to the penalty calculation it's good that you pointed that out, because it made me realize I made two mistakes in my calculations...
> If everything is within acceptable bounds, we ship the code using the wallet locked output cache as designed. If not, we go back to the drawing board. @jeffro256 what...
> If everything is within acceptable bounds, we ship the code using the wallet locked output cache as designed. If not, we go back to the drawing board. @jeffro256 I'm...
@kayabaNerve I don't see that stated in Jeffro's proposal. if that's the plan, then the proposal should say roughly this to make it explicit: "the protocol will stop honoring custom...
this is a very smart proposal because it introduces a new scarce resource to influence fork choice. that seems to be a requirement for tackling 51% attacks in Nakamoto consensus....