iguana actually does need a DB, but so far only for saving privkeys and matching up accounts to addresses



my plan is to make a DB middleware layer and just put in a reference DB or two. if anybody wants to change the DB, they would need to make a glue layer, basically initialize a structure with the functions for put, get, etc. and set its name. then they can select that DB per API call or globally



this gets out of the my DB is better than your DB debates. The only requirement is that it needs to be a DB that is linkable into the iguana, though even external DB could be used with a glue layer that has the interface code



I dont think there is a one size fits all DB that will work for all cases, as some users could use sqlite, or even just a flat JSON file, since they would just have several addresses



while other use cases would be more like MGW, that would need to track arbitrary number of account mappings.