Skip to content
FrontierDot

0xraco 开源: What the GPTibo MIT Repo Includes

Updated

Live timeline · last updated · 2 entries in the update log

If you searched gptibo or “0xraco 开源”, start here. GPTibo is a self-hosted digital-goods shop. On Oct 13, 2026 the X account @0xraco posted “GPTibo 停运及开源公告” and linked the code; that link redirects to the MIT repository CoolkHz/gptibo. Neither page says the GitHub account and the X account are the same person. This post separates what those sources say from the rumours: what the code includes, what was left out, what changed on Oct 14, and what you would still build yourself.

GPTibo is a self-hostable storefront for digital goods (React and TypeScript front end, Go with PostgreSQL or Cloudflare Workers with D1 back end) that was released as sanitized MIT-licensed source on Oct 13, 2026 after the X account @0xraco announced that the original site had stopped operating; the supplier and payment integrations are anonymized stubs, and the separate “GPT top-up” supply platform that was promised was committed once on Oct 14 and then reverted at the owner’s request.

Read on 2026-10-18: the public GitHub repository CoolkHz/gptibo (README, LICENSE, OPEN_SOURCE_REVIEW.md, releases v0.1.0 and v0.1.1, the full commit list, and repository statistics via the GitHub API) and the X posts by @0xraco quoted below. Times are UTC as GitHub and X report them. We did not clone, build or run the code, we did not log in to or buy from any storefront, and we cite no news article for any fact in the timeline. Rechecked on 2026-10-26: the GitHub API showed 857 stars and 505 forks, with no commit after Oct 14. The announcement link still redirects to CoolkHz/gptibo. The post showed 76 reposts and 134 replies.

Timeline

  1. The repository CoolkHz/gptibo is created at 15:57 UTC with a single root commit, “Release sanitized GPTibo storefront and admin under MIT”. At 15:58 UTC the release v0.1.0, “GPTibo MIT 开源版”, is published. Its notes say the first public version contains the storefront, admin panel, partner (agent) workspace and the main back end; that upstream suppliers and aggregated payment channels were anonymized; that production domains, cloud resources, merchant configuration, administrator identities and licensed product mappings were removed; that the internal supply-execution system, operations material and screenshots were removed; that real transactions are off by default; and that it uses an independent Git root with no private history.

    GitHub release v0.1.0 of CoolkHz/gptibo

  2. Two small CI fixes follow within minutes (a quoting fix for the PostgreSQL health check at 16:01 UTC and a TypeScript dependency fix at 16:04 UTC). The release v0.1.1, “验证完整的开源版本”, is published at 16:09 UTC. It says the shop and anonymized adapter source is the same as v0.1.0, and reports 391 Node tests and 496 Go tests and subtests passing without skips, a clean build, go vet and dependency audit, and Gitleaks scans of the source package and Git history with no unwaived hits. These are the maintainer’s own test claims.

    GitHub release v0.1.1 of CoolkHz/gptibo

  3. At 16:28 UTC the X account @0xraco posts “GPTibo 停运及开源公告” (GPTibo shutdown and open-source announcement). It says the site has stopped operating and thanks users; that as traffic grew, serving and maintaining it exceeded the time and energy the author could put in; that after careful thought the decision was to stop; that the site’s front-end and back-end programs are now open source; and that the full “GPT 代充” (GPT top-up) program would be open-sourced the next day “for everyone to learn from and use as reference”. The post is the origin of nearly all later reposts.

    @0xraco on X: GPTibo 停运及开源公告

  4. At 01:13 UTC a commit titled “Add sanitized supply platform and storefront X integration” lands in the repository, touching 135 files with about 17,950 added lines. Its message lists a Go supply API, a channel workspace, wallet and card adapters, a configurable X payment identity, purchasing limits and recovery contracts. At 01:21 UTC a second commit, “Revert supply platform publication”, undoes it “at the owner request” and says the tree again exactly matches the validated v0.1.1. Between the two, at 01:38 and 01:42 UTC, @0xraco quotes the announcement with a reply to critics who objected to publishing it.

    Commit ff89926 in CoolkHz/gptibo (the added supply platform)

  5. At 02:40 UTC the README is rewritten as “redesign README for the public storefront project”. The new text opens with the sentence “原站点已停止运营，项目现以 MIT 许可证开放源码” (the original site has stopped operating; the project is now open source under MIT), lists the three interfaces (storefront, admin, partner workspace), and states that the public version contains storefront-side supplier adapters but not the independent supply platform or supplier execution systems. Checked again on Oct 26, 2026: this README commit is still the latest on main.

    README.md of CoolkHz/gptibo

  6. On X, @0xraco answers replies through the day. At 09:33 UTC the account says the open-sourcing is finished, that it contains nothing core, that payment protocols and card platforms were not included and must be integrated by the user, and calls the release “a half-finished card-shop program”. This is the author’s own description and it matches the repository’s anonymized-stub design.

    @0xraco on X: reply on what was and was not open-sourced

