[SERVICE] Gliese.io – Explorer & On-Chain Tools for New Altcoin Projects

[bitcointry]

Hello Bitcointalk community,

We’re building Gliese, an on-chain analytics and explorer platform designed to help blockchain projects provide a professional explorer experience without maintaining heavy infrastructure.

Many new projects struggle with running full nodes, address indexers, explorers, and additional tooling. Gliese aims to reduce that burden by offering a ready-to-use solution.

What Gliese offers:
• Block, transaction and address explorer 
• UTXO analysis & spendability insights 
• TX simulation tools 
• Embeddable UTXO Health Widget 
• API access for integrations 

Currently live on:
• Bitcoin (BTC) 
• Litecoin (LTC) 
• Additional chains integrated as pilot cases 

For Altcoin / New Chain Teams

If you are:
• Launching a new blockchain 
• Maintaining an existing chain 
• Looking to offer an explorer without building one from scratch 

You can apply to have your coin listed on Gliese here:
https://gliese.io/list-your-coin

Instead of developing and maintaining your own explorer stack, your project can leverage Gliese’s existing infrastructure and tools.

Early-stage projects are welcome. Each integration is reviewed individually.

Feedback, questions, or integration requests are always welcome.

— Gliese Team

[BattleDog]

If you're offering an embeddable widget, please treat it like a supply chain component. Keep it dumb, cache-friendly, and not a third-party script that can become a surprise attack surface for every project that pastes it into their site. I've seen "simple embed" turn into the weakest link more than once.

If you post a short API doc + rate limits + a status page, you'll probably get a lot more serious eyeballs than the usual service thread drive-by.

[bitcointry]

Thanks for the clarification points — makes sense.

Our widget is intentionally very simple:
- it only fetches pre-computed data from our API
- no business logic, mutation, or decision-making happens on the JS side
- no tracking, analytics, or dynamic behavior

The API already enforces rate limits (60 requests per minute), and responses are cache-friendly.
The widget is essentially a thin read-only view layer over the API.

Documentation for the embed is available here:
https://gliese.io/docs#widget-embed

We agree with the general concern around third-party embeds and are keeping this one as minimal and predictable as possible.
Appreciate the feedback — it’s exactly the kind of discussion we want around the project.

If you're offering an embeddable widget, please treat it like a supply chain component. Keep it dumb, cache-friendly, and not a third-party script that can become a surprise attack surface for every project that pastes it into their site. I've seen "simple embed" turn into the weakest link more than once.

If you post a short API doc + rate limits + a status page, you'll probably get a lot more serious eyeballs than the usual service thread drive-by.