SShortSingh.
Back to feed

The Six Pits: A Pre-Flight Checklist for Swapping Signatures on a Live Chain

0
·1 views

NIST finalized the algorithm part years ago — FIPS 204 made Dilithium a standard, and NIST's transition guidance (https://csrc.nist.gov/pubs/ir/8547/ipd) now tells every product to plan the move. The algorithm was never the hard part. Everything downstream of it is. Consider this the flight checklist we wish every chain ran before swapping signatures on a network that already has users. Canonical encoding.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Como Penso e Resolvo "Count Ways to Distribute Candies" em Elixir (Corrigido)

Como Penso e Resolvo "Count Ways to Distribute Candies" em Elixir Um Guia Completo da Força Bruta aos Números de Stirling (com a correção sobre listas vs. tuplas) Correção importante: A versão original deste artigo afirmava que a solução DP usava "um array unidimensional" em Elixir. Isso está errado. Em Elixir, [] é uma linked list (lista encadeada), e operações de acesso indexado (Enum.at/2) e atualização (List.replace_at/3) são O(n), não O(1). Para obter acesso indexado O(1), é preciso usar tuplas ({}), que são o equivalente mais próximo de arrays em Erlang/Elixir.

0
ProgrammingDEV Community ·

5 things I learned letting an AI coworker run my Windows PC in the background

I'm not a programmer. I ran cafes and a convenience store before this. For the last few weeks I've been letting an AI coworker I built (by intuition, with a lot of help from AI) do real work on my own Windows PC every day: filling web forms, organizing files, managing a small game project and video jobs. Here is what surprised me, with numbers from my own logs only. Most "computer use" demos take a screenshot, think, click, take another screenshot.

0
ProgrammingDEV Community ·

Identity Document Photos Explained: A Secure API Approach for Uploads

The page says identity-photo-retention-breach, the account identifier is present, and the oldest undeleted original is 26 hours past its deadline. That is how an API should handle identity document photos: name the broken retention promise and the affected object. A page saying "image API errors increased" is not useful; it gives the responder a graph to distrust and no bounded action to take. TL;DR: process the minimum required, keep an original only for the duration of the identity check, and make scheduled deletion part of the data path. Prefer metadata over bytes when dimensions or format