How one crypto wallet flags look-alike address scams before funds are sent

·2 views

Address poisoning is a crypto scam in which fraudsters create wallet addresses that mimic a real one's first and last characters, so users copying from history send funds to the wrong place. The developer of Tazvera, an open source wallet aimed at first-time users in India, built a set of checks called Tazvera Shield that run on the confirm screen before any transfer. These include red warnings and a locked Send button for look-alike or burn addresses, a calm note for first-time recipients, and a check for smart contract code. The checks rely only on data already stored on the user's phone, and the team reduced warnings after early testing showed users were dismissing them without reading. The wallet is a volunteer project and its code is publicly available under the MIT license.

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)

DeepSeek V4.1 Flash Input and Output Prices Shift Twice in One Week

A price tracker recorded two changes to DeepSeek V4.1 Flash within a single week, with input pricing rising from $0.02 to $0.045 per million tokens on October 31 while output pricing fell from $1.00 to $0.50. The net cost impact depends on whether a workload is input-heavy or output-heavy, with input-intensive use cases now costing more. The same tracker logged Kimi K3.1 Pro at $4.00 per million input tokens and $20.00 per million output tokens on October 27, though no earlier snapshot exists for comparison. Four new OpenAI model IDs under the "gpt-6.1-terra" naming, including batch variants, also appeared on October 27, but no pricing data was captured for them.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Pounce Atlas publishes licence breakdown for its open-source map demo data

Pounce Atlas, an open-source explorer for geographic datasets, has published a guide separating the licences that apply to its demo materials. The application code and documentation are under the MIT licence, while invented business and venue attributes in the demo files are dedicated to the public domain under CC0 1.0. Place names and approximate centre coordinates are sourced from GeoNames under CC BY 4.0, which requires attribution, and boundary geometry for South Africa is derived from Natural Earth public-domain data. The post also lists licences for third-party components such as the Inter font, Three.js, and several build and testing tools, and notes that the MIT licence does not cover third-party assets or trademarks. The guide is informational rather than legal advice, and its drafting was partly assisted by AI.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Exelon separates data center power demand into high-probability and pipeline groups

Exelon's October 30 earnings materials split projected data center demand into about 11 GW of high-probability load and roughly 23 GW in a future pipeline. The company defines the higher-confidence group as projects in advanced design or backed by FERC-approved transmission security agreements, with about 45% of that group holding such agreements. The figures appear on slide 15 of the third-quarter presentation. The disclosure concerns projected demand and does not confirm that corresponding facilities have been energized. The article's author argues that infrastructure teams should track each site's specific power milestone separately from regional demand forecasts.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Go 1.26's go fix can automatically migrate callers of deprecated functions

Go 1.26 rebuilt the go fix command with a source-level inliner that rewrites calls to deprecated functions when a //go:fix inline directive is present. Previously, a Deprecated: comment only triggered linter warnings and did not update call sites, leaving library authors to wait years for downstream code to migrate. The new approach works by placing the directive on a thin wrapper that delegates to the replacement API, so the inliner pastes that body into each caller. The article uses the ioutil.ReadFile to os.ReadFile case and a money package example to illustrate the technique. The author also notes that some calls cannot be inlined, so developers must understand those limits before relying on go fix in a release.

0 comments Read more at DEV Community