[ANN] Gliese.io – UTXO Analysis, TX Simulation & Explorer for Bitcoin & Litecoin

[bitcointry]

Gliese.io – UTXO Analysis, TX Simulation & Explorer for Bitcoin & Litecoin

Hello Bitcointalk community,

I’d like to introduce Gliese, a non-custodial on-chain analysis platform focused on UTXO-based blockchains, currently supporting Bitcoin (BTC) and Litecoin (LTC).

In UTXO-based systems, balances alone are misleading. Structure matters.

--------------------------------------------------

What is Gliese?

Gliese is a technical blockchain analysis platform built directly on full nodes to provide deep insight into:

• UTXO structure 
• Transaction behavior 
• Spendability & complexity 
• On-chain feasibility before broadcasting 

Gliese is not a wallet, not an exchange, and does not custody funds.

--------------------------------------------------

Core Features

• UTXO Analysis (BTC & LTC) 
- Address-level UTXO breakdown 
- UTXO age, fragmentation & structure 
- Technical spendability scoring 

• TX Simulation 
- Raw transaction decoding 
- Input / output behavior analysis 
- Fee, size & complexity impact 
- Detect issues before broadcasting 

• Explorer (UTXO-Centric) 
- Address, transaction & block explorer 
- UTXO-focused views (not balance-only) 
- Built for analysis, not just lookup 

• Full-Node Infrastructure 
- Bitcoin Core & Litecoin Core 
- No third-party APIs 
- Deterministic on-chain data 

• Documentation 
https://gliese.io/docs

--------------------------------------------------

Who is Gliese for?

• Bitcoin & Litecoin power users 
• Developers working with UTXO chains 
• On-chain analysts & researchers 
• Platforms needing deeper transaction visibility 

--------------------------------------------------

Why UTXO-level analysis matters

In UTXO-based blockchains:
• A balance is only a summary 
• Real behavior depends on UTXO count, age and script structure 

Without UTXO awareness:
• Fee surprises 
• Inefficient transactions 
• Hard-to-spend outputs 

Gliese focuses on clarity before action.

--------------------------------------------------

Trust & Transparency

• No wallet connection 
• No private keys 
• No signing or broadcasting 
• Analysis-only platform 

--------------------------------------------------

Links

Website: https://gliese.io 
Documentation: https://gliese.io/docs 

--------------------------------------------------

Roadmap (Short-term)

• Advanced UTXO consolidation planning 
• Deeper TX simulation scenarios 
• Additional UTXO-based chains 
• Public API for developers 

Feedback and technical discussion are welcome.

[ABCbits]

I tried it for a bit, but the color choice feels weird to me.
1. Poor Value Distribution have green color.
2. Good Spendability have red color.

1. For faster confirmation, what matters most is TX fee rate rather than total UTXO.
2. While i agree it's better to consolidate UTXO during low-fee period, such period is most of the time within last 1 year. https://mempool.space/graphs/mempool#1y shows most TX have fee rate between 0-3 sat/vB.

[bitcointry]

Thanks for taking the time to test and report these issues! You were right on all points.

Fixed the color logic — status indicators now correctly reflect the severity of each factor.

Also updated the documentation:

• Corrected the "Faster Transactions" description

(confirmation speed depends on fee rate, not UTXO count)

• Fixed the score range table and factor weights to match the actual calculation
• Updated the real-world example with accurate vByte sizes for both SegWit and Legacy
• Revised the consolidation advice to be more accurate

Appreciate the feedback, it makes the project better!

https://i.ibb.co/Pz1378xW/a.png

I tried it for a bit, but the color choice feels weird to me.
1. Poor Value Distribution have green color.
2. Good Spendability have red color.

https://i.ibb.co/Ndb0fyv5/b.png

1. For faster confirmation, what matters most is TX fee rate rather than total UTXO.
2. While i agree it's better to consolidate UTXO during low-fee period, such period is most of the time within last 1 year. https://mempool.space/graphs/mempool#1y shows most TX have fee rate between 0-3 sat/vB.

[cygan]

i took a quick look at your new service and tested the explorer a little bit... everything has been running smoothly so far, and i haven't found any serious issues.
would advise you to mention your new website in this thread as well, where you might find more feedback from other/more users...
you can also refer to this official thread there

i'll also tag GazetaBitcoin, who is the creator of the explorer thread, and let him know about this thread

[bitcointry]

Thanks for the suggestion!

We’ve shared Gliese in the explorer thread as you recommended and would be happy to get more feedback from users there.

Here’s the post:
https://bitcointalk.org/index.php?topic=5197909.msg66376142#msg66376142

Really appreciate you pointing us in the right direction and for tagging the thread creator as well.

i took a quick look at your new service and tested the explorer a little bit... everything has been running smoothly so far, and i haven't found any serious issues.
would advise you to mention your new website in this thread as well, where you might find more feedback from other/more users...
you can also refer to this official thread there

i'll also tag GazetaBitcon, who is the creator of the explorer thread, and let him know about this thread

[joker_josue]

This appears to be a different approach to address analysis.
I'll test it, and give feedback as soon as possible.


However, I ask, how do you handle visitor privacy? Do you keep logs of searches?

[bitcointry]

Good question, and thanks for taking a look.

We don’t track users or build profiles based on visitor activity.

Searches are temporarily cached on the backend purely for performance reasons, so repeated lookups (same address / tx) can be served faster. This data is not tied to user identities, IP addresses, or any form of personal information.

We don’t share search data with third parties, and it’s not used for analytics, advertising, or behavioral tracking — it’s strictly a technical cache to reduce load and improve response times.

The platform is designed with a privacy-first mindset, similar to how most public explorers handle indexing and caching.

This appears to be a different approach to address analysis.
I'll test it, and give feedback as soon as possible.


However, I ask, how do you handle visitor privacy? Do you keep logs of searches?