Grant Bartel (@grant_bartel) 's Twitter Profile
Grant Bartel

@grant_bartel

Building satreap.com. Ex-quant, AI engineer, and series 65 holder. Current Bitcoiner.

ID: 1819353965055606784

calendar_today02-08-2024 12:46:44

623 Tweet

357 Followers

172 Following

Grant Bartel (@grant_bartel) 's Twitter Profile Photo

It’s hard to avoid projecting our feelings onto Bitcoin. For some it’s not up enough. For others it’s too down. Just let Bitcoin do.

Grant Bartel (@grant_bartel) 's Twitter Profile Photo

SatReap is up! πŸš€ Now I need to work through the database initialization process and ensure it's all being updated daily. Got all the BTC prices and dimension tables initialized, so next is the simulation data... Baby steps to launch.

SatReap is up! πŸš€

Now I need to work through the database initialization process and ensure it's all being updated daily.

Got all the BTC prices and dimension tables initialized, so next is the simulation data...

Baby steps to launch.
Grant Bartel (@grant_bartel) 's Twitter Profile Photo

Euphoria was the theme of the past Bitcoin cycles. People experienced big drawdowns and left only to buy in at a higher price later. Boredom is the new theme (hoping I’m wrong). And people are going to leave only to buy in at a higher price later. Don’t leave. Just hold.

Grant Bartel (@grant_bartel) 's Twitter Profile Photo

Working through a couple issues with the SatReap deployment: 1. Daily data tasks are not running automatically 2. Form inputs aren't being parsed correctly Gonna work on #2 to just get it running, then move to #1.

Working through a couple issues with the SatReap deployment:

1. Daily data tasks are not running automatically
2. Form inputs aren't being parsed correctly

Gonna work on #2 to just get it running, then move to #1.
Grant Bartel (@grant_bartel) 's Twitter Profile Photo

Fixed the form input field issue, but something else is popping up. Never works in production like it does locally. Onward πŸ’ͺ

Fixed the form input field issue, but something else is popping up.

Never works in production like it does locally.

Onward πŸ’ͺ
Grant Bartel (@grant_bartel) 's Twitter Profile Photo

Knocked out two issues with SatReap's deployment: 1. Data wasn't updated daily, now it is. 2. Env variables were only set on 1 service, not others where required. Still need to test these updates but we're getting there! πŸš€

Knocked out two issues with SatReap's deployment:

1. Data wasn't updated daily, now it is.
2. Env variables were only set on 1 service, not others where required.

Still need to test these updates but we're getting there! πŸš€
Grant Bartel (@grant_bartel) 's Twitter Profile Photo

All necessary env variables are used for all services, so everything's doing its thing automatically. The Monte Carlo sim paths are being generated, but having some synchronization issues with S3. Working those out!

All necessary env variables are used for all services, so everything's doing its thing automatically.

The Monte Carlo sim paths are being generated, but having some synchronization issues with S3.

Working those out!
Grant Bartel (@grant_bartel) 's Twitter Profile Photo

I got the Celery workers and the code to work synchronously, so we're now updating Bitcoin simulation data directly in S3. Since the servers are in the same geographical region as the S3 bucket, we should be able to read/write DIRECTLY with very little latency. Testing now!

I got the Celery workers and the code to work synchronously, so we're now updating Bitcoin simulation data directly in S3.

Since the servers are in the same geographical region as the S3 bucket, we should be able to read/write DIRECTLY with very little latency.

Testing now!
Grant Bartel (@grant_bartel) 's Twitter Profile Photo

The Celery workers take up just under 250MB of memory each, so we can run about 8 workers concurrently in the worker service. Need to test this so we don't get any memory leaks in prod. Once that's done, I need to disable some URLs so there's only one access point to the app.

The Celery workers take up just under 250MB of memory each, so we can run about 8 workers concurrently in the worker service.

Need to test this so we don't get any memory leaks in prod.

Once that's done, I need to disable some URLs so there's only one access point to the app.
Grant Bartel (@grant_bartel) 's Twitter Profile Photo

Almost done "hardening" the app so (ideally) no issues happen when accessing it. Next I need to run my deploy checker script on the server and see if there are any issues still (takes a while). After that, we launch! πŸš€

Almost done "hardening" the app so (ideally) no issues happen when accessing it.

Next I need to run my deploy checker script on the server and see if there are any issues still (takes a while).

After that, we launch! πŸš€
FinancialFreedom (@finfreedom414) 's Twitter Profile Photo

Bitcoin is at $112k and we're talking about it being great buying opportunity. In a matter of months, Bitcoin will dip to $125k and we'll talk about buying the dip again. THE FLOOR KEEPS RISING, BECAUSE FIAT NEVER STOPS PRINTING.

Bitcoin is at $112k and we're talking about it being great buying opportunity.

In a matter of months, Bitcoin will dip to $125k and we'll talk about buying the dip again.

THE FLOOR KEEPS RISING, BECAUSE FIAT NEVER STOPS PRINTING.