Anyone using noKYC domain and server hosting? Which one are you using? What are the downsides?

Planning to share a new service. Will be connected to emails.

#asknostr #plebchain #grownostr

Strange as this may sound, when a bee hive becomes too full, bees will form a "senate" comprised of more experienced bees to seek a new location.

When the location has been found, they vote on it by dancing as a collective until a consensus is reached.

#dev #cln

More work on askrene today. The infrastructure basically done, now I'm stealing Eduardo's min cost flow code.

But even that isn't trivial to drive. You get the min cost flow but the resulting path might be too expensive, or too unlikely, or too slow, and you need to tweak parameters (fees vs probability vs delay) then ask again. The current code does a binary search for this over a mu value from 0 to 127, so 7 times. I need to play with this, as I suspect we can shortcut this if we're "good enough".

Once you've got that, you look at htlc_max and htlc_min that had been published on the channels: you might have violated that too! If you hit the min, you remove that route and block the channel from future attempts. If you hit the max,, you reduce the amount you send down that route. Then you have some sats you still need to send, so you ask the min cost flow solver for the solution for just that part. This is actually unusual though: most channels route most payments.

The question is, how much goes inside the pay oracle, and how much can we punt to the caller? I think the caller can only specify the max fee and max delay, and the oracle needs to give the highest probability routes within those constraints.

I hope to have something tomorrow, but it's going to need a lot of tests! Fortunately this should be easier to test than a complete pay plugin.

Yes, Android (and GrapheneOS) uses file-based encryption by default. User profiles are also encrypted independently with their own keys. The data exfiltration is not the exploit but rather something that could be done from it, the encryption isn't affected.

The attack concept from the first vulnerability allowed brute forcing of an After First Unlock stock OS device thanks to exploiting the Fastboot firmware for a memory dump. It is a trivial platform reset attack. The issue was that Google did not erase the memory of an in-use device when switching to Fastboot. The stock OS doesn't clear freed memory while GrapheneOS does.

All operating systems incorporating disk encryption are vulnerable with this to a degree and the best mitigation is having the device purge encryption keys by rebooting or power off. We had defences like this already like auto-reboot and the option to disable USB entirely from hardware when an AFU device is in OS mode. Someone who'd be affected by this would be someone using the device the moment it had been stolen.

> "Without going into details, GrapheneOS adds that Google is only introducing a “partial solution” in the phone’s firmware to fix the second vulnerability. We’ve reached out to GrapheneOS for more information."

We sent a reply to this already but in the meantime this is what we meant:

While it appears they've changed the firmware to stop the reboot to recovery for wiping being interrupted, it's still not stealthy and the device could still have the power cut off, etc. before it completes. Wiping without rebooting is the full solution to prevent bypassing the factory reset, which we'll still need to implement ourselves for our duress PIN/password feature until they have an implementation that's included.

I often look at the price of electricity instead of the weather forecast. Low price often means lots of sun. But it can also mean lots wind (and rain), oops.

Prices in the chart below include a €0.13 / kWh tax and about €0.02 / kWh margin for the power company. Otherwise it would be zero or negative.

Fiat theft truth 🪓

#memes #zaps #bitcoin

moksha (Cashu mint) already working on on-chain support. We've just updated the protocol to implement more payment methods (like on-chain)

sorry triceps 💪

Bueno, hace como un mes o más que no entro por acá. Y la razón es sencilla: llegó un punto en el que no le encontré sentido estar acá. Pasa que ni tenía interacción para mi contenido, y mucho menos recompensas por ello, y ni hablar de no encontrar usuarios afines a mí. Por el contrario, en otras plataformas web3 encontré mayor acogida, incluso, en mi propio idioma, y más beneficios monetarios.

Quizás esté influenciado por la subida de $BTC, pero obtener recompensas acá se ha hecho, al menos para mí, imposible porque pienso que para quitarse a uno mismo y darle al otro, hace falta mucha implicación tanto con el contenido como con la otra persona, y sí, para mí el hecho de monetizar es muy importante, como mismo lo es para muchos y no es algo cuestionable. En cierto punto lo que pensé que era algo hermoso, se convirtió en algo contra mí.

Por el contrario, en otras plataformas he logrado monetizar mejor mi contenido especializado, incluso una mayor interacción y bastante rica, porque no supone quitarse uno para darle a otro, sino que la misma plataforma potencia la interacción y todos ganan al hacerlo. Tanto así que he podido aprovechar esas ganancias en beneficio personal.

No pretendo ni que me lean con todo este descargo, sino que quería de alguna forma dar cuenta de mi ausencia acá. Igual intentaré dar una vuelta de vez en cuando.

santa teresa, costa rica

who wants a surf class ? we accept ₿ 🏄‍♀️

I mean are you calling any of the other CLN commands/plugins when you are carrying out the min cost flow process?

How do you get the possible routes to use?