From 21fe457b55a5d648e39f42a331110b6d094b9c5c Mon Sep 17 00:00:00 2001 From: Kevin Date: Thu, 23 Feb 2023 21:57:37 -1000 Subject: [PATCH] thankfully the snapshot is not from 2013 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7098c8e..4136837 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ This is a one-click AWS deployment to run a Bitcoin full-node and [Ord](https:// ## Details - this is currently set up to run on AWS `us-west-2` -- it sets up a volume at `/mnt/bitcoin-ord-data` with bitcoin and ord data dirs synced up to February 22 2013 +- it sets up a volume at `/mnt/bitcoin-ord-data` with bitcoin and ord data dirs synced up to February 22 2023 - you can change regions, availability zones and instance types in `variables.tf`. Note that the data drive mount may fail for instances that use `nvme` type drives, and it may fail for other regions. If you have a use-case you need help with, feel free to create an Issue. - the AMI used is a standard AWS AMI - see `init.tpl` for the scripting done to your server (e.g. to make sure there are no backdoors here) @@ -50,4 +50,4 @@ This is a one-click AWS deployment to run a Bitcoin full-node and [Ord](https:// - [ ] on-chain info - [ ] queue controls - [ ] cancel - - [ ] prioritize / replace tx \ No newline at end of file + - [ ] prioritize / replace tx