From bc49deb7a3acb83ceefb29ee09d9279e8f963db2 Mon Sep 17 00:00:00 2001
From: Bryan Stitt <bryan@satoshiandkin.com>
Date: Tue, 29 Nov 2022 21:29:34 +0000
Subject: [PATCH] template needs two curly braces

---
 TODO.md                   | 9 +++++++--
 web3_proxy/src/app/mod.rs | 2 +-
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/TODO.md b/TODO.md
index 585d621f..af698ee0 100644
--- a/TODO.md
+++ b/TODO.md
@@ -247,6 +247,11 @@ These are roughly in order of completition
 - [x] test that sets up Web3Connections with 2 nodes. one behind by several blocks. and see what the "next" server shows as
 - [x] ethspam on bsc and polygon gives 1/4 errors. fix whatever is causing this
   - bugfix! we were using the whole connection list instead of just the synced connection list when picking servers. oops!
+- [x] actually block unauthenticated requests instead of emitting warning of "allowing without auth during development!"
+- [ ] `cost estimate` script
+  - sum bytes and number of requests. prompt hosting costs. divide
+- [ ] `stat delay` script 
+  - query database for newest stat
 - [ ] period_datetime should always be :00. right now it depends on start time 
 - [ ] two servers running will confuse rpc_accounting!
   - it won't happen with users often because they should be sticky to one proxy, but unauthenticated users will definitely hit this
@@ -254,13 +259,13 @@ These are roughly in order of completition
 - [ ] add block timestamp to the /status page
   - [ ] be sure to save the timestamp in a way that our request routing logic can make use of it
 - [ ] if a websocket connection hasn't received a new block in a while, do a reconnect or just query the block. its possible that the node was syncing when the proxy started
-
-- [ ] actually block unauthenticated requests instead of emitting warning of "allowing without auth during development!"
+- [ ] put display name into our prod configs
 
 ## V1
 
 These are not yet ordered. There might be duplicates. We might not actually need all of these.
 
+- [ ] `change_user_tier_by_address` script
 - [ ] figure out if "could not get block from params" is a problem worth logging
     - maybe it was an ots request?
 - [ ] eth_subscribe rpc_accounting has everything as cache_hits. should we instead count it as one background request?
diff --git a/web3_proxy/src/app/mod.rs b/web3_proxy/src/app/mod.rs
index f92c5fd9..ab2c2dee 100644
--- a/web3_proxy/src/app/mod.rs
+++ b/web3_proxy/src/app/mod.rs
@@ -253,7 +253,7 @@ impl Web3ProxyApp {
         // safety checks on the config
         if let Some(redirect) = &top_config.app.redirect_rpc_key_url {
             assert!(
-                redirect.contains("{rpc_key_id}"),
+                redirect.contains("{{rpc_key_id}}"),
                 "redirect_user_url user url must contain \"{{rpc_key_id}}\""
             );
         }