Initial upload

Author: julian-bcw

.env.example

@@ -0,0 +1,22 @@
+ENDPOINT=https://ENDPOINT/
+FALLBACK_ENDPOINT=https://SECONDARY_SOLANA_RPC/
+BIGTABLE_CRED="SOLANA_BIGTABLE_CRED.json"
+GCP_CREDENTIALS_JSON_PATH="GCP_CRED.json"
+OUTPUT_DIR="output"
+QUEUE_NAME="solana-etl-output"
+QUEUE_NAME_BLOCKS="blocks"
+QUEUE_NAME_BLOCK_REWARDS="block_rewards"
+QUEUE_NAME_ACCOUNTS="accounts"
+QUEUE_NAME_INSTRUCTIONS="instructions"
+QUEUE_NAME_TOKEN_TRANSFERS="token_transfers"
+QUEUE_NAME_TOKENS="tokens"
+QUEUE_NAME_TRANSACTIONS="transactions"
+RABBITMQ_USER=USER
+RABBITMQ_PASSWORD=PASS
+RABBITMQ_PORT=5672
+RABBITMQ_ADDRESS=ADDRESS
+NUM_EXTRACTOR_THREADS=NUM_CORES
+ENABLE_METRICS=true
+METRICS_PORT=4000
+METRICS_ADDRESS=ADDRESS
+RPC_METHOD_TIMEOUT=30

CONTRIBUTING.md

@@ -0,0 +1,14 @@
+# Contribution & Style Guide:
+
+1. Pull requests should result in code that does not produce any errors when compiled.
+2. Pull requests should result in code that does not produce any warnings when compiled.
+3. Run `cargo fmt` before opening a pull request.
+4. Run `cargo clippy` and resolve any warnings.
+5. All functions should have a comment directly above that explains what it does at a high level. This comment should use the triple forward-slash `///` for compatibility with rustdoc.
+6. Each module should contain a high-level description of what the module is intended for. Make sure to use `//!` in the mod.rs file, and each respective rust source file.
+7. No more than 1 line of whitespace at a time. 
+8. Do not add any blockchain-specific code (besides conditional imports).
+9. Side-effects, assumptions, and “gotchas” should be accompanied by a `NOTE:` comment. 
+10. Try to follow a functional style, except for when calling async functions:
+- Use constants and immutable variables.
+- Use `Iterator` methods like `filter()`, `map()`, and `fold()`.