clanker team just shipped our v0.0.2 token factory

this enables:
+ DEGEN, CLANKER, HIGHER, ANON pairings 
+ ERC20Votes
+ change which address gets rewards
+ configurable fee splits (3-ways)
+ allowlisted addresses to deploy (batch txns)
+ burnable 🔥

Still needs dev work for this on UI/AI 

s/o @yungwknd 👑

Bravo - been waiting years to see these innovations!

So I can set a third-party split recipient for a portion of my 0.4% LP fee share at launch. But post launch, I relinquish control over that portion, as only that current third-party recipient (or Clanker as contract owner) can reassign the split via the replaceUserRewardRecipient function.

My concern: I’ve been working on an experiment that requires the third-party split share to remain “locked” or soulbound to the originally designated address, to thwart abuse or transfer to another party.

So does the ERC-721 LP token always remain housed in the contract (using “mapping” type distros), regardless of changes to third-party recipients?

If yes, could I use an 0xSplits address I control as the recipient, allowing me to retain distribution control by forwarding 100% of the ERC-20 fees to the intended third-party recipient? If ERC-721’s transfer out of the contract on recipient changes, this won’t work since 0xSplits can’t hold ERC-721’s.