engineering/make_post_sell
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Remove database implementation details from crypto docs

Browse source 
- Remove incorrect SQL index examples from DOGECOIN.md and MONERO.rst
- Simplify Dogecoin node security section to reference make command
- Stop leaking database schema details in user-facing documentation
This commit is contained in:
Russell Ballestrini 2025-09-30 22:40:10 -04:00
parent 1e988b8553
commit 9d06903633
2 changed files with 1 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/DOGECOIN.md
View file

@ -226,23 +226,8 @@ dogecoin-cli getwalletinfo
### Security Configuration
**Node Security:**
```bash
# Production dogecoin.conf with security
server=1
daemon=1
# Strong RPC credentials
rpcuser=very_secure_username
rpcpassword=extremely_secure_password_123!@#
rpcallowip=127.0.0.1
rpcport=22555
# Pruned mode for minimal storage
prune=2200
# Specific wallet for isolation
wallet=mps_wallet
```
Use `make dogecoin-config` to generate a secure configuration file. The generated `dogecoin.conf` includes secure RPC credentials that must be changed for production use.
**Network Security:**
```bash
@ -390,13 +375,6 @@ addnode=seed.multidoge.org
addnode=seed.dogecoin.com
```
**Database Optimization:**
```sql
-- Index optimization for DOGE payment queries
CREATE INDEX idx_crypto_payment_doge_status ON mps_crypto_payment(coin_type, status) WHERE coin_type = 'DOGE';
CREATE INDEX idx_crypto_payment_doge_address ON mps_crypto_payment(address) WHERE coin_type = 'DOGE';
CREATE INDEX idx_crypto_payment_doge_created ON mps_crypto_payment(created_at) WHERE coin_type = 'DOGE';
```
### Alternative: Full Node Mode

7
docs/MONERO.rst
View file

@ -415,13 +415,6 @@ Performance Tuning
For high-volume shops, monero-wallet-rpc memory usage is minimal with remote nodes. The wallet only maintains account and subaddress data, not full transaction history.
**Database Optimization:**
::
# Index optimization for crypto payment queries
CREATE INDEX idx_crypto_payment_account_subaddr ON mps_crypto_payment(account_index, subaddress_index);
CREATE INDEX idx_crypto_payment_status_coin ON mps_crypto_payment(status, coin_type);
CREATE INDEX idx_crypto_payment_shop_created ON mps_crypto_payment(shop_id, created_at);
Scaling Considerations
----------------------