BICLE v0.1 - The Decentralized Feed Protocol

[Bicle]

BICLE v0.1 - The Decentralized Feed Protocol
"Like Bitcoin decentralized money, BICLE decentralizes information"

GitHub

Abstract

BICLE is a decentralized information protocol that creates an immutable, verifiable ledger of news and information. Inspired by Bitcoin's architecture, BICLE uses Proof-of-Information (PoI) - cryptographic hashing to ensure news integrity and create tamper-proof records.

The problem: News can be edited, deleted, manipulated. No cryptographic proof of "what was said when."

The solution: Blockchain-based immutable record. Every news item gets a unique hash. Blocks are chained. History is verifiable.


Technical Overview

Core Concept:

Code:

News Item → iHash (SHA-256)
Multiple News → Block
Block → blockHash (SHA-256)
Blocks → Blockchain (chained via previous hash)

Structure:

Code:

iHash = SHA256(title + link + source + timestamp)
blockHash = SHA256(sorted(iHash₁ + iHash₂ + ... + iHashₙ))

Properties:
- Immutable: Changing one news item breaks the entire chain
- Verifiable: Anyone can verify the blockchain independently
- Timestamped: Cryptographic proof of "when" something was published
- Tamper-evident: Any alteration is immediately detectable


Genesis Block

Just like Bitcoin's genesis block referenced "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks", BICLE's genesis block marks the beginning:

Code:

Block #0
Timestamp: 2025-11-05T11:20:00Z
News: "The Guardian 05/Nov/2025 - on the brink of a financial crisis for AIs in companies"
Link: https://www.theguardian.com/business/2025/nov/05/global-stock-markets-fall-sharply-over-ai-bubble-fears
iHash: [SHA-256]
blockHash: [SHA-256]
previous: null

Two financial crises. Two protocols. One philosophy: decentralization.


Current Features (v0.1)

✓ RSS Aggregation: 24+ trusted sources (Bitcoin Core, Ars Technica, The Guardian, etc.)
✓ Community Submissions: Anyone can submit news via /submit command
✓ Blockchain Storage: JSON-based, easily auditable
✓ Integrity Verification: /verify command checks entire chain
✓ Auto-mining: New blocks every 5 minutes
✓ Export: Full blockchain export for independent verification
✓ Open Source: MIT License, Python implementation


Comparison: Bitcoin vs BICLE

Feature	Bitcoin	BICLE
Purpose	Decentralize money	Decentralize information
Proof	Proof-of-Work	Proof-of-Information
Block Content	Transactions	News items
Hashing	SHA-256	SHA-256
Consensus	Longest valid chain	Longest valid chain (future)
Storage	~500GB blockchain	Lightweight (text only)
Network	Global P2P	Centralized (v0.1) → P2P (v0.2+)

"But You're Using Centralized Sources?"

Yes. And here's why that's not a contradiction:

BICLE v0.1 is infrastructure, not the final product.

Bitcoin didn't eliminate banks overnight. But it created the infrastructure for alternatives to emerge.

BICLE doesn't eliminate centralized journalism. But it creates the infrastructure for decentralized journalism to exist.

What v0.1 provides:
- Immutable record of existing sources
- Proof that "source X said Y at time Z"
- Tamper-evident history
- Community curation layer
- Foundation for future decentralization

Evolution path:

Code:

v0.1 → Aggregates centralized sources + creates immutable record
v0.2 → P2P node network + distributed consensus
v0.3 → NOSTR integration + Lightning Network rewards
v1.0 → Fully decentralized journalism production

We're building the Git of journalism. It doesn't matter where code was written—what matters is the history is immutable and auditable.


Roadmap

✓ Q4 2025 - v0.1 (CURRENT)
- Genesis block
- Basic blockchain implementation
- Telegram bot interface
- RSS aggregation
- Community submissions
- Public release

Future - v0.2
- P2P node network
- Blockchain synchronization
- Distributed consensus
- Multiple node deployment

Future - v0.3
- NOSTR protocol integration
- Decentralized identities (npub/nsec)
- Lightning Network zaps (Bitcoin rewards)
- Reputation system

Future - v1.0
- Full decentralization
- Web/mobile interfaces
- Regional forks (BICLE-US, BICLE-BR, etc.)
- Topic specialization (Tech, Politics, Science, Health)
- Production-ready release


Use Cases

1. Verify Historical Claims
Politician: "I never said that."
BICLE: Shows timestamped, hashed proof from 3 years ago

2. Prevent Memory-Holing
News site deletes controversial article.
BICLE: iHash and timestamp prove it existed

3. Whistleblower Protection
Anonymous submission with timestamp.
BICLE: Cryptographic proof information existed before investigation

4. Community Journalism
Local event ignored by mainstream media.
BICLE: Community member submits, creates permanent record


