License
BUSL-1.1: free to read, audit and build on — not free to fork into a competing product.
GlueHook is published under the Business Source License 1.1 (BUSL-1.1). The short version: the deployed hook is free infrastructure for everyone to use and build on — but copying the source to ship your own competing deployment is a different act, and that one needs a licence.
The one distinction that matters
Everything in this documentation — launching pools, integrating donations and quotes, building launchpads, lockers, vaults and UIs on top of the canonical deployments — is using the hook. Using a deployed contract is not governed by the source licence at all: no permission, no fee, no attribution required. It is exactly what the hook was designed for.
What the licence restricts is forking: taking the source (or a modified copy of it), deploying it yourself, and turning it into a product. That is production use of the Licensed Work, and under BUSL-1.1 it requires a grant from the licensor until the Change Date. If your plan is “this hook, but ours” — talk to us first.
launchPool, donate, quotePump, harvest or any other function on the canonical address, from any product, commercial or not, is unconditionally fine. The address is the same on every network precisely so that building on it is easy.The parameters
| parameter | value |
|---|---|
| License | Business Source License 1.1 |
| Licensor | Glue Labs Inc. (Delaware) |
| Licensed Work | GlueHook — (c) 2026 gluefinance.eth |
| Additional Use Grants | published at gluehook-license-grants.gluefinance.eth |
| Change Date | the earlier of 2030-08-05 or a date set at gluehook-license-date.gluefinance.eth |
| Change License | GNU General Public License v2.0 or later |
On the Change Date the licence converts automatically: the whole codebase becomes GPL v2.0-or-later and every restriction above ends. Until then, additional production grants can be published on-chain at the ENS record — so a grant, once given, is as public and verifiable as the code itself.
What this means in practice
| you want to… | licence answer |
|---|---|
| launch pools, donate, integrate quotes, run a UI on the deployed hook | free — always, for anyone, commercially too |
| build a launchpad / locker / vault that composes on the roles | free — this is the intended use |
| read, audit, run the tests, experiment on a devnet | free — non-production use is granted to all |
| fork the source and deploy your own competing hook | needs a grant until the Change Date |
| wait until the Change Date and use it under GPL | fine — that conversion is automatic and irrevocable |
The full text lives in LICENCE.txt at the repository root and in the verified source on every explorer. When in doubt, the test is simple: if your product calls the canonical address, you are a user; if your product is a copy of this code, you need a grant.
FAQ
Can I build a product on the deployed hook?+
Yes — launchpads, lockers, vaults, UIs and integrations that CALL the canonical deployments are the intended use and don't touch the source licence at all.
Can I fork the code into my own hook?+
Not for production: BUSL-1.1 grants copy/modify/derivative rights for NON-production use only. Shipping a competing deployment needs a grant from the licensor until the Change Date.
When does the code become fully open?+
On the Change Date — the earlier of 2030-08-05 or a date published on-chain at the licence ENS records — the licence converts to GPL v2.0 or later, automatically.
Can I read, audit and test the source?+
Freely — reading, auditing, running the test-suite and any other non-production use is explicitly granted to everyone, today.
Who do I ask for a production grant?+
Glue Labs Inc. — additional use grants are published at the ENS record listed in LICENCE.txt, and the team is reachable through the repository or @glue_fi.