What GPTibo is

GPTibo is the name of a storefront. In the repository’s own words it is a “可自托管的数字商品商城”, a self-hostable digital goods shop, that “integrates product display, payment, order delivery, after-sales handling and partner-shop management in one system”. That is the full description of the product in the primary source. The repository description on GitHub is shorter: “Self-hosted GPTibo storefront, admin and Go backend — sanitized MIT source”.

The code is organised around three surfaces that the README lists as routes: the customer storefront at the root path, an admin back office at /admin and a partner workspace at /partner. The storefront covers product and plan listings, ordering, payment status, order lookup and after-sales requests, with Chinese and English interfaces and a light and dark theme. The admin side covers product pricing, orders and customers, refunds, partner management, settlement and notification settings. The partner workspace lets sub-sellers run their own shop with branding and a custom domain, manage products and see order statistics, including for their own downstream partners.

Technically the front end is React 19 with TypeScript, Vite and Tailwind CSS. There are two interchangeable back ends: a Go service using the Gin framework and PostgreSQL, with the API and background worker run as separate processes, and a Cloudflare Workers back end using D1. Emails use React Email. Tests run with the Node test runner and Go test, and source scanning uses Gitleaks. The repository is MIT-licensed, which the LICENSE file confirms.

Why people are searching for it right now

GitHub shows the repository created on October 13, 2026, and the X announcement followed thirty minutes later. On October 26, 2026 the GitHub API reported 857 stars and 505 forks, one contributor account, and no commits after the October 14 README. The sources do not say why searches for “gptibo” and “0xraco 开源” rose. What they do show is the shutdown post and the public repository. Read again on October 26, that post showed 76 reposts and 134 replies.

The announcement post itself did not name a product category beyond the word “GPT 代充”, a Chinese phrase for topping up or subscribing to GPT services on someone else’s behalf. For the code it published, the repository does not use that phrase; it describes a general digital-goods shop and leaves out the supply side. Treat any description of exactly which goods the original site sold as unverified unless you can find it on one of those two primary sources. We did not find it there.

What the open-source release contains, and what it leaves out

The maintainer’s OPEN_SOURCE_REVIEW.md, dated October 13, 2026 Beijing time, spells out the boundary. Kept: the storefront, admin and partner workspace, the Go API and worker, the Cloudflare Worker, schema migrations and tests with synthetic data. Removed: the standalone supply-execution system, production and test-site deployment material, release and operations records, production scraping tools, admin screenshots, cloud resource bindings and operations documents.

Upstream suppliers and payment channels are replaced with generic names. The README names adapter types such as recharge, account_supplier, delivery_supplier and xgift for supply, and gatewaya and gatewayb for anonymous payment aggregators. Original service domains are replaced with the reserved example.invalid domain, product identifiers are demo values, and merchant identities, administrator identities and keys are left blank. The public payment protocols that remain carry no merchant credentials. The review file also says the anonymized migrations are not compatible with the original production database, so the code can only be installed on a fresh database.

In practice, GPTibo as published is a shop skeleton, and the business itself is not included. You would have to write or connect your own payment gateway, your own supplier integration and your own administrator login, which the README says needs a configured admin identity, TOTP and an email verification service. The default configuration provides no administrator account you can log in with and does not start real payments, purchasing or notifications.

The Oct 14 supply-platform commit and revert

The October 13 announcement promised that the full “GPT top-up” program would follow the next day. The commit history shows what happened to that promise on the repository side. At 01:13 UTC on October 14 a large commit added what its message calls a sanitized supply platform: a Go supply API, a channel workspace, wallet and card adapters and X payment identity configuration, with 17,952 lines added across 135 files. The message states 392 Node tests, 498 storefront Go tests, 211 supply Go tests and 5 source-scanner tests passed, and adds that real external transactions and container startup still needed deployment validation.

Eight minutes later a second commit reverted all of it. Its message says the revert was made “at the owner request”, that the tree again exactly matches the validated v0.1.1 and that “development work remains preserved separately”. The repository therefore never carried the supply platform for more than a few minutes, and anyone who forked in that window may hold a copy. The README written afterwards states that the supply platform is not included. We cannot say from public pages why the owner asked for the revert; the author’s replies on X that day show a heated argument with critics about releasing the project, but the repository itself gives no reason, so we do not claim one.

What the author says on X, and what we can tie together