Technical Implementation

Language: Python 3.8+
Dependencies: python-telegram-bot, feedparser, python-dotenv
Storage: JSON (v0.1), Future: LevelDB/SQLite
Interface: Telegram Bot (v0.1), Future: Web/Desktop/Mobile

Run a node:

Code:

git clone https://github.com/bicle01/bicle-protocol
cd bicle-protocol
pip install -r requirements.txt
python bicle.py

Verify blockchain:

Code:

/verify    # Check integrity
/export    # Download full blockchain JSON
/block 0   # View genesis block

Security Considerations

Current (v0.1):
- Centralized nodes (single point of failure)
- No consensus mechanism yet
- Rate limiting on submissions
- Cryptographic verification of chain integrity

Future (v0.2+):
- P2P network eliminates single point of failure
- Consensus via longest valid chain
- Sybil resistance via NOSTR identities
- Economic incentives (zaps) discourage spam


Open Source & Contributing

BICLE is 100% open source under MIT License.

Contribute:
- Run a node
- Submit pull requests
- Test and report bugs
- Add RSS sources
- Translate documentation
- Spread the word

GitHub:
License: MIT
Language: Python


The Vision

Imagine a world where:

✓ News cannot be silently deleted or edited
✓ Anyone can verify what was said and when
✓ Community validates journalism, not corporations
✓ Quality reporting is rewarded with Bitcoin
✓ No algorithm manipulates what you see
✓ Information flows freely, without censorship

That is BICLE's vision.

Bitcoin taught us: Don't trust, verify.

That principle applies to money. It should apply to information too.


Why BitcoinTalk?

This community understands decentralization better than anyone. You lived through Bitcoin's early days. You understand why trustless systems matter. You've seen how one protocol can change the world.

I'm here because BICLE is built on the same principles Satoshi outlined in 2009:

"The root problem with conventional currency is all the trust that's required to make it work."

Replace "currency" with "journalism" and you have BICLE's mission.

I'm asking for:
- Technical feedback on the architecture
- Security review of the implementation
- Ideas for P2P consensus mechanism
- Community involvement in development

This is v0.1 - experimental, rough, but functional. Just like Bitcoin v0.1 was.


Demo

NOSTRl: npub1sx33m49zg9hwgd8h08su45uf8zshrae3tx53rfs8ckh0xcv7syrsjsw85x


Try:
- /start - See available commands
- /block 0 - View genesis block
- /verify - Verify blockchain integrity
- /export - Download full blockchain


Final Words

Satoshi gave us the tools to decentralize money.
Now we're using those tools to decentralize truth.

Bitcoin proved that mathematics can replace institutional trust.
BICLE applies that lesson to information.

This is v0.1. It's experimental. It's imperfect. But it's a start.

Just like Bitcoin was on January 3, 2009.

"In cryptography we trust."

---

Genesis: November 5, 2025
Status: Live & Open Source
License: MIT

Questions? Technical discussions? Fork ideas? Let's talk.

[qwertyNpc]

website?

[Bicle]

Not yet — the website is under development.

For now, all official BICLE materials are available here:
 Whitepaper
 GitHub Repository

[qwertyNpc]

Is it possible to mine using an ASIC?

[Bicle]

No, it’s not possible to mine using ASICs — Bicle doesn’t rely on computational mining.

We’re in an early, experimental phase (v0.1). Bicle is currently a Proof-of-Information system — blocks are created by collecting and hashing news data, not by solving mathematical puzzles like Bitcoin.

Over time, as the project evolves and more people understand and join the concept, we’ll move toward a distributed curation network — where “mining” will represent validating and timestamping truthful information instead of consuming hardware power.

This is just the beginning — just like Bitcoin’s first version, Bicle will evolve with the community that believes in decentralization and transparency.

[Bicle]

Maybe in the future, computing power could even play a role for the bicle; we don't know yet.

[qwertyNpc]

Thank you

[gameparadise007]

Hello,
I tried to run a node and I have few questions.

• Is there a wallet to store any coins or any address or private key etc ?
• I was able to solve blocks from telegram using /mine, but the auto mine feature don’t work from the node. It always give me errors.

[Bicle]

Thanks for trying to run a node and for the questions! Let me clarify a few things:




There's NO wallet, coins, address, or private keys in BICLE v0.1.

This is a common misunderstanding because we use Bitcoin-inspired terminology ("node", "mine", "block").

Let me clarify what BICLE actually does:

BICLE doesn't create cryptocurrency. It creates an immutable record of INFORMATION.

Think of it this way:
- Bitcoin stores financial transactions
- BICLE stores news items

No tokens. No coins. No monetary value (yet - v0.3 might include Lightning rewards for curators, but that's future).

The current v0.1 is purely about creating cryptographic proof of "what was published when."

---

[AUTO-MINE NOT WORKING]

You mentioned /mine works but auto-mining doesn't. This is likely a permission issue.

Did you add your bot as an ADMINISTRATOR to your Telegram channel with "Post Messages" permission enabled?

Steps to fix:
1. Open your Telegram channel
2. Click channel name → Administrators → Add Administrator
3. Select your bot
4. Enable "Post Messages" permission
5. Save

Also verify your .env file has:

TELEGRAM_TOKEN=your_token_here
CHANNEL_ID=(your channel ID, ex: -100...)

The CHANNEL_ID should start with -100 (that's how Telegram formats channel IDs).

If you did all this and it still doesn't work, paste the error message here and we can debug further.

---



You're absolutely right to question the terms "node" and "mine" — they're borrowed from Bitcoin but work differently here.

Current reality (v0.1):
- "Node" = Your local instance running the bot
- "Mine" = Fetch RSS feeds + create a new block with SHA-256 hashes
- "Block" = Collection of up to 5 news items with cryptographic proof

We're NOT mining in the Bitcoin sense (no computational puzzles, no proof-of-work).

We're simply:
1. Fetching news from RSS sources (Tech category)
2. Creating SHA-256 hashes for each item (iHash)
3. Grouping them into blocks
4. Chaining blocks together (each points to previous block's hash)
5. Storing locally in blocks.json

The terminology is aspirational — it represents what BICLE will become:
- v0.2: True P2P network (multiple independent nodes)
- v0.3: "Mining" with reputation rewards (Lightning Network)
- v1.0: Decentralized consensus (like Bitcoin's longest chain)

Right now, each "node" runs independently and maintains its own blockchain locally. There's no global consensus yet.


---

Can you run this command and tell me what you see?

/block 0

This should display BICLE's Genesis Block:

Block #0
Timestamp: 2025-11-05T11:20:00Z
Source: The Guardian
Title: "On the brink of a financial crisis for AIs in companies"

If you see this, your node is working correctly.



I'd love to hear:
1. Did the concept make sense after reading the whitepaper?
2. What's your technical background?
3. Any suggestions for improving the setup process?




Thanks again for running a node and for the questions. This kind of early feedback is exactly what helps shape the protocol.

Let me know if the admin permission fix solves the auto-mining issue, and whether /block 0 shows the 'genesis block' correctly.

[Bicle]

When you used /mine, what were the blocks that you mined? What was the title + source and summary?

[gameparadise007]

It is automatically creating new blocks now.
Followed the steps and the issues were fixed.
What is next, will you add any coins and mining to this in future?

[Bicle]

Just to clarify: there's no "will you add any coins..." in BICLE — it's a community protocol, fully open source.

Anyone can contribute, fork, or propose features. The code belongs to everyone, just like Bitcoin itself.

So when thinking about future features, it's not "will you add" — it's "will the community build this together."

That's the whole point of decentralization.

To directly answer your question:

BICLE v0.1-v0.2 does NOT involve coins, tokens, or traditional mining in the Bitcoin sense.

There's:
- No cryptocurrency
- No proof-of-work mining (computational puzzles)
- No block rewards in coins

The term "mining" in BICLE refers to:
- Fetching news from RSS feeds
- Creating SHA-256 hashes (iHash)
- Grouping into blocks
- Storing on the blockchain

It's "mining information," not mining coins.

That said, future versions (v0.3+) will integrate Bitcoin — but NOT as a mined token.

The plan is:

v0.3: NOSTR Integration + Lightning Network

When BICLE integrates with NOSTR (decentralized social protocol), the community will be able to:

✓ Reward quality journalism with Bitcoin (Lightning zaps)
✓ Tip independent reporters directly
✓ Build reputation based on zaps received
✓ Create economic incentives for truth

Example:
1. Journalist posts verified news to NOSTR
2. BICLE records it on blockchain (immutable proof)
3. Community validates and sends Lightning zaps (Bitcoin tips)
4. Journalist earns Bitcoin for quality work
5. Reputation increases, more visibility

This creates a decentralized journalism economy powered by Bitcoin.

No new tokens. No ICO. Just Bitcoin's Lightning Network.



Bitcoin is the only proven, decentralized, censorship-resistant currency.

Anything else would:
- Introduce centralization
- Require trust in new systems
- Dilute the mission

For a complete understanding of BICLE's vision, roadmap, and technical details, I strongly recommend reading the whitepaper:

https://archive.org/details/bicle-whitepaper


Since this is open source and community-driven, contributions are welcome:

- Code improvements (GitHub PRs)
- Testing and bug reports
- Running independent nodes
- Proposing Lightning integration designs
- Writing documentation
- Spreading the word

The protocol evolves based on community input, not a central authority.


https://github.com/bicle01/bicle-protocol