Have been trying methylene blue as a supplement to see if it can improve my focus, memory and energy. So far nothing super noticeable except for green pee!

Great to get this out in to the wild and get some more feedback on v2 which is a big upgrade IMO View quoted note →

@R1F /create a moving string section that is recorded in high fidelity.

Learned a little more how the legacy credit card system works and got a good bit of motivation to hasten my family's move to a full Bitcoin standard. We go to the local farmers market every week and we had noticed that sometimes if we went to a shop after our farmers market run, our credit card would decline despite having plenty of available balance. This continued happening and got so bad that our card had become unusable. I eventually got fed up enough that I called the bank to find out what is going on. Turns out that when we make many payments in quick succession to many different vendors, it triggers the banks fraud detection. So each week we would go to the market and our card would get suspended. Someone from the bank would then need to manually review our txs, see that it is the same farmers market pattern and then restore our card. Apparently due to black friday sales, they have been swamped with fraud detections, so they have been slower at restoring cards, making our card unusable. The bank said that essentially this process is going to happen every time we go to the farmers market. I am honestly shocked at how rudimentary their fraud detection algorithms must be. Surely not too hard to see that the pattern of txs matches the same pattern at the same time, every week. I had no idea how much manual work was going in to keeping our card working. Obviously Bitcoin fixes this and really reiterates how much of a step improvement Bitcoin is compared to the legacy system. The only reason we use a credit card over a debit card is that in the case of it getting compromised, then the bank is on the hook for stolen funds, which i my experience makes them much more responsive. We are going to stop being lazy and just get out cash each week from now on. Much better privacy and better for the merchants. Long term I really want to start getting paid in Bitcoin and then hopefully find some good tools for interacting with the legacy system. Really need to orange pill my local farmers, but that is proving difficult after already trying multiple times.

