Roadmap v0.1

[pdet]

My current plan is to significantly extend support for querying Ethereum nodes. Here are the most likely next steps:

DuckDB Integration

• Get rid of CURL and use DuckDB HTTPFS
• Potentially use DuckDB's JSON reader
• Windows R-Tools

256-bit Integers

Ether values are actually quite large; due to the level of fractioning used, there is no guarantee they will fit in the current 128-bit integer values supported by DuckDB. It might make sense to implement this natively in DuckDB instead of in an extension, as it could be useful for the engine itself.

• 256-bit integer
• 256-bit (u)integer

Hex Types

Provide easy use of hex types for addresses and integral types. It will be a BLOB, with easy casting for hex-type varchars and numeric types.

• Hex Type -> BLOB
• BLOB "casts" to numeric values.

ETH contract Aliasing

Smart contracts are usually accessed by their hex address, but this affects usability significantly. I must extend the mapping of coin names to addresses.

• Script this.

Full support for eth_getlogs

• Finalize support of topics for eth_getLogs. Parameters can be more flexible, and support other possible topics.
• Support cardinality estimation
• Support Progress Bar
• Support Filter Pushdown. One interesting side-effect here, is that by moving to filter pushdown, I can probably remove the parameters from the function call and create the json rpc after the pushdown.
• Support Projection Pushdown