Kilombino
ꓘɨℓσꬺƄɨP110ꓘɳσ[Ŧƨ] 𓅦丰

🌸BarcelonaBitcoinOnly member
#BIP1️⃣🔟
🕳️Fiat Value Extractor
⛏️Humble Sat Stacker

Public Key

npub1qqqqqqzs0udz0dpa93ra5thgycmcmwsqw5qave53ltdrd75nrptqv5h62x

NIP-05 Address

Profile Code

nprofile1qqsqqqqqqpg87x38ks7jc3769m5zvdudhgq82qwkv6gl4k3kl2f3s4spp4mhxue69uhkummn9ekx7mqppamhxue69uhkummnw3ezumt0d5k87ww7

Publishing to

nos.lol

nostr.mom

Author Public Key

npub1qqqqqqzs0udz0dpa93ra5thgycmcmwsqw5qave53ltdrd75nrptqv5h62x

Show more details

Published at

2026-05-08T14:26:46Z

Kind type

0 Metadata

Event JSON

{ "id": "5d4f4b17b80221cb9dca756a1b3ece0d41d761cdbf12de3745204c7fcef5ae84", "pubkey": "00000000507f1a27b43d2c47da2ee826378dba007501d66691fada36fa931856", "created_at": 1778250406, "kind": 0, "tags": [ [ "alt", "User profile for Kilombino" ], [ "name", "Kilombino" ], [ "display_name", "ꓘɨℓσꬺƄɨP110ꓘɳσ[Ŧƨ] 𓅦丰" ], [ "picture", "https://image.nostr.build/23ee33cac87bf71b98e809e2d990cf0a04c5aa1af452383f8a845479e072d79f.gif" ], [ "banner", "https://pbs.twimg.com/profile_banners/1763693547914395648/1778250330/1500x500" ], [ "website", "https://kilombino.com" ], [ "pronouns", "Freedom/Warrior" ], [ "about", "🌸BarcelonaBitcoinOnly member\n#BIP1️⃣🔟\n🕳️Fiat Value Extractor\n⛏️Humble Sat Stacker" ], [ "nip05", "[email protected]" ], [ "lud16", "[email protected]" ], [ "client", "Amethyst" ], [ "i", "twitter:Kilombino_", "1921673123079881186" ], [ "i", "github:Kilombino", "559cbc1ce4dbc5de463f1f7ff0dede5d" ] ], "content": "{\"name\":\"Kilombino\",\"about\":\"🌸BarcelonaBitcoinOnly member\\n#BIP1️⃣🔟\\n🕳️Fiat Value Extractor\\n⛏️Humble Sat Stacker\",\"picture\":\"https://image.nostr.build/23ee33cac87bf71b98e809e2d990cf0a04c5aa1af452383f8a845479e072d79f.gif\",\"banner\":\"https://pbs.twimg.com/profile_banners/1763693547914395648/1778250330/1500x500\",\"displayName\":\"Kilombino[str]\",\"lud16\":\"[email protected]\",\"display_name\":\"ꓘɨℓσꬺƄɨP110ꓘɳσ[Ŧƨ] 𓅦丰\",\"nip05\":\"[email protected]\",\"pronouns\":\"Freedom/Warrior\",\"website\":\"https://kilombino.com\",\"payment_preference\":\"lightning\"}", "sig": "ae5de2f1fcb9008649b63b9161734fbbc03bb132d93bb4bd85da9e311463a85f86b5bf9810c538b4f5347ae85cf6d5afcc5f9aa47a40ccf11b2bbfef5b971878" }

Last Notes

2026-05-22 09:53:24 UTC

- reply

Thanks for sharing your campaigne

2026-05-22 09:52:50 UTC

- reply

#AQSTR Anima Prime: the animated film for the album “Disclosure”. #note14nz…t0ck

2026-05-21 08:03:30 UTC

- reply

Silk Road/Economías circulares

2026-05-19 21:38:06 UTC

Me parece que no tiene ningún sentido que pidan agua y una linterna para un niño con fiebre.
Me declino por la opción B: No abrir bajo ningún concepto. Hablar por la mirilla y pedir que se marchen.
Siguiente paso si no se van:
Smithers, suelta a los perros!

