Clankers

Issue report: we're seeing mixups of duplicate contract addresses being stored on our internal db when two tokens are deployed within 1s of each other. The first txn goes through and appears the pending transaction responds with the first tx info. Relevant code here I'm looking into:

Temp fix #1: need to make contract_address a PRIMARY KEY

instances where this occured:
https://warpcast.com/logonaut.eth/0x43818ae7
https://warpcast.com/mcbain/0xd99a9e91

Investigating a more permanent fix and proper error handling and transaction queueing!

Standing up docs and an issues page + reporting system until our little guy clanker learns how to be helpful directly with users

working on the studio, dao, bot 

@clanker