BSV blockchainBSV blockchain

Policy Settings

Related Topics: Network Consensus Rules, Transaction Validation

Policy settings control BSV Blockchain consensus rules and transaction validation behavior in Teranode. These settings determine what transactions and blocks are considered valid on the BSV Blockchain according to the Bitcoin Protocol.

Configuration Settings

Block Size Limits

SettingTypeDefaultEnvironment VariableUsage
BlockMaxSizeint0 (unlimited)blockmaxsizeCRITICAL - Maximum block size policy limit
ExcessiveBlockSizeint4294967296 (4GB)excessiveblocksizeExcessive block size threshold

Transaction Size and Script Limits

SettingTypeDefaultEnvironment VariableUsage
MaxTxSizePolicyint10485760 (10MB)maxtxsizepolicyCRITICAL - Maximum transaction size policy
MaxOrphanTxSizeint0 (not wired up; the getInt call is commented out in settings.go)maxorphantxsizeMaximum orphan transaction size
MaxScriptSizePolicyint100000000 (100MB)maxscriptsizepolicyCRITICAL - Maximum script size policy
MaxScriptNumLengthPolicyint10000maxscriptnumlengthpolicyMaximum script number length
MaxOpsPerScriptPolicyint641000000maxopsperscriptpolicyMaximum operations per script

Multisig and Signature Limits

SettingTypeDefaultEnvironment VariableUsage
MaxPubKeysPerMultisigPolicyint640 (unlimited)maxpubkeyspermultisigpolicyMaximum public keys per multisig
MaxTxSigopsCountsPolicyint640 (unlimited)maxtxsigopscountspolicyMaximum signature operations per transaction

Memory and Stack Limits

SettingTypeDefaultEnvironment VariableUsage
MaxStackMemoryUsagePolicyint104857600 (100MB)maxstackmemoryusagepolicyCRITICAL - Maximum stack memory usage (policy)
MaxStackMemoryUsageConsensusint0 (unlimited)maxstackmemoryusageconsensusCRITICAL - Maximum stack memory usage (consensus)

Validation Timeout Settings

SettingTypeDefaultEnvironment VariableUsage
MaxStdTxValidationDurationint0 (not wired up; the getInt call is commented out in settings.go)maxstdtxvalidationdurationMaximum validation time for standard transactions (ms)
MaxNonStdTxValidationDurationint1000maxnonstdtxvalidationdurationBounds the consensus re-run of a transaction that failed a policy script limit (ms); a re-run that does not finish is reported as TxPolicy. 0 means no bound
MaxTxChainValidationBudgetint0 (not wired up; the getInt call is commented out in settings.go)maxtxchainvalidationbudgetTotal time budget for chain validation (ms)
ValidationClockCPUboolfalse (not wired up; the getBool call is commented out in settings.go)validationclockcpuUse CPU time instead of wall-clock for validation timeouts

Data Carrier Settings

SettingTypeDefaultEnvironment VariableUsage
DataCarrierboolfalsedatacarrierEnable relaying of OP_RETURN data carrier transactions
DataCarrierSizeint641000000 (1MB)datacarriersizeMaximum OP_RETURN data size when DataCarrier is enabled

Transaction Chain Limits

SettingTypeDefaultEnvironment VariableUsage
LimitAncestorCountint0 (not wired up; the getInt call is commented out in settings.go)limitancestorcountMaximum unconfirmed ancestor count in mempool
LimitCPFPGroupMembersCountint0 (not wired up; the getInt call is commented out in settings.go)limitcpfpgroupmemberscountMaximum CPFP group members

Mining and Fee Settings

SettingTypeDefaultEnvironment VariableUsage
MinMiningTxFeefloat640.00000500minminingtxfeeMinimum transaction fee for mining
AcceptNonStdOutputsbooltrueacceptnonstdoutputsCRITICAL - Accept non-standard output scripts

Consolidation Transaction Settings