I have been hacking away at a v2 of Clams which involves pretty much completely rewriting the codebase, and I thought that I should try building it in public for anyone that might be interested. The plan is to regularly add posts to this thread showing progress, what problems I am trying to solve, what I am stuck on and any other thoughts I have. Hopefully I can get some good feedback/criticism along the way, but either way, sometimes it is just good to write things down to get them out of my head :). So for some background I thought I would try and sum up the goals, top level features and people we are building for in v1 of Clams and contrast that with the upcoming v2 aspirations. CLAMS V1 Goals Remove barriers to spending Bitcoin on a daily basis by making connecting to a remote node simple and performant, payments on the go easy and make tax time a simple one click export. Who Are We Building For? Version 1 of Clams is built for individuals running a personal Core Lightning node and want a clean UI tailored to sending and receiving payments on the go, managing channels, offers and accounting exports. It uses a novel way of connecting to the node which does not require any additional software to be installed alongside the node and rather uses the lightning network (BOLT#1, BOLT#8) itself to connect. Top Level features - Progressive Web App, runs on any device with a web browser and can be saved to the home screen for a native app like experience. - Privacy focused. All data is stored locally. No logging, no Google scripts. - FOSS. - Internationalisation built in, but we need to create/commission translations. - Secure and private connection to the node using the lightning network messaging protocol and the Commando plugin for RPC access, with no additional software required. - Send and receive payments with a clean and easy to use interface. - View and manage channels. - Create and pay/withdraw BOLT12 Offers. - One click download of CSV files that can be uploaded to tax services like Koinly for simple end of year capital gains/loss calculations. - LNURL client side support for Pay, Withdraw and Auth protocols CLAMS V2 Goals Create a unified Bitcoin app that provides individuals and businesses that are running on a Bitcoin standard all of the tools needed to efficiently manage their finances. Who Are We Building For? Bitcoiners. People who are living in the future and are living in a mostly post-fiat world. It could be anyone from an individual running a single node, to a professional routing node runner, to a business that has multiple nodes and cold storage devices for their funds. Typically most Bitcoiners have their bitcoin and transaction data spread across multiple apps, nodes and cold storage devices. Clams is where all of the data can be synced/imported locally on a device. Once that data is collated in the one place, metadata can be added to enhance it to provide greater insights as well as automated tax and business reporting. Top Level Features Not all of these features will be in the initial v2 release, but are definitely ones that we want to implement eventually. - All of the features that are listed above in v1 will be carried over. Some of those features will also get a bit of a revisit to enhance them further. - Cross platform app. In addition to the PWA, we are using Tauri to create a native desktop app and down the line native mobile apps. This means that you can use Clams on whichever device and platform you like. - Connect more than just a Core Lightning node. We will have a more generic "Connections" interface which generalises any kind of Bitcoin connection for syncing data. We currently have plans to support LND, xpub, multisig, Electrum and Esplora (for private xpub data) connections. Further in the future we may implement Coldcard and Jade connections as well as other protocols such as Fedimint and Cashu connections. Basically any kind of transaction related to Bitcoin, we should be able to make a connection interface for Clams. The app itself just interacts with a generic interface for any given connection and just progressively enhances the available features based on what is available to a specific connection. - One click profit and loss statements for businesses. We have been working with @Satoshi Pacioli Accounting to understand what Bitcoin businesses need for automatic data exports for simple accounting and that is part of what prompted a need for a full refactor of the app. We will be also adding an API to our server and a DB with historical Bitcoin prices to facilitate automatic capital gains/loss calculations - Built in Koinly replacement that is focused only on Bitcoin and will not require sending all of your personal transaction data to a server, but generated from your local enhanced data. This will require generating tax documents for each jurisdiction, so will likely be rolled out one at a time. - Add metadata to your data to further enhance it's usefulness. This will make one click profit and loss statements, charts showing changes over time for certain types of transactions and a lot more possible. We will have reasonable default metadata out of the box for transactions (think "income", "expense", "transfer") and since the app will have an overview of all of your transactions it can automatically detect transfers. I also find personally that in our house we find ourselves asking "How much did we spend on food in the last 3 months" so that we can effectively adjust our budget to know how much bitcoin we can buy lol. The ability to tag transactions is key to being able to gain these kind of insights. - Charts that show you totals and data over time allowing you to get a big picture view over your finances. You can customise the charts using your custom metadata to show whatever you like. - Lightning Address and LNURL Pay codes straight to your node(s). Add your node auth (to create invoices) and connection details and our server will handle all requests to your address and pay codes. You can give details for multiple nodes for fallbacks just in case one of your nodes is down. - Lightning node uptime monitoring. Our server can regularly attempt to make a peer connection to your node and if it is down, send you a notification via Nostr DM, Email, Text. - Encrypted data backups to our server as well as a simple export of all data from your device to backup yourself. - Advanced permissions and device syncing so that you can selectively allow others access to certain parts of your data. An example would be allowing your accountant read only access to updated data so that they can open Clams and export necessary data/documents on a quarterly basis. - Custom data imports for when automatic syncing connections cannot be created (think custodial apps like WOS). - Clean UI integrations with node providers like Greenlight and Voltage so that a node can be spun up and automatically connected to from within the app. - Clean UI integrations with ways to buy and sell Bitcoin from within the app with API's from Azteco, The Bitcoin Company, Bitrefill etc. - Clean UI integrations with leading LSP providers and Liquidity Ads protocol for getting inbound liquidity. - Nostr DMs and identity key management that can be derived from your root node keys. - Professional business invoicing that pays directly to your node(s), cold storage etc. We plan to monetise the app some time next year so that we can try and create a sustainable business ourselves that brings in sats flow. We will probably follow the Mutiny+ model and make a collection of the above features available for a monthly subscription fee, but will always have a core set of features that are useful and free out of the box. Most likely the features that are included in the paid subscription are the ones that require our server to work which cost resources on our end. So if you got this far, you may want to follow along and try out the app on a CoreLN regtest node yourself. The latest code is available on the v2 branch here: https://github.com/clams-tech/App/tree/v2 I am going to start adding posts to this thread to catch you all up to where v2 is currently at and then regularly post updates as I go.

Is there a Nostr extension that allows you to manage and switch between multiple identities?

@ODELL Just finished listening to the latest RHR. Thanks for the shoutout in the software releases section! Just wanted to say that Clams is too good a name to be left to a dead shitcoin and the inspiration comes from the great essay "Shelling Out" by Nick Szabo. We are reclaiming it and repurposing it to be the name for what we envision will become an essential FOSS app for individuals and businesses that are operating on a Bitcoin standard. Hopefully one day our app will be useful for you and @Marty Bent to manage your businesses. You will be able to privately connect all of your nodes, xpubs and sync all of your transaction data in one place locally on your device. Tag your transactions to categorise them and then have one click P&L statements, capital gains reports to give to your accountant. @Satoshi Pacioli Accounting is helping us understand what Bitcoin businesses need and we are hard at work building it out. I will hit you up to give it a try once it is ready if you are interested?

How many people thought they were getting a call on signal whilst listening to the latest RHR 🤣

@Gigi @DETERMINISTIC OPTIMISM 🌞 We are looking at applying for a grant for Opensats, and I noticed in the FAQ that the grants go out once a year. Since the last one went out recently, will the next round go out a year from now? Is it worth applying now, or wait until closer to the next announcment?