SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Attaques Sybil : comment de fausses identités faussent la gouvernance décentralisée

0
·1 views

Une attaque Sybil consiste à créer de nombreuses identités fictives dans un système décentralisé afin de manipuler votes, décisions ou validations. En multipliant faux comptes, alias ou nœuds, l'attaquant donne l'illusion d'un soutien majoritaire alors que la décision repose sur une seule partie. Le guide explique pourquoi ce risque inquiète les réseaux décentralisés et comment il nuit à l'équité des décisions collectives. Il propose des pistes de détection, telles que l'analyse des comportements groupés, ainsi que des contre-mesures comme les systèmes de réputation ou les dépôts de jetons. Un scénario fictif illustre enfin les conséquences concrètes d'une telle manipulation sur la confiance des membres.

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 ·

Verkkolasku ilman laskutusohjelmaa: näin Finvoice 3.0 toimii käytännössä

Suomessa elinkeinonharjoittajalla on oikeus pyytää toiselta elinkeinonharjoittajalta koneluettavaa verkkolaskua sähköisestä laskusta annetun lain mukaan, joka tuli voimaan vuonna 2020. Kotimainen verkkolasku on useimmiten Finvoice 3.0 XML-muodossa, kun taas julkishallinto ja rajat ylittävä laskutus käyttävät usein Peppol BIS Billing 3.0 -standardia. Verkkolasku on tietue, jossa jokainen kenttä, kuten päiväykset, Y-tunnus, ALV-erittely ja IBAN, täytyy antaa erikseen oikeassa muodossa. Tarkisteiden, kuten Y-tunnuksen, viitenumeron ja IBANin, oikeellisuus voidaan varmistaa laskennallisesti, ja virheet kannattaa korjata ennen lähettämistä. Verkkolaskun tuottaminen ja sen lähettäminen ovat erillisiä vaiheita, ja pienelle yritykselle voi olla edullisempi tuottaa standardin mukainen tiedosto itse kuin hankkia kallis operaattorisopimus.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Guide Explains Two Qwen and H3 Workflows for Turning Product Stills into Hero Shots

The article describes a manual handoff: a product still is prepared and reviewed, then deliberately loaded into a video workflow, since the supplied JSON files do not automate this step. It covers two saved graphs, a 40-node H3 hero-shot graph and a 32-node Qwen Image 2.1 harmonization graph, with 108 combined links. The active image is upscaled with 4x-UltraSharpV2 and scaled to roughly four megapixels before reaching the encoder, though this does not guarantee a fixed final resolution. The old canvas and foreground/background route is bypassed and not connected to generation, so enabling those nodes alone will not change the output. The guide also notes that a LoRA is active in the main branch, so it is not an untouched baseline, and that the alternate branch uses a separate model and a second LoRA.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Choosing an Uptime Monitoring API for Logistics SaaS: Keep Cost Attribution in Your Own Telemetry

A DEV Community guide argues that a logistics SaaS should use an uptime monitor only to confirm endpoint reachability and alert on failures, while keeping cost attribution in its own telemetry. It recommends checking every critical HTTP endpoint, including the dispatch agent loop, and verifying free-tier frequency, quotas, and SLA terms before relying on them. The author suggests running four checks: a healthy response, a controlled failure alert, visible recovery, and a join to service and workflow records, with probes kept safe and idempotent. The piece compares UptimeRobot, Better Uptime, Healthchecks.io, Sentry, and Datadog by the failure shape each one observes. It concludes that pairing an HTTP monitor with a heartbeat for scheduled workers, plus application-owned attribution records, is a sound approach.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Temporal API in TypeScript: Handling Deadlines and Time Zones Correctly

A developer explains how the new Temporal API in TypeScript, available without a flag in Node.js 26, replaces the legacy Date object with dedicated types for instants, calendar dates and zoned times. The article notes that Date-based deadline logic often breaks around daylight saving time changes, such as when "plus 48 hours" yields a different result than "plus two days." It walks through building deadline logic for a fictional library, storing values in DynamoDB and deploying to AWS Lambda with the Serverless Framework. The piece also covers testing across DST transitions and migrating from Date or date-fns. Temporal is described as immutable and organized as a namespace containing several classes, each suited to different use cases.

0 comments Read more at DEV Community