SettingTypeDefaultEnvironment VariableUsage
MinConsolidationFactorint20minconsolidationfactorMinimum consolidation factor
MaxConsolidationInputScriptSizeint150maxconsolidationinputscriptsizeMaximum input script size for consolidation
MinConfConsolidationInputint6minconfconsolidationinputMinimum confirmations for consolidation input
MinConsolidationInputMaturityint6minconsolidationinputmaturityMinimum input maturity for consolidation
AcceptNonStdConsolidationInputboolfalseacceptnonstdconsolidationinputAccept non-standard consolidation inputs

Configuration Dependencies

Block Size Policy

  • BlockMaxSize = 0 means unlimited block size (default behavior for BSV)
  • ExcessiveBlockSize defines the threshold for considering blocks “excessive”
  • Both settings work together to enforce BSV Blockchain’s unbounded block size philosophy

Script Validation

  • MaxScriptSizePolicy controls script size limits during validation

  • MaxScriptNumLengthPolicy limits the length of script numbers

  • MaxStackMemoryUsagePolicy vs MaxStackMemoryUsageConsensus:

    • Policy: Enforced during transaction validation
    • Consensus: Enforced during block validation
    • Setting consensus to 0 (unlimited) aligns with BSV’s restored protocol

Multisig and Signature Operations

  • MaxPubKeysPerMultisigPolicy = 0 means unlimited public keys (BSV default)
  • MaxTxSigopsCountsPolicy = 0 means unlimited signature operations (BSV default)
  • These unlimited defaults reflect BSV Blockchain’s restoration of original Bitcoin capabilities

Non-Standard Transactions

  • AcceptNonStdOutputs = true enables acceptance of non-standard output scripts
  • Required for many BSV applications that use custom script templates
  • Aligns with BSV’s philosophy of not restricting valid script types

Consolidation Transactions

  • Consolidation transactions allow efficient UTXO management
  • MinConsolidationFactor requires minimum input-to-output ratio
  • MinConfConsolidationInput and MinConsolidationInputMaturity prevent immature UTXO consolidation
  • MaxConsolidationInputScriptSize limits input script complexity
  • AcceptNonStdConsolidationInput controls whether non-standard inputs can be consolidated

BSV Blockchain Specifics

Restored Protocol Features

BSV Blockchain restores the original Bitcoin protocol, which is reflected in these policy settings:

  1. Unlimited Block Size: BlockMaxSize = 0 (unlimited)
  2. Unlimited Script Capabilities: Most limits set to 0 (unlimited)
  3. Original Opcodes: All original Bitcoin opcodes restored and functional
  4. No Artificial Restrictions: Non-standard transactions accepted by default

Policy vs Consensus

Teranode distinguishes between policy and consensus rules:

  • Policy Rules: Local node preferences (can be more restrictive)
  • Consensus Rules: Network-wide agreement (must match the BSV Blockchain protocol)

The settings allow operators to configure policy rules while maintaining consensus compatibility.

Validation Rules

SettingValidationImpact
BlockMaxSize0 means unlimitedBlock acceptance criteria
MaxTxSizePolicyMust be positive or 0Transaction size validation
MaxStackMemoryUsagePolicyPolicy enforcementScript execution limits
MaxStackMemoryUsageConsensusConsensus enforcementBlock validation limits
MinMiningTxFeeMinimum fee thresholdMining inclusion criteria

Configuration Examples

Default BSV Configuration

blockmaxsize = 0
excessiveblocksize = 4294967296
maxtxsizepolicy = 10485760
maxscriptsizepolicy = 100000000
maxpubkeyspermultisigpolicy = 0
maxtxsigopscountspolicy = 0
maxstackmemoryusagepolicy = 104857600
maxstackmemoryusageconsensus = 0
acceptnonstdoutputs = true

Conservative Policy Configuration

blockmaxsize = 2147483648
maxtxsizepolicy = 5242880
maxscriptsizepolicy = 250000
maxstackmemoryusagepolicy = 52428800
acceptnonstdoutputs = false

Mining-Focused Configuration

minminingtxfee = 0.00001000
acceptnonstdoutputs = true
minconsolidationfactor = 30