2026-05-17 07:26:40 UTC

- reply

#AQSTR #MunkyTreeDesign #Vlog #older #video #workshop #note1c2t…a7pn

2026-05-16 06:07:30 UTC

- reply

Mine solo or point it at your pool.
No account. No KYC. #note1s4y…ecvm

2026-05-16 06:06:32 UTC

- reply

Thanks for sharing the new tunes

2026-05-15 06:47:36 UTC

https://blossom.primal.net/8f2b1c5174bc0e09e958381a22e075fbb8f35918055adea53e704bcbadc067a0.jpg

2026-05-13 19:05:47 UTC

- reply

Thank your for sharing your projects

2026-05-13 19:05:18 UTC

- reply

#AQSTR SmartFlowSocial works as an installable mobile PWA #note13yv…ggcv

2026-05-13 05:13:53 UTC

- reply

I love this new song with Western vibe

2026-05-12 19:54:20 UTC

- reply

Put your hands up on the air!

2026-05-12 19:53:40 UTC

- reply

#AQSTR independent DJ & music producer deeply rooted in the cypherpunk & freedom ethos. #note1sm9…z9v8

2026-05-12 16:09:17 UTC

- reply

The nature always giving answers

2026-05-12 16:07:13 UTC

- reply

#AQSTR tuma is looking for technical writing work #note1v0k…ke2h

2026-05-12 14:10:55 UTC

- reply

This speech is disgusting to me.
Kill your heroes.
Including Aantonop.

2026-05-11 08:13:28 UTC

- reply

Thank you for the weekly dose of memes

2026-05-10 20:58:03 UTC

- reply

Heheh i love this kind of tatoos

2026-05-10 20:57:37 UTC

- reply

#AQSTR alien design tattooed on his friend #note1rf8…qmy3

2026-05-10 20:56:45 UTC

- reply

Thanks for the news Bitcoin tasks

2026-05-10 20:56:09 UTC

- reply

#AQSTR Many entrepreneurs are joining BitTasker.com #note1el6…7chn

2026-05-09 20:39:25 UTC

- reply

Who cares about Mac?

2026-05-07 21:03:47 UTC

- reply

Thank you for sharing your ideas

2026-05-07 16:36:28 UTC

- reply

Very interesting dashboard

2026-05-07 16:36:01 UTC

- reply

#AQSTR Check your odds 🎲 #note1p94…8zqv

2026-05-07 10:18:12 UTC

- reply

Holly mama!
I am the yield now

2026-05-07 05:10:14 UTC

- reply

https://24242.io/0a7f46b2fbf8d2779b957933d961778448dcd85b65cd70d8a518da6bdbde9bfc.jpg

2026-05-07 05:07:11 UTC

- reply

#AQSTR WEBFIVE by @Zaza 🎶 #note1eh4…2g88

2026-05-06 17:49:07 UTC

- reply

#AQSTR Check this out..... @Plebeian Market @Amplified Tunes @Katealing Peace Haleen #note183t…fddy

2026-05-06 17:20:02 UTC

- reply

I will listen if you don´t zap me too
Your music is the best of Wavlake!

2026-05-05 15:48:31 UTC

- reply

Will check out your interview

2026-05-05 11:44:55 UTC

- reply

👏👏👏🤝
Vas a la BCC?

2026-05-05 05:20:43 UTC

- reply

#AQSTR Nostr is the best way to advertising #note1p2v…xm8y

2026-05-05 05:20:09 UTC

- reply

Where could I start trying it?

2026-05-05 05:18:58 UTC

- reply

Hey nice idea and nice pins

2026-05-05 05:18:18 UTC

- reply

#AQSTR The GENESIS 113 PCB Pins, in collaboration #note1nym…qvd6

2026-05-04 07:54:01 UTC

- reply

Thank you for bring us the best weekly memes

2026-05-04 06:07:59 UTC

- reply

Music moves our soul 😍🍕

2026-05-04 06:07:08 UTC

