AP
← Developer activityStrong match

Antoine Poinsot

Public commit activity attributed with strong match confidence. This page describes observable work, not personal trustworthiness.

10 commits1 monitored projects2 candidates0 high-risk analyses
Project constellation

Where the commits appear

Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.

Monitored External sample
Projects connected to Antoine PoinsotA visual map of monitored and externally discovered repositories.APdeveloper10Bitcoin Core
Monitored evidence

CommitWatch projects

External discovery

Other public projects

No external sample loaded yet.

A verified GitHub handle is needed before external discovery.
Analyzed activity

Recent published watches

Message quality and risk characterize commits, never the person.

Informational 15 AI analysisMessage 53 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: release notes and bips doc update for #34779

This commit only updates documentation. It adds a release note and a BIP implementation list entry describing a prior code change (PR #34779) that makes Bitcoin Core ignore certain BIP 9 soft-fork signal bits per BIP 323. There is no code …

94e3ac0bby Antoine Poinsot+6−02 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

versionbits: update VersionBitsCache doc comment to match current behaviour

This commit only updates a code comment in a header file to describe the current behavior of a cache used for tracking Bitcoin softfork deployment status. No executable code was changed, and there is no security impact.

107d4178by Antoine Poinsot+2−11 file
No security note in commit
Informational 12 AI analysisMessage 75 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

qa: test we don't warn for ignored unknown version bits deployments

This commit only adds a new test case to Bitcoin Core's existing test suite. It checks that the software does not produce spurious warnings for version bits that belong to deployments that have been explicitly disabled/ignored. There is no…

1d524057by Antoine Poinsot+20−21 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

qa: use NORMAL_GBT_REQUEST_PARAMS consistently

This commit only changes Bitcoin Core's internal functional test code. It replaces hardcoded {'rules': ['segwit']} parameters with a shared constant NORMAL_GBT_REQUEST_PARAMS when calling getblocktemplate in tests. There is no change to pr…

ca5483a6by Antoine Poinsot+17−135 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

qa: regenerate hardcoded regtest chain for kernel lib unit tests

This commit only updates hardcoded test data used by Bitcoin Core's internal unit tests. The data is a pre-generated regtest (regression test) blockchain, and the change regenerates it so the tests continue to work with the current code. T…

98f706c6by Antoine Poinsot+210−2102 files
No security note in commit
Informational 17 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: Enforce additional version invariants in PSBT fuzzer

This commit only changes test/fuzzing code and adds equality operators to internal data structures so the fuzzer can check round-trip behavior of PSBT (Partially Signed Bitcoin Transaction) data. It does not change production transaction h…

Fuzzer invariant hardening (not a runtime security fix)Adds equality operators to PSBTInput, PSBTOutput, CScriptWitness for test assertionsAsserts PSBT version is 0 or 2 in fuzz target
470e52a5by Antoine Poinsot+66−83 files
No security note in commit
Low 29 AI analysisMessage 70 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: make sure PSBT serialization roundtrips

This commit adds a new fuzz test to Bitcoin Core that checks whether PSBT (Partially Signed Bitcoin Transaction) data can be serialized and then deserialized back to the exact same bytes. It is a defensive test meant to catch future bugs w…

Adds fuzzing assertion for serialization roundtripPrevents creation of PSBT output that the same code cannot re-parseDefensive regression test, not a runtime fix
d76ec4deby Antoine Poinsot+11−01 file
No security note in commit
Low 28 AI analysisMessage 58 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

miniscript: correct and_v() properties

This commit tightens the internal type-checking rules for a Bitcoin script feature called Miniscript. Specifically, it removes a property ('d', meaning 'dissatisfiable') from the logical 'and_v()' fragment because that property could never…

Type-system correction in Miniscript property computationRemoval of unreachable 'dissatisfiable' property for and_v() fragmentNo input validation or memory-safety change
4fab35cfby Antoine Poinsot+1−11 file
No security note in commit
Informational 15 AI analysisMessage 58 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

script: remove unused SCRIPT_ERR_LAST

This commit removes an unused macro named SCRIPT_ERR_LAST from a Bitcoin Core header file. The macro was simply another name for an existing internal counter and was not referenced anywhere in the code. There is no functional change, no bu…

51abf7d1by Antoine Poinsot+0−21 file
No security note in commit
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →