Add logic to skip proof-of-work check for testnet when there's been 20 minutes of inactivity, allowing min difficulty blocks to be mined. This helps maintain chain progress during periods of low testnet activity.
Move the special 20-minute rule check before LWMA calculation for clarity and maintain the same behavior. Remove redundant else block and consolidate the logic for returning last non-special-min-difficulty block.
Update testnet minimum chain work and default assume valid values to current state.
Restore security check in getblocktemplate RPC to prevent usage during initial block download.
- Apply LWMA difficulty calculation for testnet from block 0 to match mainnet behavior
- Clarify testnet min-difficulty rule by using explicit 20 minute threshold instead of nPowTargetSpacing*2
- Change BIP34Height from 0 to 8192 to match mainnet activation
- Adjust nPowTargetTimespan from 1 day to 14 days for better difficulty stability
- Add nPowTargetSpacingV2 parameter for future compatibility
- Swap rule change activation threshold and miner confirmation window values
- Clarify fPowAllowMinDifficultyBlocks comment
Replace direct CLIENT_BUILD usage with FormatVersion to consistently display semantic versioning. This omits trailing ".0" and git suffix when build number is zero, making version strings cleaner and more predictable.
The previous consensus parameters prevented the node from completing
initial sync without manually importing blocks. Updated chainparams so
a fresh node can fully synchronize on its own.
- Condensed lengthy documentation into more concise sections
- Removed redundant troubleshooting and implementation details
- Organized content by architecture with clear command/output sections
- Maintained all essential information while improving readability
- Add Dockerfile.linux-armv7l for ARMv7l cross-compilation environment
- Create build-linux-armv7l.sh script to automate the build process
- Update .dockerignore to exclude more build artifacts and temporary files
- Extend README.md with ARMv7l build instructions and target details
Update all references to 'testnet3' to 'testnet' for consistency. This includes:
- Changing magic bytes in network messages
- Updating directory paths and configuration files
- Modifying documentation and test framework references
- Adjusting chain parameters and validation logic
Add Dockerfile and build script for Linux aarch64 cross-compilation targeting ARM64 devices like Raspberry Pi. Includes documentation updates explaining the build process and troubleshooting tips.
The changes enable building Palladium binaries for ARM64 architecture using cross-compilation in a Docker container, with output binaries placed in the build directory.
The detailed build instructions were moved to separate platform-specific documents in the `/doc` folder to make the README more maintainable and easier to navigate. This change provides clearer guidance for users building on different operating systems.
Add Dockerfile.windows and build-windows.sh for cross-compiling Windows executables
in a containerized environment. Includes documentation updates in README.md with
build instructions and troubleshooting tips for Windows builds.
- Replace old releases page URL with new organization URL
- Add Docker build instructions as recommended method
- Expand manual build instructions with detailed steps and verification
- Include runtime dependencies for GUI
- Replace generic Dockerfile with platform-specific Dockerfile.linux-x86_64
- Simplify .dockerignore to essential patterns
- Update build script with improved container build process and output handling
- Enhance README with detailed build process documentation
Add Dockerfile, build script, README and .dockerignore to create a reproducible build environment for Palladium Core binaries. The system builds x86_64 Linux binaries with all required dependencies and outputs them to the out/ directory.
The whitepaper has been converted from PDF to LaTeX format to enable easier maintenance and updates. The content has been revised and expanded with additional technical details about Palladium's protocol specifications.
- Restructured document with clear sections and improved formatting
- Added detailed configuration instructions with parameter explanations
- Included build instructions and contribution guidelines
- Updated security information and support resources
- Enhanced overall readability and completeness of documentation