- reply

#AQSTR #2140Sessions #music #Remixculture #note1xta…3g8f

2026-05-04 06:06:31 UTC

- reply

New instrument? Nostr is growth

2026-05-04 06:05:51 UTC

- reply

#AQSTR 🌿 Joining the @Divine HQ app #note1fv2…ds09

2026-05-02 18:00:32 UTC

- reply

You are losing zaps 🙃

2026-05-01 10:31:16 UTC

- reply

This update is in the right direction. Good work

2026-05-01 10:30:53 UTC

- reply

#AQSTR renting hashrate to your DATUM is the way #note1ggh…nagh

2026-04-30 13:02:46 UTC

- reply

I'm in!
🍕

2026-04-30 06:57:02 UTC

- reply

Thanks for sharing podcasts

2026-04-30 06:56:38 UTC

- reply

#AQSTR Uncensored Global Emergency Podcast #note1zc8…y6r0

2026-04-30 06:54:23 UTC

- reply

Always

2026-04-29 22:09:36 UTC

- reply

#AQSTR Loving the hashrate services #note1ug7…a5y4

2026-04-29 22:09:14 UTC

- reply

I want to choose my DATUM gateway to point the hashrate

2026-04-29 08:35:39 UTC

- reply

Thanks for promote the bitcoin economy

2026-04-29 08:35:02 UTC

- reply

#AQSTR BitTasker App is now available from the Google Play Store for Android Users #note137s…vhtl

2026-04-29 00:42:11 UTC

