pull down to refresh
@optimism
326,864 sats stacked
stacking since: #879734longest cowboy streak: 75npub13wvyk...hhes6rk47y
Compliance.
It's one of the thing I hated about a US-based Bitcoin company I worked with in the past - they closed up shop because of "impossible" compliance, rather than working around this.
Sometimes, you have to resist.
However, if you're already non-compliant, then mass surveillance is very threatening.
PS: I'd say that we have both, today, everywhere.
WooCommerce is nice as an order-to-sats system (for digital goods) and yeah, BOLT-11, it's the only thing that makes sense from a "good design" perspective.
What I think that BIP-353 tries to solve is that you can have an authenticated address for on-chain transactions rather than an address that can be easily MITM'd (for example by browser extension malware) whereas with DNSSEC you can authenticate the input (as long as you don't get exploited in fetching the wrong expected key).
If 2 people do a payment at the same time, how do you do order matching if you had 4 orders open for that amount, with reusable payment addresses? Do you accept through LNADDR now instead of a BOLT-11 invoice? How does that work?
I mostly do research to create new tooling, but explicitly not with ChatGPT, because I am convinced that that (and all hosted chatbots with it) is a massive trojan horse, like FB. So I only use local implementations and I since a month and a bit I have a little set-up where I queue up large LLM requests and run it on rented cloud hardware.
Under (early) development:
- A "dream" mode where idle GPU/NPU time is being used on a RAG knowledge base to re-prioritize knowledge and update importance of stored knowledge. I'm not sure if this is going to work. For now I'm re-tooling it completely because I started in a wrong direction with it initially.
In "testing":
- A case builder that judges relevance of additional information to be added to a case. I.e. I can feed it a link, I'm currently working on this article from this morning. I programmatically extract all links and fetch all these, convert videos, podcasts and pdfs to text, which are added to a RAG knowledge base powered by
all-MiniLM-L6-v2as a sentence transformer. Then 2nd layer links are each examined for relevance, and so on. This is currently eating most my NPU on my laptop, especially since I'm messing with PDF transposition withminerUwhich takes for. ev. er.
In "production":
- News article aggregation against clickbait titles (#1006868) I use this daily as an alternative RSS reader. I need to rework it though, I'm thinking to maybe use Airflow for orchestration, the prototype suxx because of
NATSnot being stable when ran locally (which was why I wanted that and notkafka). - I noticed that I use Brave's AI-enhanced search results more often than the algo results.
I was interested in who voted yea from Dems... vote but it turned out more interesting to find that Massie did the NV thing. Wonder why.
It initially did that for me (after a couple minutes of status=500, I assumed that this happened while you fixed that) but after it started working again on my active browser, I restarted that and I've not had the issue since - it felt like some caching issue.
That's ok. Matt is the author of the BIP; I'm more interested in what others think. There's definitely a tradeoff going on - as there always is.
This was among the first (if not the first) dev mail list messages after the migration to google groups. I remember thinking the group broken because there were no replies - but the discussion was mostly on the pull req.
Personally I wouldn't use this - invoice/psbt swapping is better imho, but I understand that there's a need for a canonical signature to identify the counterparty, reducing MITM risk (though i could probably still MITM anyone with my supply chain attack into your fav browser extension we shall not name to do
s/@coinbase.com/@colnbase.com/)BIP 353 is a huge leap forward in security
From mentioned Bitcoin Design Guide's writeup:
Security & privacy
Every approach requires at least one intermediary that is being contacted to serve the payment information. This creates potential privacy and security risks that users need to understand. Key considerations:
- Intermediaries can track requests and metadata to build profiles of users and payment patterns
- DNS queries may leak information about payment relationships
- Services can potentially serve different payment information than specified
If the domain (website) where the payment information is stored, is not controlled by the user, we will refer to the address as “managed”. To be clear, intermediaries cannot move funds at the user-provided address. They can only prevent payment information retrieval, or re-route funds by returning different payment information.
So what is it? Huge leap forward, or huge leap backward?
Maybe, I personally don't care either way. Drawdown means more extractable sats per hour... so that's great, but it gets evened out with more sats being extracted on the expense side...
Archived: https://archive.is/mtFij
freqtradehas an ai mode that apparently works "because it analyzes multiple granularities". I'm not a trader so idk about all that but it sounded intriguing.