메뉴
Verify that the Java ME signer and Rust companion produce identical outputs for the same cryptographic inputs. Use after modifying any BIP39/32/44/84/173 code in either signer/ or companion/core/, or when updating protocol/vectors/.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build and test the burner-wallet monorepo. Runs signer (Java ME / Ant) and companion (Rust / Cargo) test suites. Use after making code changes to verify correctness, or when the user asks to run tests, build, or check the project.
Create a git commit following this project's Conventional Commits format with DCO sign-off. Use when the user asks to commit changes or when code changes are ready to be committed.
Security-focused review for cryptographic code in signer/ and companion/core/. Validates BIP standard compliance, checks for timing side-channels, verifies test vector coverage, and ensures cross-implementation consistency. Use when modifying files in signer/src/org/burnerwallet/core/, signer/src/org/burnerwallet/chains/, or companion/core/src/.
Enforces Java ME constraints when writing code in signer/. Prevents Java 5+ language features, validates CLDC 1.1 and MIDP 2.0 API usage, and monitors JAR size. Use whenever editing or creating Java files under signer/src/ or signer/test/.
Implementation guide for BIP174 PSBT (Partially Signed Bitcoin Transactions) on the Java ME signer. Reference for M1c milestone. Use when working on PSBT parsing, signing, or transaction construction in signer/src/org/burnerwallet/transport/ or signer/src/org/burnerwallet/chains/bitcoin/.
Monitor and optimize the signer JAR size to stay under the 1 MB budget. Use when adding new classes or dependencies to signer/, or when the user is concerned about JAR size.
| name | cross-verify |
| description | Verify that the Java ME signer and Rust companion produce identical outputs for the same cryptographic inputs. Use after modifying any BIP39/32/44/84/173 code in either signer/ or companion/core/, or when updating protocol/vectors/. |
The burner-wallet has two independent crypto implementations that MUST produce byte-identical results:
| Operation | Signer (Java ME) | Companion (Rust) |
|---|---|---|
| Mnemonic → Seed | Bip39Mnemonic | mnemonic.rs |
| Seed → Master Key | Bip32Key | keys.rs |
| Key Derivation | Bip32Derivation | derivation.rs |
| Path Parsing | Bip44Path | derivation.rs |
| Address Generation | BitcoinAddress | address.rs |
| Bech32 Encoding | Bech32 | address.rs (via bitcoin crate) |
| Base58Check | Base58 | (via bitcoin crate) |
# Signer (153 tests)
cd signer && JAVA_HOME=$SIGNER_JAVA ant test
# Companion (32 tests)
cd companion/core && cargo test
Both must pass with zero failures.
The source of truth is protocol/vectors/cross-impl-wallet.json. This file contains:
cat protocol/vectors/cross-impl-wallet.json
Both implementations reference this file in their tests:
signer/test/org/burnerwallet/chains/bitcoin/AddressTest.javacompanion/core/tests/integration.rsIf you changed any crypto code, run a diff check:
# Ensure both still reference the same vector file
grep -r "cross-impl-wallet" signer/test/ companion/core/tests/
When adding new functionality (e.g., PSBT signing), add vectors to protocol/vectors/:
protocol/vectors/<feature>.json{
"description": "Description of what this tests",
"vectors": [
{
"description": "Test case description",
"input": {
"mnemonic": "abandon abandon abandon ...",
"passphrase": "",
"network": "mainnet",
"path": "m/84'/0'/0'/0/0"
},
"expected": {
"seed_hex": "5eb00bbddcf069...",
"master_xprv": "xprv9s21ZrQH143K...",
"derived_xpub": "xpub6CatWDiKy...",
"address": "bc1q..."
}
}
]
}
Watch for these when implementations disagree:
index + 0x80000000, not index | 0x80000000 (same for positive values, differs for edge cases)