# Actualizar ThunderHub: la guía robusta
La guía Minibolt habitual para actualizar ThunderHub funciona, pero le faltan tres piezas importantes que, en mi opinión, no deberían faltar en infraestructura Bitcoin/Lightning: **verificación de firmas GPG**, **manejo del `package-lock.json` cuando da problemas**, y **activar el modo producción** para que el JWT secret no sea el default `123456789` (sí, en serio, ese es el default si no haces nada).
Esta es esa misma actualización, pero hecha bien. Sirve para cualquier release de ThunderHub a partir de v0.16.x.
---
## Setup único (solo la primera vez)
Antes de la primera actualización con verificación de firma, importa las claves GPG que firman los commits de ThunderHub. Son **dos**:
```bash
sudo su - thunderhub
# Clave 1: clave personal de apotdevin (mantenedor)
gpg --keyserver hkps://keys.openpgp.org --recv-keys 4403F1DFBE779457
# Si el primer keyserver falla, prueba con:
# gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 4403F1DFBE779457
# Clave 2: clave de GitHub web-flow (no está en keyservers públicos,
# se importa directamente desde GitHub)
curl https://github.com/web-flow.gpg | gpg --import
exit
```
¿Por qué dos? Porque ThunderHub mezcla commits firmados localmente por el mantenedor (clave `4403F1DFBE779457`) con releases generadas vía GitHub Actions o merge desde la UI web (clave `B5690EEEBB952194`, parte del archivo `web-flow.gpg`). Las dos firmas son legítimas; solo cambia el origen. Sin las dos importadas, alguna verificación va a fallar.
### Activar `NODE_ENV=production` (crítico, una sola vez)
Por defecto, el servicio arranca ThunderHub sin `NODE_ENV=production`. Esto tiene una consecuencia poco evidente: el código usa el JWT secret hardcodeado `'123456789'` en lugar de generar uno fuerte. Cualquiera con acceso a la red local podría forjar tokens de sesión válidos sin saber tu contraseña.
Lo arreglamos con un override de systemd:
```bash
sudo mkdir -p /etc/systemd/system/thunderhub.service.d/
sudo tee /etc/systemd/system/thunderhub.service.d/override.conf > /dev/null <<'EOF'
[Service]
Environment="NODE_ENV=production"
EOF
sudo systemctl daemon-reload
```
A partir de aquí, cada arranque de ThunderHub generará un JWT secret aleatorio fortísimo (128 hex). El único efecto visible: cuando reinicies el servicio se invalidan las sesiones activas y tendrás que volver a hacer login. Para uso personal es totalmente aceptable.
---
## Procedimiento de actualización
Estos son los pasos cada vez que aparezca una versión nueva. Mira primero los releases en [github.com/apotdevin/thunderhub/releases](https://github.com/apotdevin/thunderhub/releases) y lee el changelog antes de empezar.
### 1. Parar el servicio
Como usuario `admin`:
```bash
sudo systemctl stop thunderhub
```
### 2. Cambiar al usuario `thunderhub`
```bash
sudo su - thunderhub
cd thunderhub
```
### 3. Definir la versión objetivo
```bash
VERSION=0.16.1 # ← cámbialo a la versión que quieras instalar
```
### 4. Descartar cambios locales auto-generados
Tras cada `npm install` o `npm run build`, ThunderHub modifica algunos ficheros que luego entran en conflicto al hacer `git pull`. Los descartamos limpiamente:
```bash
git checkout -- package-lock.json schema.gql 2>/dev/null
```
### 5. Fetch del tag (sin merge todavía)
```bash
git fetch https://github.com/apotdevin/thunderhub.git tag v$VERSION
```
### 6. Verificar la firma GPG
Esto es la diferencia más importante con la guía oficial. **No mergees a ciegas.**
```bash
git verify-commit v$VERSION^{commit}
```
Lo que debe aparecer:
```
gpg: Good signature from "Anthony Potdevin <[email protected]>"
```
O alternativamente:
```
gpg: Good signature from "GitHub <[email protected]>"
```
Cualquiera de las dos es válida. **Si aparece "Can't check signature: No public key" con una clave que no reconoces, o "BAD signature", PARA y averigua antes de continuar.** No es paranoia: es la única forma de detectar un compromiso del repositorio.
El warning *"This key is not certified with a trusted signature"* es cosmético y se puede ignorar — significa solo que no has marcado las claves como confiables localmente con tu propia clave GPG.
### 7. Mergear
```bash
git merge v$VERSION
```
### 8. Leer el changelog antes de instalar
```bash
less CHANGELOG.md
```
Especialmente importante en saltos de minor o major. Busca breaking changes, variables de entorno nuevas, requisitos nuevos de Node, cambios en formatos de configuración. Apunta cualquier variable nueva que veas en la sección del `.env`.
### 9. Limpiar el build anterior (solo en saltos grandes)
| Tipo de salto | ¿Limpiar? |
|---|---|
| Patch (0.16.1 → 0.16.2) | No hace falta |
| Minor (0.16.x → 0.17.x) | Recomendado |
| Major o salto grande (0.13 → 0.16) | Obligatorio |
```bash
rm -rf node_modules dist src/client/dist
npm cache clean --force
```
### 10. Instalar dependencias y construir
```bash
npm install
```
Si te corta con `ECONNRESET` (típico en redes detrás de Tor o con conexiones inestables), aumenta los timeouts y reintenta:
```bash
npm config set fetch-retries 5
npm config set fetch-retry-mintimeout 20000
npm config set fetch-retry-maxtimeout 120000
npm config set fetch-timeout 600000
rm -rf node_modules
npm install
```
Los warnings de `deprecated`, `ERESOLVE`, y `npm audit` son ruido del ecosistema npm — son responsabilidad del mantenedor del proyecto, no tuya. **No ejecutes `npm audit fix`**, puede romper el build.
Cuando termine sin errores, construye:
```bash
npm run build
```
### 11. Verificar la versión
```bash
head -n 3 package.json | grep version
```
Debe coincidir con `$VERSION`.
### 12. Salir y arrancar el servicio
```bash
exit
sudo systemctl start thunderhub
sudo journalctl -fu thunderhub
```
### 13. Verificaciones críticas en el log
Busca estas dos líneas en los primeros segundos:
```
Getting production env variables.
```
Si pone `development` en lugar de `production`, el override de systemd no se aplicó. Revisa `/etc/systemd/system/thunderhub.service.d/override.conf` y haz `sudo systemctl daemon-reload && sudo systemctl restart thunderhub`.
```
Nest application successfully started
Application is running on: http://[::1]:3001
Connected to <tu-nodo>
```
Si todo aparece, sal con `Ctrl+C` y abre la web para confirmar que carga y conecta con tu nodo. Te pedirá la contraseña otra vez (esperado, el JWT secret cambió).
---
## Solución de problemas comunes
### `Your local changes to the following files would be overwritten by merge`
Te lo da `package-lock.json`. Solución limpia:
```bash
git checkout -- package-lock.json
git merge v$VERSION
```
### `gpg: Can't check signature: No public key`
Con la clave `B5690EEEBB952194`, importa la de GitHub web-flow:
```bash
curl https://github.com/web-flow.gpg | gpg --import
```
Y vuelve a verificar.
### `sh: 1: rimraf: not found` durante `npm run build`
Significa que el `npm install` anterior falló a mitad. Borra `node_modules` y reinstala:
```bash
rm -rf node_modules
npm install
```
### El servicio arranca pero `isProduction: false` en el log
El override de systemd no se aplicó. Revisa:
```bash
sudo cat /etc/systemd/system/thunderhub.service.d/override.conf
```
Debe mostrar:
```
[Service]
Environment="NODE_ENV=production"
```
Si no, recréalo con el bloque `tee` del setup inicial.
### Si todo lo demás falla
Antes de la opción nuclear (desinstalar y reinstalar), prueba:
```bash
rm -rf node_modules package-lock.json dist src/client/dist
git checkout -- package-lock.json
npm install
npm run build
```
---
## Procedimiento resumido (chuleta)
Cuando ya tengas el setup hecho, esto es todo lo que necesitas mirar:
```bash
# Como admin
sudo systemctl stop thunderhub
sudo su - thunderhub
cd thunderhub
VERSION=0.16.2 # ← cambia
git checkout -- package-lock.json schema.gql 2>/dev/null
git fetch https://github.com/apotdevin/thunderhub.git tag v$VERSION
git verify-commit v$VERSION^{commit} # confirma "Good signature"
git merge v$VERSION
less CHANGELOG.md
# Solo en minor/major:
rm -rf node_modules dist src/client/dist
npm install
npm run build
head -n 3 package.json | grep version
exit
sudo systemctl start thunderhub
sudo journalctl -fu thunderhub | grep -E 'isProduction|jwtSecret|successfully started'
```
---
## Por qué esto importa
Tu nodo Lightning gestiona dinero real. Cada actualización es una oportunidad para que código nuevo entre en él. Sin verificación de firmas, confías en que GitHub no esté comprometido, en que la cuenta del mantenedor no esté hackeada, y en que tu conexión TLS al servidor de GitHub sea íntegra. Verificar la firma GPG del commit reduce esa cadena de confianza a un único punto: la clave del mantenedor.
Sobre el `NODE_ENV=production`: este no es un fallo de las guías existentes per se. Es una decisión de diseño de ThunderHub que asume que el operador conoce el estado de su entorno. Si tú no lo sabes, lo razonable es asumir lo peor.
Si encuentras erratas, mejoras o casos no cubiertos te leo en los comentarios 🤙

2026-04-28 22:19:30 UTC

- reply

Nice to know more about blunt knife

2026-04-28 22:18:27 UTC

- reply

#AQSTR Blunt Knife's Music Video is out #note1z7m…etz7

2026-04-28 05:55:11 UTC

- reply

Nostr is different with your memes

2026-04-27 18:16:55 UTC

https://trobades.kilombino.com/2fde82ea8eff7739348214037d1112c5c5f1a8c9ce166e701c00fa4b3f061177.jpg

2026-04-27 16:47:34 UTC

https://trobades.kilombino.com/201b237a9cade1ed941f6530b3bacf542846971f6df3a92a1de6436eb1251f25.jpg

2026-04-27 09:19:59 UTC

- reply

Thank you for sharing circular economy

2026-04-27 05:03:07 UTC

- reply

#AQSTR The home relay of the Noderunners. Connect: wss://relay.noderunners.network #note1xyl…3npu

2026-04-26 16:34:46 UTC

- reply

Could I join?

2026-04-26 16:33:59 UTC

- reply

Received from primal, nos,lol and damus

2026-04-26 07:05:27 UTC

- reply

Perfecto
Esto es mas comprobable por seres humanos
Queda mas entretenido, visual y educativo para aprender hexadecimal
Que te parece? https://trobades.kilombino.com/c8db83c4be77f6665a0666182cfe5ff5a319d44116ce88c681bcc2deb306eb26.jpg https://trobades.kilombino.com/ea397bf182685c95f1289c2a3664faaac4bfa6902bf68c9e31812c011f2579b9.jpg

2026-04-25 23:29:28 UTC

Test Trobades Blossom https://trobades.kilombino.com/869061a6737a8e1a2dee528fe6e49a97506df4325cfdb78507e820386a2f056b.jpg

2026-04-25 23:27:14 UTC

I just annihilated 17 Nostr zombies from orbit using the NUCLEAR OPTION in #PlebsVsZombies! ☢️🧟‍♂️🧟‍♀️
💀 MAXIMUM CARNAGE ACHIEVED! 💀
My Zombie Score™ was 24%! What's yours?
🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟩🟩🟩🟩
Follow @npub1pvz…sd4h and join the hunt at: 🏹
https://plebsvszombies.cc

2026-04-25 23:18:57 UTC

- reply

Random.org

2026-04-25 22:10:21 UTC

🌐 Running my own Nostr relay at my open free for all relay:
wss://relay.kilombino.com
What it does:
• Strfry-powered, running on my homelab in Spain.
• Actively routing events from relay.minibolt.info, nos.lol, nostr.mom, trobades.kilombino.com, relay.primal.net and relay.damus.io — so your notes land here even if you don't publish directly to it
• Write policy plugin: keeps spam out while staying open to real humans
• Rate limiting per npub to avoid abuse
• Member of the BBO community (Barcelona Bitcoin Only)
If you want to stay in sync with the Catalan Bitcoin/Nostr scene, add it to your relay list:
wss://relay.kilombino.com
If you run your own relay, consider adding mine to your routing config — I'll do the same. DM me.
#nostr #relay #bitcoin #homelab #spain

2026-04-25 21:31:23 UTC

- reply

I am only saying what I am doing.
Closing the faucet slowly.
And a mix of being lazy and know what is happening in the Google gulag.

2026-04-25 21:28:17 UTC

Claude-Donals https://blossom.primal.net/cb2bf347ba58eb814823c00ffb71ec730ccab6f118802a7c5c9b6aa10104c258.jpg

2026-04-25 16:45:57 UTC

I run two cameras on my GrapheneOS phone, and each one saves to its own folder — so the streams never mix.
The first is Open Camera, which I use for "normie" photos with no faces, nothing sensitive. Shots go into their own dedicated folder, and the whole thing lives in a separate profile alongside Google Photos and Sandboxed Google Play. That profile is what I let the Google ecosystem see: a curated, boring version of my life that makes me look like a regular user.
The second is GrapheneOS's native Secure Camera, in my main profile — fully degoogled, no Sandboxed Google Play, nothing phoning home. Its photos save to a completely separate folder (the default DCIM/Camera), isolated from anything Google can touch. That's where the photos I actually care about live: the ones I don't want touching Google's servers, ever.
Keeping the folders separate means there's zero risk of accidentally syncing a private shot to the cloud — Google Photos only ever sees the folder I point it at. I like being selective. I only feed Google what I want it to know about me: sanitized, faceless, low-signal data, while everything personal stays local, on-device, and out of the cloud.
Have a nice weekend beautiful people!

2026-04-25 14:32:49 UTC

- reply

No, no uso ni usaré Spark ni ninguna app que lo integre

2026-04-25 14:10:39 UTC

https://blossom.primal.net/0a7f46b2fbf8d2779b957933d961778448dcd85b65cd70d8a518da6bdbde9bfc.jpg

2026-04-23 20:45:17 UTC

- reply

Not your keys, not your notes

2026-04-20 14:29:32 UTC

- reply

Thank you for the Best Weekly Memes

2026-04-20 13:51:53 UTC