Regardless of what you may want, you're primary use case is to run a bitcoin node. So users running your software for this use case that are running bitcoin core will not know that they are not running the latest version. Do you have any plan to remedy this situation? I hope it's not to have us just continue waiting for 0.4.0 since we've already been waiting two years since the last update. nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcprfmhxue69uhhxetwv35hgtnwdaekvmrpwfjjucm0d5hszxthwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgtcuauf96
⚠ BITCOIN CORE v30.0, PLEASE READ ⚠
HOW TO INSTALL?
1. Stop Bitcoin.
3. Download "bitcoind.s9pk" from the bitcoin-core-startos Github release page. https://github.com/Start9Labs/bitcoin-core-startos/releases/tag/v30.0
4. In StartOS, navigate to System -> Sideload a Service
5. Upload bitcoind.s9pk
WHY DOWNLOAD INSTEAD OF MARKETPLACE?
Knots and Core share the same ID. This allows dependent services, such as lightning, to use either one. It also allows people to switch between them without needing to resync the blockchain.
Due to a bug in StartOS 0.3.5.1, if either service goes up in version, it will show as an "update" for the other service. This sucks and has caused people to think StartOS is trying to trick them into switching. To minimize confusion and mistakes, we release new versions of Knots and Core in parallel and require explicit action for switching. Not ideal, but a decent stop gap until StartOS 0.4.0.
Because there is no Knots v30.0, listing Core 30.0 on the marketplace would result in Knots users forever seeing Core v30.0 as a "update". As such, we are making Core v30.0 available as a download/sideload instead of listing it on the marketplace.
Discussion
Yes, as stated, this is fixed in StartOS 0.4.0. Until then, we think this is the best solution to a tough predicament.