What went wrong
->Qué salió mal
Then:The problem wasn't a network outage or a hack. OCEAN's own setup glitched, and some miners got pointed at a chain that isn't the real Bitcoin chain. BIP-110 is an old, abandoned fork — it's not moving. So those miners were hashing away on a dead ledger, producing nothing of value, for the better part of a day.
Translation:El problema no fue una interrupción de la red ni un hackeo. La propia configuración de OCEAN falló, y algunos mineros fueron dirigidos a una cadena que no es la cadena real de Bitcoin. BIP-110 es un fork antiguo y abandonado — no se mueve. Así que esos mineros estuvieron minando en un libro de contabilidad muerto, sin producir nada de valor, durante la mayor parte de un día.
Next:It's not clear exactly when the error started or how long it took to spot. The pool only said the issue affected a subset of miners, not the whole operation. That's a small mercy, but for the people caught in it, 18 hours of wasted work is a real hit.
Translation:No está claro exactamente cuándo comenzó el error ni cuánto tiempo se tardó en detectarlo. El pool solo dijo que el problema afectó a un subconjunto de mineros, no a toda la operación. Eso es un pequeño alivio, pero para las personas atrapadas en ello, 18 horas de trabajo desperdiciado son un golpe real.
Next:The rebate
->El reembolso
Next:OCEAN is making it right with direct payments. The pool will distribute about 0.3 bitcoin in total to the affected miners, calculated to match what they'd have earned on the main chain during that window. It's not a huge sum, but it's the principle — miners shouldn't lose out because of a pool-side mistake.
Translation:OCEAN está enmendando el error con pagos directos. El pool distribuirá alrededor de 0,3 bitcoins en total a los mineros afectados, calculado para igualar lo que habrían ganado en la cadena principal durante ese período. No es una suma enorme, pero es el principio: los mineros no deberían perder por un error del lado del pool.
Next:The rebate is a one-off, not a policy change. OCEAN didn't say whether it's changed its configuration to prevent a repeat, but you'd hope so. A mistake like this is embarrassing enough without happening twice.
Translation:El reembolso es único, no un cambio de política. OCEAN no dijo si ha cambiado su configuración para evitar que se repita, pero uno esperaría que sí. Un error como este es bastante vergonzoso sin que ocurra dos veces.
Next:Who's affected
->Quiénes están afectados
Next:Only a portion of OCEAN's miners were caught in the error. The pool didn't name names or give a headcount, just that it wasn't everyone. For those who were, the rebate should land in their accounts soon. OCEAN said it's distributing the payments, but didn't give a specific date.
Translation:Solo una parte de los mineros de OCEAN se vieron afectados por el error. El pool no dio nombres ni un número exacto, solo dijo que no fueron todos. Para los afectados, el reembolso debería llegar a sus cuentas pronto. OCEAN dijo que está distribuyendo los pagos, pero no dio una fecha específica.
Next:For the rest of the mining community, this is a reminder that even established pools can fumble the basics. The good news is OCEAN owned up and is paying back what's owed. The bad news is 18 hours of hashing power went to a chain that will never produce a block.
Translation:Para el resto de la comunidad minera, esto es un recordatorio de que incluso los pools establecidos pueden fallar en lo básico. La buena noticia es que OCEAN asumió la responsabilidad y está devolviendo lo que se debe. La mala noticia es que 18 horas de poder de hash se fueron a una cadena que nunca producirá un bloque.
Now we need to assemble the content with all paragraphs and headings in order. The original article has:...
thenWhat went wrong
then...
etc. So we'll preserve that. We'll put the entire content as a string with HTML. Also, ensure we use "bitcoin" as "bitcoin" or "BTC"? The original says "bitcoin" lowercase. We'll keep "bitcoin" or "bitcoins" as appropriate. In Spanish, it's often "bitcoin" (singular) or "bitcoins" (plural). We'll use "bitcoins" for plural. Also, "fork" is used as is, but in Spanish it's often "bifurcación" but "fork" is also used. Since it's a technical term, we can keep "fork" or use "bifurcación". The original says "fork" - we can keep it as "fork" or translate to "bifurcación". I'll use "bifurcación" to be more natural, but "fork" is also common. Let's use "bifurcación" for clarity. Actually, in the context, "BIP-110 is an old, abandoned fork" - we can say "bifurcación antigua y abandonada". I'll do that. Also "hashing away" - we can say "minando" or "haciendo hash". We'll say "minando". Also "dead ledger" - "libro de contabilidad muerto" is fine. Now we need to produce the JSON. Let's write the final content string. We'll use double quotes for JSON, so we need to escape any double quotes inside. The content has no double quotes, but we have apostrophes? No, we have single quotes? No. We have "—" em dash, that's fine. We'll just include it as is. We'll also ensure the meta description is translated. Now, let's construct the JSON. { "title": "OCEAN Mining Pool reembolsa a los mineros tras un error de
