after mining some coins, i see there is 48 ql per block at time of this post show 1438 blocks X 48=69,024 and the total outstanding is 5,269,024 so my guess is there is a 5.2M premine? i dont see any info about this on website. can you shed some lite on this just for clarity?
Good catch, and you're right to ask — this should be clearer on the site itself, thank you for flagging it.
Yes, there's a genesis allocation of 5,200,000 QL, split across two project-controlled treasury wallets (visible on the public explorer as Master Vault A and Operational Vault B — you can see their balances and addresses directly there, nothing hidden). This sits alongside a separate 20,300,000 QL mining pool that's earned purely through proof-of-work, for a 25,500,000 hard cap total.
The genesis allocation covers ongoing development costs, infrastructure, and things like security review and exchange listing costs down the line — standard treasury/reserve practice for early-stage projects, but I agree it needs to actually say that clearly on the explorer rather than just being visible as numbers. Getting that added.
A real, working Layer 1 node — proof-of-work mining, automatic difficulty retargeting
how is this calculated? if a big cpu farm comes onboard, mines gets a bag, and leaves ,at what point will the diff drop back down when they leave?
Fair question, and genuinely tested this exact scenario over launch weekend. Difficulty retargets every 10 blocks, comparing actual time taken against the 5-minute-per-block target — it can move in either direction, not just up.
Concretely, what actually happened here: difficulty climbed from 22 to 31 bits over a weekend as more hashpower joined, then walked back down over the following retarget cycles once hashpower dropped. Not instant — it takes a few 10-block windows to fully correct — but it does genuinely settle back down, not stay artificially high forever.
So to your scenario directly: a big farm joining would push difficulty up while they're active, and after they leave, it corrects back down over the next several retarget windows as block times naturally slow back toward target.
Appreciate you asking directly rather than assuming the worst — exactly the kind of scrutiny a project should welcome.
