Keybase chia how to#
Keybase chia mod#
Keybase chia software#

Keybase chia how to#

(EDIT: I did it!) README.md Update #2Īpart from the YouTube video explaining how to use yakuSwap (which is so bad it’s actually funny - and was also a community suggestion), a member of the Discord server suggested having written instructions on using the software. I had hoped he’d view my project and say something about it, but probably my tag got lost among the thousands of notifications he receives daily - still, I don’t regret trying and I’m sure I’ll get his attention some day. I posted a Tweet that addressed Bram Cohen, the ‘father’ of Chia (and BitTorrent). While testing, I tried passing values such as 0x0, None, and '' to the aggregate signature parameter, but I never tried giving it an empty aggregate signature, which is empty_agg_sig: G2Element = AugSchemeMPL.aggregate() or 0xc0 followed by a lot of 0s.Ī lot of people got worried by the ‘unsafe’ keywork in the opcode’s name, so that commit probably also improved the project’s credibility. The commit that made the change to the contract reads ‘thanks matt_howard’ - a member of the Chia team who (aside from saying that my work is “very impressive”) helped me realize how stupid I was.

Keybase chia software#

I stated in my last article that those instructions were there to bypass a limitation of the Chia wallet software - so what happened? The major change is that there are no more AGG_SIG_UNSAFE instructions.

Keybase chia mod#

Remember the Chialisp contract I presented in this article? This is ‘him’ now: ( mod ( SECRET_HASH AMOUNT FEE FROM_ADDRESS TO_ADDRESS YAKUSWAP_ADDRESS MAX_BLOCK_HEIGHT secret ) ( defconstant CREATE_COIN 51 ) ( defconstant ASSERT_HEIGHT_RELATIVE 82 ) ( defconstant ASSERT_FEE 52 ) ( defun-inline get_exchange_fee () ( + ( f ( divmod ( * 7 ( - AMOUNT FEE )) 1000 )) 1 ) ) ( if ( = ( sha256 secret ) SECRET_HASH ) ( list ( list CREATE_COIN YAKUSWAP_ADDRESS ( get_exchange_fee )) ( list CREATE_COIN TO_ADDRESS ( - AMOUNT FEE ( get_exchange_fee ))) ( list ASSERT_FEE FEE ) ) ( list ( list CREATE_COIN FROM_ADDRESS ( - AMOUNT FEE )) ( list ASSERT_FEE FEE ) ( list ASSERT_HEIGHT_RELATIVE MAX_BLOCK_HEIGHT ) ) ) ) I never tought about including screenshots in the README.md file - that was a brilliant idea! Oops They asked for screenshots of the app - it turns out that a lot of people didn’t know what yakuSwap actually did. Someone from the community messaged me asking if they could make a suggestion. Moreover, the Chia team started releasing tutorials about Chialisp and even built a new helper command-line utility - I was even able to add currying to my contract, a feat I wasn’t able to achieve before ingesting those resources! While yakuSwap is probably the first community-built app that uses Chialisp, everything could’ve been much easier if I waited one more week (I have no regrets, though!). Patience is a VirtueĪ few days after I finished reverse engineering a big part of the Chia wallet to find out how the RPC server & Chialisp work, the Chialisp site started getting updates.

As a nice bonus, Chia miners will start earning more fees. The fix is pretty elegant: instead of putting an arbitrary fee, set each transaction’s fee to 1/10000 of the total value - that way, performing the attack would cost more than the potential reward. If they syncronize this attack (which could cost less than $1, especially if done on a fork coin’s network) with the moment a party claims the second contract in the trade, a malicious actor could theoretically finish the swap and get both currencies, effectively stealing their partner’s money (the attacker would also earn a right to say “Not so atomic now, eh?” with a cowboy accent). However, I failed to consider one obvious flaw: someone could create billions of transactions with a fee of 2 mojo, thus flooding the blockchain and causing the transaction to not be included in a block for a few days. This would grant the transaction ‘priority’ over most of the others (fees are completely optional). The initial version of yakuSwap (v0.0.1-BETA) told users to use a fee of one mojo (smallest division of Chia 1 XCH = 1 trillion mojo). This also applies to all current Chia-based cryptocurrencies. This list is called the mempool and the transactions are sorted by - you guessed it - fees. In Chia, all transactions are stored in an ordered list before being included in a block. Below is a compiled list of ideas that significantly imporved yakuSwap in no particular order - and yes, most of them were suggested by someone on the Discord server. That number might not tell you much, but I’ve learned so many things that keeping them for myself would be selfish. If you’re reading this, I’ve succesfully launched yakuSwap version 0.0.4. Having a Discord server and listening to my users’ suggestions was a very good decision.