The announcement was posted by @0xraco, whose display name is “Raco | 玉米须”. It names https://gptibo.com as the site that had stopped, and its open-source link redirects to https://github.com/CoolkHz/gptibo. In follow-up posts on October 14 the account argued with critics who said publishing the code harmed sellers who run similar shops. It said it had not open-sourced any payment protocol, described the release as a half-finished card-shop program, and in one post described the trade of buying cryptocurrency to top up cards in its own words as a grey-market business. We quote none of the insults in those posts, and we do not link the account’s statements to anything beyond what they say.

One thing neither primary source states is that the GitHub account CoolkHz and the X account @0xraco belong to the same person. The timing, the shared subject and the repository’s statement that the original site had stopped operating all point the same way, and the repository README matches the announcement’s wording, but neither page names the other. So this post says “the repository” and “the announcing X account” rather than naming a single operator. If a source for that link matters to you, check the repository owner’s profile yourself.

Practical notes if you want to try the code

The README gives two ways to run it locally. For the Go route you need Node.js 24, Docker Compose and a Python 3 script that initializes local secrets; you then build the API image, start PostgreSQL, run migrations and a grant step, start the API and worker, and run the Vite front end, which proxies /api to the Go service on port 8093. For the Cloudflare route you copy an example .dev.vars file, apply local D1 migrations with Wrangler and run the Worker preview on port 8787. The project’s verification commands are npm test, npm run lint, npm run build and npm run security:scan, plus go test and go vet for the Go service.

The maintainer’s own text suggests two cautions. The integration adapters use unavailable placeholder addresses, so you have to implement and check the real protocols, and the review file says automated tests never touched a real payment or supplier service. The security scan is described as a best-effort check that cannot prove no secret or flaw remains. Before putting real customers or money through any storefront code, run your own review. If you plan to resell subscriptions or accounts of any service, also read that service’s terms; the code does not address that question.

As a comparison point with other open-source commerce stacks, it is a reference implementation of order state, refunds and partner pricing in one codebase. For other dated, source-by-source write-ups of open releases on this site, see the Reflection Beam 501B timeline and the Meta Muse Spark Open timeline. Another open-source release from the same week, which people often confuse in search results, is covered in Puter and The Everything Project. The Front blog index lists every post.

What is not verified

  • Which exact goods or services the original site sold. The repository says “digital goods”; the announcement says “GPT 代充”. We found nothing that lists a catalogue.
  • Whether the CoolkHz GitHub account and the @0xraco X account are the same person. Neither page says so.
  • Why the supply-platform commit was reverted. The commit says only “at the owner request”.
  • Whether the shop skeleton works end to end. The test counts are the maintainer’s claims; we did not build or run the code.
  • Whether https://gptibo.com is currently reachable or who holds it. The announcement names that URL. We did not open it.
  • Any claim about the number of users, orders or revenue of the original site. No primary source gives one.
  • Third-party descriptions on aggregator sites or in AI answers. They repeat the README and add nothing we could check at the source, so we did not use them.

Keep reading on Front

Every post, newest first, is on the Front blog index.

FAQ

What did @0xraco announce about GPTibo?

On Oct 13, 2026 the account posted “GPTibo 停运及开源公告”. It said https://gptibo.com had stopped operating, that the front end and back end were now open source, and that the full GPT top-up program would follow the next day. The open-source link in that post redirects to https://github.com/CoolkHz/gptibo. The current README says the supply platform is not included. The post does not say the X account and the GitHub account CoolkHz are the same person.

What is GPTibo?

A self-hostable digital-goods storefront with a customer shop, an admin back office and a partner workspace. Its original site stopped operating, and the code was published under the MIT license on October 13, 2026.

Is GPTibo open source?

Yes. The repository CoolkHz/gptibo is MIT-licensed, and the open-source link in the @0xraco announcement redirects there. Supplier and payment integrations are anonymized stubs, and a separate supply platform is not included.

Can I run GPTibo as a shop right away?

No. By the maintainer’s own description, real transactions are off by default, there is no usable admin account, and you must build or connect your own payment and supplier adapters first.

Was the GPT top-up program open-sourced too?

It was announced for Oct 14. A commit adding a supply platform appeared at 01:13 UTC that day and was reverted eight minutes later at the owner’s request. The current README says it is not included.

What tech does GPTibo use?

React 19, TypeScript, Vite and Tailwind CSS on the front end; Go with Gin and PostgreSQL, or Cloudflare Workers with D1, on the back end.

Update log

  • — Rechecked the GitHub API and the @0xraco announcement on Oct 26, 2026: 857 stars, 505 forks, no commit after Oct 14, and the post showed 76 reposts and 134 replies.
  • — First published. Checked the CoolkHz/gptibo repository, its two releases, commit history, README and review file, and the announcing X posts through Oct 18, 2026 (UTC+8).

Sources