injective-wallet-ops
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
Mass create, derive, and manage Injective wallets. Generate wallets from mnemonics (BIP-44 HD derivation), create random wallets, convert between ETH/INJ addresses, and batch fund wallets with INJ or USDT. Supports bulk wallet generation and batch funding.
In this repository20 other files it gives its agents.
- injective-ai-cost-optimizationSkill
- injective-cliSkill
- injective-core-detect-changesSkill
- injective-docs-styleSkill
- injective-evm-developerSkill
- injective-faucetSkill
- injective-frontend-walletSkill
- injective-fundingSkill
- injective-mcp-serversSkill
- injective-rfq-integrationsSkill
- injective-trading-accountSkill
- injective-trading-autosignSkill
- injective-trading-bridgeSkill
- injective-trading-chain-analysisSkill
- injective-trading-frontend-uxSkill
- injective-trading-market-dataSkill
- injective-trading-stakingSkill
- injective-trading-tokensSkill
- injective-usdc-integrationSkill
- linear-cliSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 125
After funding bank accounts, deposit to trading subaccounts:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Injective Wallet Operations Skill
Overview
Generate, derive, fund, and manage Injective wallets in bulk. Based on proven patterns from an Injective RFQ test framework.
Reference Code
Key implementation files (from an Injective RFQ test framework):
- Wallet library:
src/rfq_test/crypto/wallet.py - Mass generation:
scripts/generate_wallets.py,scripts/setup_wallets.py - Key derivation CLI:
derive_key.py - Mass funding:
scripts/fund_subaccounts.py,scripts/fund_demo_subaccounts.py - Balance checks:
scripts/check_balances.py,scripts/check_all_balances.py
Wallet Generation
From Mnemonic (Deterministic, BIP-44)
from eth_account import Account
Account.enable_unaudited_hdwallet_features()
def generate_wallets_from_seed(seed_phrase: str, count: int, start_index: int = 0):
wallets = []
for i in range(start_index, start_index + count):
path = f"m/44'/60'/0'/0/{i}"
acct = Account.from_mnemonic(seed_phrase, account_path=path)
eth_addr = acct.address
inj_addr = eth_to_inj_address(eth_addr)
wallets.append({
"index": i,
"private_key": acct.key.hex(),
"eth_address": eth_addr,
"inj_address": inj_addr,
})
return walletsRandom Wallets
import secrets
key = secrets.token_hex(32)
# Then use PrivateKey.from_hex(key) from pyinjectiveAddress Conversion (ETH <-> INJ)
Injective is EVM-compatible: every secp256k1 key has two address encodings that map 1:1. The 0x form (40 hex chars) is what MetaMask + bridging tools show; the inj1 form (bech32, 38 chars after the prefix) is what Cosmos RPCs, MsgSend, contract state, and the indexer use. Any code that accepts a user-supplied address should accept both forms and canonicalize to inj1 before chain ops — rate limits, dedup keys, and authz lookups must be keyed on the inj form, otherwise a caller can dodge them by flipping encodings.
Validation regexes (accept both, reject everything else):
inj1: ^inj1[02-9ac-hj-np-z]{38}$ (bech32 charset; no b/i/o/1)
0x: ^0x[0-9a-fA-F]{40}$ (mixed case OK; normalize to lowercase)Python (standalone, no SDK):
import bech32
def eth_to_inj_address(eth_address: str) -> str:
eth_bytes = bytes.fromhex(eth_address.removeprefix("0x"))
five_bit = bech32.convertbits(eth_bytes, 8, 5)
return bech32.bech32_encode("inj", five_bit)
def inj_to_eth_address(inj_address: str) -> str:
_, five_bit = bech32.bech32_decode(inj_address)
eight_bit = bech32.convertbits(five_bit, 5, 8, False)
return "0x" + bytes(eight_bit).hex()Node / TypeScript (via @injectivelabs/sdk-ts, preferred when the project already depends on it):
import { getInjectiveAddress, getEthereumAddress } from '@injectivelabs/sdk-ts';
// 0x → inj1
const inj = getInjectiveAddress('0xYourEthAddress…40hex');
// inj1 → 0x (lowercase)
const eth = getEthereumAddress('inj1yourbech32address…');Accept-either pattern (server accepting an external address):
const INJ_BECH32 = /^inj1[02-9ac-hj-np-z]{38}$/;
const ETH_HEX = /^0x[0-9a-fA-F]{40}$/;
function normalize(raw: string) {
const s = raw.trim();
if (INJ_BECH32.test(s)) return { inj: s, eth: getEthereumAddress(s).toLowerCase() };
if (ETH_HEX.test(s)) return { inj: getInjectiveAddress(s), eth: s.toLowerCase() };
throw new Error('malformed address — expected inj1… (43 chars) or 0x… (42 chars)');
}The PrivateKey.toBech32() / .toAddress() methods on sdk-ts's PrivateKey return these two forms from a key directly — useful when you're generating + need both at once.
Mass Funding
Send INJ to Many Wallets (batched MsgSend)
The setup_wallets.py pattern batches up to 200 MsgSend messages in a single transaction:
from pyinjective.composer import Composer
from pyinjective.transaction import Transaction
msgs = []
for wallet in wallets:
msg = composer.msg_send(
sender=funder_address,
receiver=wallet["inj_address"],
amount=amount,
denom="inj"
)
msgs.append(msg)
# Submit all msgs in one txDeposit to Exchange Subaccount
After funding bank accounts, deposit to trading subaccounts:
from pyinjective.core.broadcaster import MsgBroadcasterWithPk
msg = composer.msg_subaccount_deposit(
sender=address,
subaccount_id=get_subaccount_id(address, nonce=0),
amount=Decimal(str(amount)),
denom=denom
)Two-Step USDT Funding (testnet)
- Parent wallet sends USDT via bank
MsgSendto child - Child deposits USDT from bank to exchange subaccount
Balance Checks
# Bank balance
balance = await client.fetch_bank_balance(address, denom)
# Subaccount deposit
deposits = await client.fetch_subaccount_deposits(subaccount_id)Environment Config
- Env var prefix pattern:
{ENV}_LOAD_TEST_MM_SEED_PHRASE,{ENV}_LOAD_TEST_RETAIL_SEED_PHRASE - Or comma-separated key lists:
TESTNET_MM_KEYS=hex1,hex2,... - YAML configs at
configs/{env}.yaml
Dependencies
injective-py>=1.12.0eth-account>=0.11.0bech32>=1.2.0- Python >= 3.11
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

