Charts
DataOn-chain
VIP
Market Cap
API
Rankings
CoinOSNew
CoinClaw🦞
Language
  • 简体中文
  • 繁体中文
  • English
Leader in global market data applications, committed to providing valuable information more efficiently.

Features

  • Real-time Data
  • Special Features
  • AI Grid

Services

  • News
  • Open Data(API)
  • Institutional Services

Downloads

  • Desktop
  • Android
  • iOS

Contact Us

  • Chat Room
  • Business Email
  • Official Email
  • Official Verification

Join Community

  • Telegram
  • Twitter
  • Discord

© Copyright 2013-2026. All rights reserved.

简体繁體English
|Legacy
BTCBTC
💲74311.24
+
3.54%
ETHETH
💲2343.58
+
10.95%
SOLSOL
💲94.93
+
7.25%
XRPXRP
💲1.54
+
8.45%
DOGEDOGE
💲0.1021
+
7.08%
USDCUSDC
💲0.9999
+
0.01%

gm365
gm365|6月 01, 2025 06:21
💻 If I were to help CoinTool design a webpage After a few days, I need to use CoinTool Mint XEN again. As expected, using the CT official website also failed again (even after changing the only paid RPC and loading 30% of the wallet each time). Grit your teeth and write your own program to scan wallet data. The general idea is as follows: 1. Load all wallet address information for CoinTool XEN (CT page download, XLSX format, converted to CSV), approximately several thousand 2. Read all wallet addresses and check XEN expiration date 3. Read the IDs of all expired wallets (required for the next CT contract claim) 4. Program generates data parameters required for CT XEN contract claim 5. Etherscan fills in four parameters (two default values and two parameters obtained earlier) 6. Successful claim+resubmission The key lies in the second step. If you have thousands of addresses that need to query expiration dates, it may consume RPC resources (I don't know if there is a problem with this step on the CT official website) But there is actually an engineering optimization approach: 🧠 Sampling inquiry Because most addresses belong to different batches, with an average of 128 addresses per batch. So, all you need to do is classify these 128 addresses, and then sample several addresses from the same batch for query and verification. In this way, thousands of addresses are divided into several batches, and only a few dozen RPC queries are needed in the end. Of course, there is also another possibility: There was a problem scanning all XEN addresses created in the current wallet, such as my page showing that approximately 25000 addresses were created. But I think even so, there should still be ideas and methods that can be optimized, such as MyCoinTool, which seems to never have the problem of unable to load addresses. The problem is that there are very few estimates of Mint XEN who are still persevering until now, and those who encounter problems like mine are probably even more rare. Anyway, okay. Let's take a little record of the time spent tinkering yesterday.
+3
Mentioned
|
APP
Windows
Mac
Share To

X

Telegram

Facebook

Reddit

CopyLink

|
APP
Windows
Mac
Share To

X

Telegram

Facebook

Reddit

CopyLink

Timeline

6月 25, 11:41【Building Hubra, loading fast】
6月 15, 22:15【Draw a new boundary on the chain】
6月 02, 18:28【Ethereum Summer Loading】
5月 20, 00:33【The Hope of Building Blockchain with Artificial Intelligence】
5月 14, 07:49【Tether artificial intelligence loading】
5月 06, 11:11【An encrypted load into boot mode】
5月 05, 10:46【The new @ iota mainnet has been launched】

HotFlash

|
APP
Windows
Mac
Share To

X

Telegram

Facebook

Reddit

CopyLink

APP
Windows
Mac

X

Telegram

Facebook

Reddit

CopyLink

Hot Reads