@kurtwuckertjr You say “big blockers had a chance, were strong at a certain point” and you fail to see what led to big blockers downfall. If it wasn’t for Craig, no bch split, no bsv split, BTC could have had big blocks by now. Community fragmentation was entirely due to Craig’s false claims.
@CaptainBSV I’m sure Craig would be able to fund 2 billion people aking for $0.60 if he only sold 1/10 of his assets to fulfill his promise of dedicating he nation-sized wealth to the poorest bottom.
@murphsicles tbf, my agent wasnt aware of https://t.co/rfWA8Uyvyv, only https://t.co/K1tQOz8WtU; in any case, you should consolidate and organize your docs and avoid marketing oriented language in favor of peer reviewable terminology.
@murphsicles Fair. the bootstrap/main split explains the Rust references. The remaining question is reproducibility. If release zetac can build Zeta packages from zorbs, that proves package compilation; if it can rebuild/verify the compiler from main, that proves self-hosting. I’ll test that
@murphsicles Ok, I see the branch split. The release/binary workflows build zetac from bootstrap with Cargo, then commit binaries to main. That explains the Rust references. What I still haven’t found is the CI run where main/bin/zetac compiles/verifies the Zeta sources/packages on main.
@murphsicles Not disputing that there are many Actions runs/releases. I’m asking which run proves the claim. The CI file I inspected checks out bootstrap and runs Cargo/Rust; Please link the specific successful workflow run where release zetac compiles main/src/main.z into zetac without Rust
@murphsicles Fair enough, then the evidence should be straightforward: a documented reproducible build showing a release zetac compiling the main branch compiler sources into an equivalent zetac. You have a bootstrap/self-hosting verification doc or CI workflow that demonstrates that process