Issues

• BIP 300: 26% censoring attack

  LayerTwo-Labs/bip300301_enforcer#665 · Filter by author someone235 opened on Oct 9, 2026

• CreateDepositTransaction accepts the full s<slot>_<address>_<checksum> deposit address and writes it unchanged; sidechains then burn the deposit

  LayerTwo-Labs/bip300301_enforcer#645 · Filter by author mblowes opened on Sep 27, 2026

• getblocktemplate fails on every call until restart when a mempool tx fails the template dry-run (e.g. "Old Ctip for sidechain N is unspent")

  LayerTwo-Labs/bip300301_enforcer#634 · Filter by author Wired4ncer opened on Sep 21, 2026
  3

• Provide an embeddable Rust crate integration for BIP300/301 validation

  LayerTwo-Labs/bip300301_enforcer#620 · Filter by author gosunuts opened on Sep 8, 2026
  1

• --enable-mempool: mempool tracking silently desyncs from the node — block templates become invalid and mined blocks are rejected (bad-txns-inputs-missingorspent)

  LayerTwo-Labs/bip300301_enforcer#611 · Filter by author mblowes opened on Sep 1, 2026
  6

• --enable-mempool: initial mempool sync can hang indefinitely (0% CPU, getblocktemplate stuck at -10) instead of completing or exiting

  LayerTwo-Labs/bip300301_enforcer#610 · Filter by author mblowes opened on Aug 31, 2026
  3

• Initial sync aborts fatally on header-only blocks (Block not available (not fully downloaded))

  LayerTwo-Labs/bip300301_enforcer#571 · Filter by author Wired4ncer opened on Aug 26, 2026
  2

• connect_block does not check that it contains M6 messages for all withdrawal eligible bundles

  LayerTwo-Labs/bip300301_enforcer#424 · Filter by author fumin opened on Jun 29, 2026

• connect_block artificially inserts unnecessary M4 messages

  LayerTwo-Labs/bip300301_enforcer#423 · Filter by author fumin opened on Jun 29, 2026

• put_pending_m6id should reject withdrawal bundle with duplicate m6id

  LayerTwo-Labs/bip300301_enforcer#414 · Filter by author fumin opened on Jun 27, 2026

• M6 should check that sidechain treasury value from "L1 tx.input" and "enforcer database" always match

  LayerTwo-Labs/bip300301_enforcer#413 · Filter by author fumin opened on Jun 26, 2026

• compute_m6id should check that payout_outputs are valid

  LayerTwo-Labs/bip300301_enforcer#412 · Filter by author fumin opened on Jun 25, 2026

• DB corruption

  LayerTwo-Labs/bip300301_enforcer#282 · Filter by author torkelrogstad opened on Mar 19, 2026

• Implement stalling logic during initial sync

  LayerTwo-Labs/bip300301_enforcer#249 · Filter by author torkelrogstad opened on Aug 20, 2025
  1

• Enforcer should exit with non-zero code on sync issues

  LayerTwo-Labs/bip300301_enforcer#248 · Filter by author torkelrogstad opened on Aug 20, 2025
  3

• Ideas for speeding up validator sync

  LayerTwo-Labs/bip300301_enforcer#237 · Filter by author torkelrogstad opened on Jun 24, 2025

• self-transfers to my own address reports 0 received satoshi and 0 sent satoshis

  LayerTwo-Labs/bip300301_enforcer#200 · Filter by author octobocto opened on Apr 30, 2025
  1

• Add rpc to sign message

  LayerTwo-Labs/bip300301_enforcer#164 · Filter by author octobocto opened on Feb 8, 2025
  5

• wallet: self-transfers have wrong amount

  LayerTwo-Labs/bip300301_enforcer#163 · Filter by author octobocto opened on Feb 7, 2025

• error: CUSF enforcer task w/o mempool

  LayerTwo-Labs/bip300301_enforcer#157 · Filter by author seriouscatsoserious opened on Feb 6, 2025
  4

• Allow for multiple deposit transactions using mempool ancestors

  LayerTwo-Labs/bip300301_enforcer#138 · Filter by author torkelrogstad opened on Jan 23, 2025
  1

• Add fuzzing and testing

  blockedenhancementsecurity
  LayerTwo-Labs/bip300301_enforcer#77 · Filter by author nchashch opened on Oct 31, 2024
  2

• Make sure that the implementation conforms to the specification

  blockedenhancement
  LayerTwo-Labs/bip300301_enforcer#76 · Filter by author nchashch opened on Oct 31, 2024

• Is it secure to expose cryptographic RPCs?

  blockedquestionsecurity
  LayerTwo-Labs/bip300301_enforcer#64 · Filter by author nchashch opened on Oct 26, 2024
  2