๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Stash Labs
@rgbstashlabs
Building the largest native liquidity pool for RGB. Unlocking RGB liquidity on Bitcoin.
๊ฐ€์ž… January 2025
42 ํŒ”๋กœ์ž‰ ์ค‘    570 ํŒฌ
๐Ÿ“ข From Managed to Self-Hosted: Giving Node Data Ownership Back to Users Stash Cloud has always auto-backed up managed nodes. Itโ€™s a platform-side default: node data lands on independent storage on a regular schedule, so when a machine fails, a container crashes, or a mis-op corrupts data, we can restore the node to the latest usable state โ€” usually without the user noticing. This layer is on by default; users donโ€™t have to do anything. But that solves service availability, not ownership. Auto-backups live in the infrastructure providerโ€™s storage, managed by the provider, restored when the provider decides. They stop most technical failures โ€” except one: a user who wants to keep their own node data and run an RGB Lightning node without depending on any infrastructure provider. This blog covers our exploration and practice of moving RGB Lightning nodes from cloud-managed to self-hosted. ๐Ÿ”—
๋” ๋ณด๊ธฐ