The mnemonic function within the mock-jutsu ecosystem serves as a vital tool for developers building decentralised applications and financial software. By generating realistic BIP-39 recovery phrases, this utility allows teams to populate their environments with high-quality mock data that mirrors real-world blockchain interactions. Whether you are building a non-custodial wallet or a cryptocurrency exchange interface, having access to authentic-looking test data is essential for verifying how your application handles sensitive cryptographic inputs and user onboarding flows.
Adhering strictly to the BIP-39 standard, the mnemonic generator produces a sequence of words designed to represent a binary seed. This standardisation ensures that the mock data produced by mock-jutsu is not just random text, but follows the specific linguistic patterns required for deterministic wallet generation. Developers can utilise these phrases to test recovery logic and checksum validation, ensuring that backup and restore workflows function correctly before any real assets are at risk. This level of realism is crucial for debugging complex cryptographic modules where data integrity is paramount.
Beyond simple functional checks, the mnemonic function is indispensable for stress-testing UI and UX components. Because recovery phrases can vary in length and word complexity, using mock-jutsu to generate diverse test data helps identify layout issues or overflow errors in mobile and web views. It provides a reliable way to simulate the user experience where a mnemonic must be displayed, confirmed, or manually entered, allowing for a seamless transition from development to production environments without relying on hardcoded strings.
Integration is streamlined across various environments, making mock-jutsu a versatile choice for modern DevOps pipelines. Whether invoked via the Python API for unit tests, the command-line interface for quick prototyping, or through JMeter for performance benchmarking, the mnemonic function remains consistent and reliable. This cross-platform flexibility allows engineers to maintain a unified approach to data generation, ensuring that every stage of the software development lifecycle is backed by robust, standardised, and secure cryptographic strings that behave exactly like their production counterparts.
mockjutsu generate mnemonic --words 12mockjutsu bulk mnemonic --count 10mockjutsu export mnemonic --count 10 --format jsonmockjutsu export mnemonic --count 10 --format csvmockjutsu export mnemonic --count 10 --format sql# --mask: regulation-compliant output (PCI DSS / GDPR / KVKK)mockjutsu generate mnemonic --maskmockjutsu bulk mnemonic --count 5 --maskfrom mockjutsu import jutsujutsu.generate('mnemonic')jutsu.bulk('mnemonic', count=10)jutsu.template(['mnemonic'], count=5)# with --words parameterjutsu.generate('mnemonic', words=12)# mask=True: regulation-compliant outputjutsu.generate('mnemonic', mask=True)jutsu.bulk('mnemonic', count=5, mask=True)${__mockjutsu_crypto(mnemonic)}${__mockjutsu_crypto(mnemonic:12)}# JMeter Function: __mockjutsu_crypto# Parameter 1: mnemonic OR mnemonic:# Qualifier values: 12|15|18|21|24# Parameter 2: (not required for this function)# Add 'mask' keyword to get a regulation-compliant masked value${__mockjutsu_crypto(mnemonic,mask)}GET /generate/mnemonic# → {"type":"mnemonic","result":"...","status":"ok"}GET /bulk/mnemonic?count=10POST /template {"types":["mnemonic"],"count":1}# mask=true: regulation-compliant outputGET /generate/mnemonic?mask=trueGET /bulk/mnemonic?count=5&mask=true| Parameter | Values | Description |
|---|---|---|
| --words | 12|15|18|21|24 | Word count for mnemonic |
| --mask | true | false | Return a regulation-compliant masked value (PCI DSS, GDPR, KVKK…) |