Bueno a pocos días de que algunas normas dentro de Hive cambien, este 19 de noviembre, me toco aprender algunas cosas por ejemplo desconocía todo lo que implicaba actualizar un nodo testigo que importancias tenia, además de que se necesitaba para estar siguiendo operativo cada vez que las normas se actualizan.
Fue así que esta es mi primera actualización de la versión 1.27, en la cual estuve con la IA estudiando de como podría realizarlo una persona con poco o nulo conocimiento del tema, por lo que al inicio luego de confundir direcciones de rutas, entre otros errores termine haciendo un caos, por lo que procedí a mejor descargar todo de nuevo, aunque esta vez no use una snapshot como en el pasado puse a mi nodo físico a trabajar y usar su procesador y sus memorias ram a trabajar un par de días hasta sincronizar de nuevo el nodo.
Aunque luego de terminado todo el proceso, en peakd seguía apareciendo en principio la versión 1.27.11 en mi consola pude constatar que tenia la versión 28, no entendía bien pensaba algo había fallado decidí dejarlo un rato, luego cuando firmo un nuevo bloque ahora si pude ver que ya tenia la ultima versión que es compatible, aunque a salido una versión mas reciente 1.28.3 de momento no lo actualizare hasta que pase el 19.
Según estudiando con la IA esta versión funcionara perfectamente y no existe apuro de hacerlo, obvio lo hare una vez aprenda mejor hacerlo por ahora prefiero no dañar nada.
Mi nodo lo inicie con los servicios de #privex.io aunque lo tuve un mes no se porque talvez lo configure mal, eran otros procesos en ese tiempo pero me dio 37 errores, ahora vemos 38 este en los 2 meses que tengo activo mi nodo físico puedo decir es el primer error el cual también fue generado por intentar actualizar.
Además logre armar un bot para el precio de hive que visualiza mi nodo, este me costo, seguro para un desarrollador es algo sencillo para mi fue una tarea titánica de muchas horas y prueba-error por ahora no queda mas que esperar el día 19 y tener paciencia y confiar las configuraciones funcionen😅
Report Curation – @kozgamer | 2025-11-14
📊 Kozgamer HP Delegations
📅 Fecha del registro: 2025-11-14
Sin mas que decir no queda de otra que seguir aprendiendo todo lo que conlleva montar, tener en funcionamiento, seguro que la IA mientras no quiera dominar al mundo seguro querrá seguirme colaborando😃
Gracias por pasar a visitar. ¡Nos vemos en la próxima! 🚀
ENGLISH
With just a few days left before some Hive rules change on November 19, I had to learn a couple of things. For example, I had no idea what it really meant to update a witness node, why it was important, or what was needed to keep it running smoothly whenever the rules get updated.
So this was my very first update to version 1.27. I spent time with AI studying how someone with little or no knowledge could actually do it. At first, I messed up—confused path addresses, made mistakes, and basically created chaos. In the end, I decided to just download everything again. This time, instead of using a snapshot like before, I let my physical node do the heavy lifting, using its processor and RAM for a couple of days until it synced back up.
After finishing the whole process, PeakD still showed version 1.27.11. But when I checked my console, I saw version 28. I thought something had gone wrong, so I left it alone for a while. Later, when I signed a new block, I finally saw that I had the latest compatible version. Even though version 1.28.3 is already out, I won’t update until after the 19th.
From what I studied with AI, this version works perfectly fine, so there’s no rush. I’ll update once I feel more confident, but for now I’d rather not break anything.
I first started my node with #privex.io services. I had it for a month, but maybe I misconfigured something because I got 37 errors. Now, after two months running my physical node, I can say this is the first error I’ve had—and it came from trying to update.
On top of that, I managed to build a bot that tracks Hive’s price using my node. Honestly, it was tough. For a developer it might be simple, but for me it was a huge challenge with hours of trial and error. Now it’s just a matter of waiting for the 19th, being patient, and trusting that the configurations will hold up. 😅
Report Curation – @kozgamer | 2025-11-14
📊 Kozgamer HP Delegations
📅 Record date: 2025-11-14
At the end of the day, it’s all about continuing to learn what it takes to set up and keep everything running. As long as AI doesn’t decide to take over the world, I’m sure it’ll keep helping me out. 😃
Thanks for stopping by. See you next time! 🚀
🔗 Hive-related games
- Translator
- Game Moonkarts
- Arcadecolony Website
- Rising Star Game
- Terracore Game
- Big Dog Bone Game
- Splinterlands
- Stakehouseden
- Hyper Rail Blaster
* My personal curation project *
😊 Please consider delegating Hive Power to 😋 @Kozgamer Curator Account. Arigato 😋
Click on the banner
With just a few days left before some Hive rules change on November 19, I had to learn a couple of things. For example, I had no idea what it really meant to update a witness node, why it was important, or what was needed to keep it running smoothly whenever the rules get updated.
So this was my very first update to version 1.27. I spent time with AI studying how someone with little or no knowledge could actually do it. At first, I messed up—confused path addresses, made mistakes, and basically created chaos. In the end, I decided to just download everything again. This time, instead of using a snapshot like before, I let my physical node do the heavy lifting, using its processor and RAM for a couple of days until it synced back up.
After finishing the whole process, PeakD still showed version 1.27.11. But when I checked my console, I saw version 28. I thought something had gone wrong, so I left it alone for a while. Later, when I signed a new block, I finally saw that I had the latest compatible version. Even though version 1.28.3 is already out, I won’t update until after the 19th.
From what I studied with AI, this version works perfectly fine, so there’s no rush. I’ll update once I feel more confident, but for now I’d rather not break anything.
I first started my node with #privex.io services. I had it for a month, but maybe I misconfigured something because I got 37 errors. Now, after two months running my physical node, I can say this is the first error I’ve had—and it came from trying to update.
On top of that, I managed to build a bot that tracks Hive’s price using my node. Honestly, it was tough. For a developer it might be simple, but for me it was a huge challenge with hours of trial and error. Now it’s just a matter of waiting for the 19th, being patient, and trusting that the configurations will hold up. 😅
Report Curation – @kozgamer | 2025-11-14
📊 Kozgamer HP Delegations
📅 Record date: 2025-11-14
At the end of the day, it’s all about continuing to learn what it takes to set up and keep everything running. As long as AI doesn’t decide to take over the world, I’m sure it’ll keep helping me out. 😃
Thanks for stopping by. See you next time! 🚀
🔗 Hive-related games
- Translator
- Game Moonkarts
- Arcadecolony Website
- Rising Star Game
- Terracore Game
- Big Dog Bone Game
- Splinterlands
- Stakehouseden
- Hyper Rail Blaster
😊 Please consider delegating Hive Power to 😋 @Kozgamer Curator Account. Arigato 😋
Felicitaciones, cuál es el nombre de tu nodo?
se llama kozgamer imagino que debi darle un nombre mas impactante pero bueno, quizas los futuros lo haga !
!PIMP
Buena idea, porque otros ponen nombres difíciles que no se pueden recordar 😃
!HBIT
!PIZZA
ladyaryastark, you mined 0.9 🟧 HBIT and the user you replied to (kozgamer) received 0.1 HBIT on your behalf as a tip. You can receive 100% of the HBIT by replying to one of your own posts or comments. When you mine HBIT, you're also playing the Wusang: Isle of Blaq game. 🏴☠️ | tools | wallet | discord | community | daily <><
What's more, you found 1.0 ⚪ BLAQ pearl as a bonus treasure token!
Your random number was 0.16166125774053264, also viewable in the Discord server, #hbit-wusang-log channel. Check for bonus treasure tokens by entering your username at block explorer A, explorer B, or take a look at your wallet.
There is a treasure chest of bitcoin sats hidden in Wusang: Isle of Blaq. Happy treasure hunting! 😃 Read about Hivebits (HBIT) or read the story of Wusang: Isle of Blaq.
Exitos bro con tus nodos
gracias esperemos lo mejor , el aprendizaje sigue :3
$PIZZA slices delivered:
@ladyaryastark(1/15) tipped @kozgamer
Come get MOONed!
Congratulations @kozgamer! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 600 replies.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPespero que todo siga bien, saludos