DEV Community: Mahmud eyitoba bello

#icp

Mahmud eyitoba bello — Mon, 03 Feb 2025 18:42:24 +0000

Build Your First Todo App on ICP: A Friendly Guide

Mahmud eyitoba bello ・ Feb 3

Build Your First Todo App on ICP: A Friendly Guide

Mahmud eyitoba bello — Mon, 03 Feb 2025 18:34:08 +0000

Ready to build something cool on the Internet Computer? Let's create a todo app together. Don't worry if you're new to this - I'll walk you through everything step by step, no fancy jargon required.

Why ICP Is Pretty Cool

Think of Internet Computer like a giant, shared computer that's always online. Instead of running your app on servers owned by big companies, it runs on a network that belongs to everyone. Pretty neat, right? Here's why it's awesome:

Your app never goes down (unless the internet itself breaks!)
You don't need to pay for expensive servers
Users don't pay gas fees like on other blockchains
It's fast - like, really fast

Getting Started

First, let's get your computer ready. Open your terminal and type:

sh -ci "$(curl -fsSL https://sdk.dfinity.org/install.sh)"

This installs dfx - your new best friend for building ICP apps. Now create your project:

dfx new todo_app
cd todo_app

Building the Brain (Backend)

Let's create the backend first. find a file called src/todo_app_backend/main.mo and drop in this code:

import Array "mo:base/Array";
actor {
    // This is what each todo looks like
    type Todo = {
        id: Nat;
        text: Text;
        completed: Bool;
    };

    // Keep all todos in one place
    private var todos: [Todo] = [];
    private var nextId: Nat = 0;

    // Add a new todo to the list
    public func addTodo(text: Text) : async Nat {
        let todo: Todo = {
            id = nextId;
            text = text;
            completed = false;
        };
        todos := Array.append(todos, [todo]);
        nextId += 1;
        return todo.id;
    };

    // Get all your todos
    public query func getTodos() : async [Todo] {
        return todos;
    };

    // Mark a todo as done (or not done)
    public func toggleTodo(id: Nat) : async Bool {
        todos := Array.map(todos, func (todo: Todo) : Todo {
            if (todo.id == id) {
                return {
                    id = todo.id;
                    text = todo.text;
                    completed = not todo.completed;
                };
            };
            todo;
        });
        return true;
    };

    // Remove a todo
    public func deleteTodo(id: Nat) : async Bool {
        todos := Array.filter(todos, func(todo: Todo) : Bool { 
            todo.id != id 
        });
        return true;
    };
}

Making It Pretty (Frontend)

Now for the part you'll actually see! Create src/todo_app_frontend/src/main.jsx:

import React, { useState, useEffect } from 'react';
import { todo_app_backend } from 'declarations/todo_app_backend';

function App() {
    const [todos, setTodos] = useState([]);
    const [newTodo, setNewTodo] = useState('');

    // Get all todos when the app starts
    const loadTodos = async () => {
        const result = await todo_app_backend.getTodos();
        setTodos(result);
    };

    // Add a new todo
    const handleAdd = async (e) => {
        e.preventDefault();
        if (!newTodo.trim()) return;
        await todo_app_backend.addTodo(newTodo);
        setNewTodo('');
        loadTodos();
    };

    // Mark a todo as done/not done
    const handleToggle = async (id) => {
        await todo_app_backend.toggleTodo(id);
        loadTodos();
    };

    // Delete a todo
    const handleDelete = async (id) => {
        await todo_app_backend.deleteTodo(id);
        loadTodos();
    };

    useEffect(() => {
        loadTodos();
    }, []);

    return (
        <div className="container mx-auto p-4">
            <h1 className="text-2xl font-bold mb-4">Todo List</h1>

            <form onSubmit={handleAdd} className="mb-4">
                <input
                    type="text"
                    value={newTodo}
                    onChange={(e) => setNewTodo(e.target.value)}
                    className="border p-2 mr-2"
                    placeholder="Add new todo"
                />
                <button type="submit" className="bg-blue-500 text-white px-4 py-2 rounded">
                    Add
                </button>
            </form>

            <ul>
                {todos.map((todo) => (
                    <li key={todo.id} className="flex items-center mb-2">
                        <input
                            type="checkbox"
                            checked={todo.completed}
                            onChange={() => handleToggle(todo.id)}
                            className="mr-2"
                        />
                        <span className={todo.completed ? 'line-through' : ''}>
                            {todo.text}
                        </span>
                        <button
                            onClick={() => handleDelete(todo.id)}
                            className="ml-auto text-red-500"
                        >
                            Delete
                        </button>
                    </li>
                ))}
            </ul>
        </div>
    );
}

export default App;

Starting It Up

Time to see your app in action! In your terminal:

dfx start --clean --background
dfx deploy

Your app will pop up at http://localhost:4943. Pretty cool, right?

What's Actually Happening Here?

Let's break down what we just built:

The Motoko code (backend) is like a super-secure notebook:
- It remembers all your todos
- Gives each todo a unique ID
- Keeps track of what's done and what isn't
- Can add, check off, or delete todos
The React code (frontend) is like a friendly interface:
- Shows you all your todos
- Lets you type in new ones
- Has checkboxes to mark things as done
- Includes delete buttons to remove todos

Cool Things You Can Add

Now that you've got the basics working, why not spice it up? You could:

Add due dates
Group todos into categories
Share todos with friends
Add file attachments

When Things Go Wrong

Don't panic! Here's what to check:

Is dfx running? (check with dfx status)
Did you save all your files?
Are there any red error messages?
When in doubt, try dfx deploy again

Need Help?

Everyone gets stuck sometimes. Here's where to find help:

DFINITY's Discord channel
Stack Overflow (tag: 'internet-computer')
Internet Computer forums

Remember: every developer started exactly where you are now. Take your time, have fun, and don't be afraid to experiment - that's how we learn!

The Four Layers of Internet Computer Protocol

Mahmud eyitoba bello — Fri, 17 Jan 2025 20:42:46 +0000

Understanding ICP's Four Layers: A Friendly Guide

Hey there! Let's break down how the Internet Computer Protocol (ICP) works in a way that actually makes sense. Think of ICP like a really well-organized city, where different departments work together to keep everything running smoothly. Let's explore each "department" (or layer) and see what they do.

The Four Layers: Your Quick Guide

Before we dive in, here's what we're going to cover:

P2P Network Layer (how computers talk to each other)
Consensus Layer (how they agree on things)
Message Routing Layer (how messages find their way)
Execution Layer (where the actual work happens)

Layer 1: P2P (Peer-to-Peer) Network Layer

Think of this as the city's road system and communication network

What is P2P, anyway?

P2P means "peer-to-peer" - imagine it like people talking directly to each other instead of going through a middle person. In computer terms, it's when computers connect and share information directly, rather than going through a central server.

What does this layer do?

Finds Other Computers
- Keeps track of who's who in the network
- Helps computers find each other (like a phone book)
- Notices when new computers join or leave
Manages Connections
- Makes sure computers can talk to each other
- Keeps connections strong and reliable
- Handles backup connections if some fail

Real-world example: It's like how your phone knows how to find and connect to other phones for a video call, even if you're both moving around.

Layer 2: Consensus Layer

Think of this as the city's decision-making system

What is Consensus?

Consensus is just a fancy word for "everyone agreeing on something." In ICP, it's how all the computers in the network agree on what's happening and in what order.

How does it work?

Making Decisions
- Computers vote on what happened and when
- Makes sure everyone has the same information
- Prevents any single computer from cheating
Keeping Things in Order
- Decides which actions happen first
- Makes sure everything is recorded properly
- Keeps track of the official history

Real-world example: It's like how a group of friends decides where to go for dinner - everyone needs to agree on the final choice, and they need to remember what they decided.

Layer 3: Message Routing Layer

Think of this as the city's postal service

What is Message Routing?

This is how information gets from Point A to Point B in the network. It's like having a really smart postal service that knows exactly how to get packages to their destination.

What does it handle?

Delivering Messages
- Makes sure messages reach the right destination
- Finds the best path for each message
- Handles messages between different parts of the network
Traffic Management
- Prevents message traffic jams
- Makes sure important messages get through first
- Handles backup plans if the usual path is blocked

Real-world example: Like how GPS finds the best route for your car, considering traffic, road closures, and shortcuts.

Layer 4: Execution Layer

Think of this as where the actual work gets done - like the city's factories and offices

What is Execution?

This is where computer programs (called "canisters" in ICP) actually run and do their job. It's where all the actual computing happens.

What happens here?

Running Programs
- Runs the actual applications (called "canisters")
- Manages computer memory and resources
- Makes sure programs run correctly and safely
Managing Resources
- Keeps track of how much computing power is used
- Makes sure programs don't use too much memory
- Handles program storage and data

Real-world example: It's like how your phone runs apps - it needs to make sure each app has enough memory and battery power, and that they're not interfering with each other.

How Do These Layers Work Together?

Like departments in a well-run organization

Let's follow what happens when you use an app on ICP:

You click a button in an app
The P2P layer figures out which computers need to handle your request
The Consensus layer makes sure everyone agrees on what you're trying to do
The Message Routing layer gets your request to the right place
The Execution layer actually performs the action you wanted

Why This Matters to You

Even if you're not a tech person, understanding these layers helps you:

Know how your apps and data are being handled
Understand why ICP is different from regular internet services
Make better decisions about using ICP services

Common Questions Answered

"Why do we need all these layers?"

Each layer has a specific job, like departments in a company. Having specialized layers makes everything run more smoothly and safely.

"What makes ICP different from regular internet?"

Regular internet relies on big companies running central servers. ICP spreads everything across many computers, making it harder to shut down and more fair for everyone.

"Is it complicated to use?"

Nope! All these layers work behind the scenes. When you use an ICP app, it feels just like using any other app - all the complex stuff happens automatically.

Wrapping Up

Think of ICP's four layers as a well-oiled machine where each part has its job:

P2P Layer connects everyone
Consensus Layer keeps everyone in agreement
Message Routing Layer delivers information
Execution Layer gets things done

Together, they create a system that's:

Hard to shut down
Fair for everyone
Able to run the next generation of internet services

Remember, you don't need to understand all the technical details to use ICP - but knowing the basics helps you appreciate what's happening behind the scenes!

Got questions? Feel free to ask! Sometimes the best way to understand is to relate these concepts to things you already know.

Blockchain Fundamentals and ICP Architecture: A Deep Dive

Mahmud eyitoba bello — Fri, 17 Jan 2025 20:32:04 +0000

Hey there! Let's dive into the fascinating world of blockchain and the Internet Computer Protocol (ICP). I will break this down in a way that'll make sense, even if you're just getting started with blockchain technology.

The Building Blocks: Understanding Blockchain Basics

Think of a blockchain like a digital ledger that everyone can see, but nobody can tamper with. You know how we used to write important stuff in those big ledger books? Well, blockchain is like that, but way cooler and more secure.

Why Blockchain Matters

Picture this: You're playing a game of Monopoly, but instead of having one banker, everyone at the table keeps track of all the money and properties. If someone tries to cheat, everyone else would know immediately because they all have the same information. That's basically how blockchain works, but for real-world stuff like money, contracts, and applications.

Key things that make blockchain special:

It's like a shared notebook that everyone can read but nobody can erase
Once something's written down, it's there forever (like that embarrassing yearbook photo, but for data)
Everyone agrees on what's written because they all follow the same rules
It works without needing to trust any single person or company

The Internet Computer: Not Your Average Blockchain

Now, let's talk about what makes ICP different from your typical blockchain. Imagine if you could take everything cool about blockchain and combine it with the power of the internet itself. That's basically what ICP is trying to do.

The Secret Sauce: Network Nervous System

Think of the Network Nervous System (NNS) as the brain of the entire operation. It's like having a super-smart autopilot that:

Keeps everything running smoothly
Makes sure everyone plays by the rules
Updates the system when needed
Manages all the resources

The cool part? It's not controlled by any single company or person. Instead, it's run by the community through something called "neurons" (fancy name for voting rights).

Breaking Down the Architecture

Let's look at how ICP is built, layer by layer:

1. The Foundation Layer

This is where all the heavy lifting happens. We've got:

Data centers spread across the world
Super powerful computers working together
Special hardware that keeps everything secure

2. The Protocol Layer

This is the rule book that everyone follows. It includes:

Ways for computers to talk to each other
Security measures to protect everything
Methods for reaching agreement on what's happening

3. The Canister Layer

This is where things get really interesting. Canisters are like super-powered smart contracts that can:

Run websites directly on the blockchain
Store and process data
Talk to other canisters
Handle user interactions

What Makes ICP Special?

Speed and Scalability

Remember how Bitcoin can only handle a few transactions per second? ICP can handle thousands. It's like comparing a bicycle to a sports car.

Real Web Integration

Most blockchains can't interact directly with the internet. ICP can. It's like having a blockchain that speaks fluent "internet."

Cost Effectiveness

Instead of paying crazy fees for every little thing (looking at you, Ethereum), ICP uses something called "cycles" which are way more predictable and usually cheaper.

Real-World Applications

Let's talk about what you can actually do with this stuff:

Web3 Applications

Social media platforms that users actually own
Games where your items are truly yours
Financial services without the banks

Business Solutions

Supply chain tracking that actually works
Secure document storage
Identity verification systems

Developer Tools

Building websites that can't be taken down
Creating applications that run themselves
Making services that don't need servers

Looking Ahead

The really exciting part about ICP is where it's heading. Imagine:

Websites that never go down
Apps that can't be censored
Services that run themselves
Digital identities you actually control

Some Final Thoughts

Remember when the internet first came out, and most people couldn't imagine how it would change our lives? ICP and blockchain technology are at that same stage right now. We're just scratching the surface of what's possible.

The architecture might seem complicated (and honestly, parts of it are), but the goal is simple: create a better, more open internet that everyone can use and nobody can control.

Whether you're a developer, business owner, or just someone interested in technology, understanding these fundamentals puts you ahead of the curve. As we move towards a more decentralized future, the principles and architecture we've discussed here will become increasingly important.

Keep exploring, keep asking questions, and most importantly, keep imagining what's possible. After all, that's how all great technological revolutions start.

Stay curious, and see you in the decentralized future!

AI Agents Meet TEEs: When Digital Minds Get Their Own Secret Bunkers

Mahmud eyitoba bello — Thu, 02 Jan 2025 20:15:35 +0000

The Deep Dive

Remember when you were a kid and had a secret hideout where you could think, plan, and dream without anyone bothering you? That's basically what we're giving to AI agents when we combine them with Trusted Execution Environments (TEEs). But instead of a treehouse, they get an ultra-secure digital bunker inside a computer processor.

Why This Marriage Makes Sense

Think about it: AI agents are getting smarter and more autonomous by the day. But with great power comes great responsibility (thanks, Spider-Man!). We need ways to:

Keep their processing secure
Protect sensitive data they work with
Verify their decisions are trustworthy

TEEs solve all these problems in one elegant package. It's like giving each AI agent their own personal vault where they can:

Process sensitive data without exposure
Make decisions that can't be tampered with
Prove their work without revealing their secrets

Real-World Applications That'll Blow Your Mind

1. The Financial Advisor That Keeps Your Secrets

Imagine an AI financial advisor that can:

See your complete financial history
Know your secret investment goals
Analyze your risk tolerance
Make personalized recommendations

But here's the kicker: all this sensitive information never leaves the TEE. The only thing that comes out is the final advice, like "Buy these three stocks." Even the people running the AI service can't spy on your financial details!

2. The Ultimate Privacy-Preserving Medical Assistant

Healthcare AI is amazing, but privacy is crucial. With TEEs:

Patient data stays encrypted
Analysis happens in the secure environment
Only necessary results are shared
Everything is HIPAA-compliant by design

The Plot Thickens: AI Agents Working Together

Now here's where it gets really interesting. When multiple AI agents with TEEs work together, they can:

Share insights without exposing raw data
Verify each other's behavior
Collaborate on sensitive tasks
Maintain privacy between themselves

It's like having a team of super-smart consultants who can work together while keeping their sources and methods completely confidential.

What's Next? The Future is Wild

The combination of AI agents and TEEs is opening up possibilities that sound like sci-fi:

Autonomous Negotiators: AI agents that can handle sensitive business deals with genuine confidentiality
Privacy-Preserving Social Networks: Where AI moderators can spot bad behavior without actually reading your private messages
Secure Multi-Agent Systems: Teams of AI agents working together on sensitive tasks while maintaining perfect isolation
Trustworthy Autonomous Systems: Self-driving cars and robots with verifiably secure decision-making processes

The Cherry on Top: Verifiable Trust

The really cool part? All of this happens with mathematical certainty. When an AI agent processes something in a TEE:

You can verify it followed its rules
You know the data wasn't tampered with
You can prove the results are legitimate

It's like having a notary public for AI decisions!

Wrapping Up

The marriage of AI agents and TEEs is like giving digital minds their own secure space to think, grow, and collaborate. It solves some of the biggest challenges in AI adoption: privacy, security, and trust.

As these technologies mature, we're going to see more and more applications that seemed impossible before. AI agents will be able to handle our most sensitive tasks while keeping our secrets safer than ever.

The future isn't just about making AI smarter – it's about making it more trustworthy. And TEEs are helping pave the way to that future, one secure computation at a time.

TEEs

Mahmud eyitoba bello — Thu, 02 Jan 2025 09:02:22 +0000

TEEs: The Secret Sauce Making Ethereum Rollups Faster and Simpler

Mahmud eyitoba bello ・ Jan 2

#rollup #evm #blockchain #zkp

TEEs: The Secret Sauce Making Ethereum Rollups Faster and Simpler

Mahmud eyitoba bello — Thu, 02 Jan 2025 08:53:38 +0000

TEEs: The Secret Sauce Making Ethereum Rollups Faster and Simpler

Remember when you first heard about blockchain scaling and your head started spinning with terms like zero-knowledge proofs and validity proofs? Well, there's a new kid on the block that's making waves in the Ethereum scaling world: Trusted Execution Environments (TEEs). And trust me, this one's actually pretty cool to wrap your head around.

What's the Big Deal About TEEs?

Imagine you're sending a super important letter. In the traditional world, you might use a notary - someone everyone trusts to verify that everything is legit. TEEs are kind of like having a tiny, super-secure notary built right into your computer's processor. Pretty neat, right?

How Does it Actually Work?

Let's break this down into something we can all understand. When you're running a rollup (which is basically a way to bundle lots of Ethereum transactions together), you need to prove that nobody's trying to pull a fast one. Traditionally, this meant using zero-knowledge proofs - super complex math that makes your computer sweat.

Enter TEEs. They're like having a secure vault inside your processor where you can run code that even you can't mess with. It's like having a tamper-proof room where all your transactions get processed.

Why This is Actually Pretty Cool

Here's what makes TEEs a game-changer for Ethereum rollups:

Speed Demon: Instead of crunching complex math proofs, TEEs just need to generate a simple signature saying "yep, this all checks out!" It's like going from writing a dissertation to just getting a quick notary stamp.
Trust Made Simple: While you do need to trust the TEE manufacturer (like Intel or AMD), it's a pretty straightforward kind of trust. It's similar to how you trust your phone's secure enclave to handle your fingerprint data.
Developer Friendly: Writing code for TEEs is much more straightforward than developing zero-knowledge proofs. It's basically just regular programming with some extra security guarantees.

Real World Impact

When you're actually implementing this in practice, you'd typically use something like Intel SGX or AMD SEV. These are the industrial-strength versions of TEEs that major companies trust with their sensitive data. Your rollup's EVM (the thing that processes Ethereum transactions) runs inside this secure environment, happily crunching away at transactions while the TEE keeps watch.

The best part? At the end of processing a batch of transactions, the TEE spits out a simple attestation - basically a cryptographic signature saying "I processed everything according to the rules." This gets posted back to Ethereum's main chain, and everyone can quickly verify it's legit.

What's Next?

The TEE approach to rollups is still relatively new, but it's gaining traction fast. While traditional zero-knowledge proof rollups aren't going anywhere, TEEs offer an exciting alternative that might just be the sweet spot between security, performance, and practicality.

Think of it this way: sometimes the best solutions aren't about inventing completely new math - they're about finding clever ways to use technology we already trust in new and interesting ways. TEEs in rollups are exactly that kind of clever hack, and that's what makes them so exciting for the future of Ethereum scaling.

Proof of work or proof of stake

Mahmud eyitoba bello — Wed, 02 Mar 2022 22:08:32 +0000

Division of a Blockchain

Blockchain , a distributed but robust database of nodes ,is divided into six parts :

OOR Interface: Part for the mapping and delegation resolution using LISP
Peer to peer protocol: Protocol used in order to communicate the multiple nodes in the network.
Consensus Algorithm(Focus of this report): Algorithm used to decide, depending on the inputs, who signs a block.
User input: Module to allow the communication from the user with the blockchain. Typically a file with transactions to be added.
Keystore: Storage of the keys.
Chain persistence: Database structure in which all the data from the Blockchain will be stored.

Our major focus here is the Consensus algorithm

What's Consensus Algorithm ?

A consensus algorithm is a mechanism in computer science theory used to establish agreement on a single data value across distributed processes or systems. A consensus algorithm is a protocol through which all the parties of the blockchain network come to a common agreement (consensus) on the present data state of the ledger and be able to trust unknown peers in a distributed computing environment. Sounds simple .

For blockchain networks, the consensus algorithms are an essential element because they maintain the integrity and security of these distributed computing systems.

Proof Of work and proof of Stake are forms of Consensus algorithm

Proof Of Work (P.o.W)

The main idea behind proof of work is to work hard in order to demonstrate
the commitment a node has with the network and thus, receiving a reward for
the work done. This is often known as mining.
In Bitcoin, for example, a reward is given to the first node that finds a specific
hash by hashing some information. The correct hash is a SHA-256 string made
by the transactions of the block, the previous block hash and the nonce, which
consists on having a leading number of zero bits. Two of the three parameters
of the SHA-256 hash are static, but one of them, the nonce, is selected by using
brute force, as it is the only known way to find the correct hash.
Proof of work is used nowadays in blockchains because it provides security to the chain as it is very complex to modify old blocks due to the fact that the
valid chain for the vast majority of the nodes is the longest one, i.e. the chain
with more accumulated computing power. This property ensures that data in
old blocks will not be modified, as it requires a hard computational work in
order to generate "by your self" a blockchain longer than the one that is shared
with the rest of the network.
Despite proof of work seems to be secure, there are some drawbacks that should
be mentioned:

about 30% attack: Some research has been done about the problem of having a group with at least 34% of the hash mining power over the network. Such group could modify the chain and thus turning the blockchain insecure.
Increasing complexity: One of the properties of proof of work blockchains
is that the complexity of mining a block increases over time. This can seen as a strength of the protocol, because it protects the network against new hardware, but it is not. As the complexity increases, there
are only few mining farms1
that can spend enough money to achieve new
specific hardware in order to mine a cryptocurrency. This can lead do a centralization of the mining power, which is contrary to the idea of
decentralization of blockchain.
Energy waste: As the complexity of mining a block increases, it is needed
more hashing power, which can be seen as more energy used. This is nowadays the main problem to solve on blockchains, as there are a lot of
cryptocurrencies using proof of work, i.e. wasting a lot of energy.

Proof Of Stake (P.o.S)

The basics of this Algorithm is that participants or nodes in the network with
more stake in the blockchain, will be able to add blocks more often. Normally,
for each new expected block, a new signer of the block will be selected, through
random criteria, from the list of participants given its weight, i.e., the amount
of stake they have. With this in mind, the power effort destined to mine a block
is much less compared with PoW, thanks to the no hash power needed.
Although PoS give us the advantage of wasting much less energy than PoW and
some more decentralization, it has some drawbacks:

Monopoly: The main drawback of PoS algorithms is that a potential monopoly from the major stakeholders of the network could be possible. This possibility puts those algorithms at the same level of PoW situation that should be avoided.
Nothing at stake: Regarding any proof-of-work blockchain, in front of a
double-spend attack or in a chain fork
, nodes will have three options to
choose:

– Follow chain 1 and probably get benefit if chain 1 wins.

– Follow chain 2 and probably get benefit if chain 2 wins.

– Do nothing and get no benefit

Only one of these three options can be chosen, otherwise you would waste
energy mining on the wrong chain, costing you a lot of money in terms of
electricity.
Using the proof of stake protocol, this situation changes. Having in mind
the small cost of energy on creating a block in a PoS environment, you could easily follow the two created chains using less power than a proof-of-work blockchain miner do.
If this situation occurs, the blockchain will have no order and thus be a
chaos. Moreover, if there is more than one unique chain being followed, it
is probable to have more forks, which could cause more chaos.
On the other hand, proof of stake is suitable for us in this aspects:

Nothing at stake is not worth it in our environment as the major stake-
holders are the most interested in the proper functioning of the chain. In
order to succeed in a nothing at stake attack, a high percentage of the nodes in the network should follow more than one chain when a fork occurs. As the nodes with more stake are the ones interested on a healthy chain, it makes no sense to follow the attack.
Energy is not wasted as it is in proof-of-work blockchains. Typically, the
election of a new signer is made by the use of random criteria and weighted
depending on the stake a node has. So making more attempts per second
do not increase the possibility of being selected as the new signer. Hence,
a reduction in time and energy can be noticed.
Faster chains are possible by using proof-of-stake algorithms. Without the
need of computing a lot of hashes to find the correct one, is possible to create a chain with a higher rate of block generation. Nowadays, taking Bitcoin as an example of a proof-of-work blockchain, one block is createdevery 10 minutes. This situation is not scalable, so proof of stake offers a
faster way for block creation by reducing the time to chose a new block signer.

That seems like a lot , it only gets better......

Distributed ledger Technology

Mahmud eyitoba bello — Wed, 02 Mar 2022 15:39:07 +0000

Definition

A distributed ledger is essentially an asset database that can be shared across
a network of multiple sites, geographies or institutions. All participants within
a network can have their own identical copy of the ledger. Any changes to the
ledger are reflected in all copies in minutes, or in some cases, seconds. The
assets can be financial, legal, physical or electronic. The security and accuracy
of the assets stored in the ledger are maintained cryptographically through the use of ‘keys’ and signatures to control who can do what within the shared ledger.
Entries can also be updated by one, some or all of the participants, according to
rules agreed by the network.
DLT comes on the heels of several peer-to-peer (P2P) technologies enabled by the
internet, such as email, sharing music or other media files, and internet telephony.
However, internet-based transfers of asset ownership have long been elusive, as
this requires ensuring that an asset is only transferred by its true owner and ensuring
that the asset cannot be transferred more than once, i.e. no double-spend. The asset in question could be anything of value.

Application of DLT

Cryptocurrency and Bitcoin

Underlying this technology is the ‘block chain’, which was invented to create
the peer-to-peer digital cash Bitcoin in 2008. Block chain algorithms enable
Bitcoin transactions to be aggregated in ‘blocks’ and these are added to a
‘chain’ of existing blocks using a cryptographic signature. The Bitcoin ledger is
constructed in a distributed and ‘permissionless’ fashion, so that anyone can
add a block of transactions if they can solve a new cryptographic puzzle to add
each new block. The incentive for doing this is that there is currently a reward
in the form of twenty five Bitcoins awarded to the solver of the puzzle for each
‘block’. Anyone with access to the internet and the computing power to solve
the cryptographic puzzles can add to the ledger and they are known as ‘Bitcoin
miners’. The mining analogy is apt because the process of mining Bitcoin is
energy intensive as it requires very large computing power. It has been estimated
that the energy requirements to run Bitcoin are in excess of 1GW and may be
comparable to the electricity usage of Ireland.
Bitcoin is an online equivalent of cash

Government taxation and revenue policies
Distributed ledger technologies have the potential to help governments to
collect taxes, deliver benefits, issue passports, record land registries, assure the
supply chain of goods and generally ensure the integrity of government records
and services. In the NHS, the technology offers the potential to improve health
care by improving and authenticating the delivery of services and by sharing
records securely according to exact rules. For the consumer of all of these
services, the technology offers the potential, according to the circumstances, for
individual consumers to control access to personal records and to know who has
accessed them.
money & Payments
• Payment authorization, clearance & settlement
• International remittances and cross-border payments (alternative to correspondent banking)
• Foreign exchange
• Micropayments
Healthcare
Electronic medical records
Governance • E-voting systems
• E-Residence
• Government record-keeping, e.g. criminal records
• Reducing fraud and error in government payments
• Reducing tax fraud
• Protection of critical infrastructure against cyberattacks

Merits of DLTS

Decentralization and disintermediation. DLT enables direct transfers of digital
value or tokens between two counterparties and decentralized record-keeping,
removing the need for an intermediary or central authority who controls the ledger.
This can translate into lower costs, better scalability and faster time to market.
Greater transparency and easier auditability.
All network members have a
full copy of the distributed ledger (which can be encrypted). Changes can only be made when consensus is established and they are propagated across the entire network in real-time. This feature, combined with the lack of a central authority or limited involvement of a central authority, has the potential to reduce fraud and eliminate reconciliation costs.
Automation & programmability. DLT enables programming pre-agreed
conditions that are automatically executed once certain conditions hold. This is
referred to as “smart contracts” (see section 8), for example invoices that pay
themselves when a shipment arrives or share certificates which automatically
send owners dividends or cash-for-work programs that pay beneficiaries out
once the contracted work is completed. Smart contracts can be done in traditional
centralized ledger systems as well, but the design of centralized ledger systems
requires such actions to be implemented only after the concerned parties have
agreed to the underlying transaction as recorded in the central system, which in
some contexts can take upwards of a day. In contrast, in a DLT, the counterparties
by definition agree the moment the transaction is completed, as both have the
same record of the transaction. Also, the result of the execution of the “smart contract” itself will take additional time to propagate and be reconciled in a traditional ledger system.
Immutability & verifiability.
DLT can provide an immutable and verifiable
audit trail of transactions of any digital or physical asset. While in most cases,
immutability is desirable, it can create problems related to recourse mechanisms if the system fails. Immutability of the ledger, however, does not mean that a countervailing transaction to annul a disputed transaction cannot be created. This is in line with how dispute
resolution works, for example in payment card systems. The original record would, however, in this case still remain. Two MIT researchers have recently filed a patent for a cryptographic solution
that would allow an administrator to ‘unlock’ units
in a blockchain and edit them, though this is highly
controversial as immutability is seen as one of the core advantages of the first blockchains.
Gains in speed and efficiency.
DLT offers
the potential of increasing speed and lowering
inefficiencies by removing or reducing frictions in
transactions or in clearing and settlement processes
by removing intermediaries and automating
processes.

-Cost reductions.
DLT offers the potential for
significant cost reductions due to removing the
need for reconciliation as DLT-based systems by
definition contain the “shared truth” and hence there
is no need to reconcile one version of “truth” with
that of one’s counterparties. Additional sources of
cost reduction could be lower infrastructure costs for
maintaining a DL, as well as reductions in frictions
and fraud. According to some estimates, distributed
ledger technology could save the financial industry
alone around $15-20 billion per year.

Enhanced cybersecurity resilience. DLT has the potential to provide a more resilient system than traditional centralized databases and offer better protection against different types of cyber attacks because of its distributed nature, which removes the single point of attack.

Challenges associated with DLT

Privacy: In permissionless ledgers, such as Bitcoin
and Ethereum, all transactions are open and visible
to all network members, though they can be
encrypted and the identity of the user is hidden. In
certain contexts, the identity of the participant can
be inferred based on transaction patterns or other
markers. Permissioned DLs encounter the same
issue. This is one of the key concerns of applying
DLT to financial market infrastructures and it is one
of the issues which CORDA and Fabric propose to
address in their design.
- Environmental costs. Using proof-of-work as a consensus mechanism creates a large electricity footprint as vast amounts of computing processing power are used up for “mining”. (This concern mainly applies to permissionless blockchains that use proof-of-work protocols.)
- Bleeding Edge/Lack of Maturity. DLT remains at an early stage of development and there are still serious concerns about the robustness and resilience of DLT especially for large volume transactions, availability of standardized hardware and software applications, and also ample supply of skilled professionals. However, large traditional IT players like IBM and Microsoft, as well as financial sector players like Visa and MasterCard have started developing DLT products and services, which could eventually provide the same level of trust and confidence as traditional IT systems offer today.
- Scalability and Transaction Speed. Current iterations of permissionless distributed ledgers face issues related to scalability of blockchains, both in terms of transaction volume and speed of verifications. Existing permissionless blockchains have limited transaction speed. Bitcoin, for example, can only process between 4-7 transactions per second due to the limitation of the block size at one megabyte, a subject of controversy in the bitcoin community. (Block size could be increased but bigger blocks would take longer to propagate through the network, worsening the risks of forking.) This problem, however, could be resolved over time and is most pronounced in the Bitcoin system. Other permissionless DLT systems like Ethereum report higher transaction throughputs. In addition, permissioned blockchains have greater capacity and can process higher transaction volumes but these lack global scale and come at the expense of a more centralized, less transparent platform, which removes many of the benefits from the distributed, open nature of public DLT systems.
- Interoperability and Integration. Different DLT systems will need to be interoperable with other ledgers and integrated with existing systems if they are to be introduced at scale into the financial system. In addition, the cost of integrating DLT into financial infrastructures like payment and settlement systems will require industry wide co- ordination and collaboration and require significant expenses. There are efforts underway to develop DL frameworks specifically for the financial sector, notably the CORDA framework by R3 CEV and Fabric by Hyperledger project. These two frameworks are an effort to address specific requirements raised by industry practitioners in areas such as: • allowing transactions between counterparties in a peer-to-peer manner; need for validating identity of counterparties; • limiting visibility of transactions on a need-to- know basis; need for regulators to have access to transactions; • ensuring equivalence between smart contracts and actual legal prose; • using existing industry standard software tools; • interfaces between multiple distributed ledgers; and • supporting a variety of consensus models, including one approach of just having the transacting counterparties participate in the consensus. These frameworks, in essence, explore using DL approaches within prevailing business and regulatory practices. CORDA is specifically focused on the financial sector whereas Hyperledger seeks to provide a broader framework with initial applications proposed for the financial sector and for supply chain management.

Blockchain and web 3.0

Mahmud eyitoba bello — Wed, 02 Mar 2022 15:34:51 +0000

Web 3.0 is the third generation of internet services which provide websites and applications with the technology to run. Web 3.0 is set to be powered by AI and peer-to-peer applications like blockchain. The key difference between Web 2.0 and Web 3.0 is that Web 3.0 is more focused on using innovative technologies like machine learning and AI to create more personalized content for each user. It is also expected that Web 3.0 will be more secure than its predecessors because of the system it is built upon.

The Web3 has set out to break up the market power of these centralized players by replacing the centralized server-client infrastructure with distributed ledgers, the most common type being the blockchain. So instead of all data being stored on a centralized server, it will be scattered across a decentralized computer network. Centralized entities, which previously acted as intermediaries, will thus become obsolete.

Here is an example: Anyone sending money from one bank to another today uses the centralized servers of the respective banking providers. The banks act as intermediaries by carrying out the transaction. The user must hand over all the data to the banks involved and rely on them to execute the transaction correctly. The bank, of course, charges a fee for this service. This is Web2 banking.

In Web3 you can send your transaction via a decentralized blockchain such as the Bitcoin blockchain. This blockchain independently verifies the accuracy of the transaction through the use of mathematics and computing power. Unlike Web2, banks are no longer needed as intermediaries. That also means the user retains control over their data, and since there is no centralized actor making money from the transaction, there are no fees to pay.

In other words, Web3 should return data sovereignty and ownership rights to the user – that's at least the idea.

"The ownership element is the key difference between Web 2.0, the current iteration of the internet, and web3,” said Shaun Heng, vice president and chief of staff at CoinMarketCap.

So What is Blockchain .

Blockchains are made up of blocks that store information. Each block has a unique “hash” that differentiates it from other blocks. These blocks are then connected by a chain in chronological order. The information stored in these blocks is permanent, which makes it a very secure way to complete online transactions.

This is why cryptocurrencies, like Bitcoin, are built on blockchain technology. Blockchain gives cryptocurrencies the platform and security they need to work. These blocks, or records are stored on online servers, which are publicly accessible, but only by you or anyone else who the block has been shared with.

How do They Work Together?

Blockchain serves as the foundation of Web 3.0; Web 3.0 would not be possible without the systems provided by blockchain. The enhanced security and privacy offered with blockchain is something that the developers of Web 3.0 are using to appeal to internet users. Since blockchain is a decentralized system, there is no single point of control that could be easily hacked. For Web 3.0, this means that individual websites and the internet, in general, would be much more secure against attacks. Users would not have to worry about their information being deleted or compromised. Together, Web 3.0 and blockchain will allow for better cryptocurrency trading and mining.

Examples of Web 3.0 Technologies

Examples of companies already using Web 3.0 AI technology include Apple with Siri and Amazon through Alexa. Both companies are using voice-controlled AI to give consumers real-time answers to their questions. Web 3.0 would expand the reach of internet access to everyone at any time. Amazon has also taken steps to integrate smart devices, which fall under the category of Web 3.0, into their Alexa products. With smart devices, a user can communicate with or control multiple devices from their phone or with their voice. But the most talked-about Web 3.0 technology that is already in use is cryptocurrency like Bitcoin.

Now you see that there are differences between web3 and blockchain technology, see you next time , when I talk about distributed ledger technology``

Learning solidity and rust for web 3.0

Mahmud eyitoba bello — Fri, 28 Jan 2022 16:04:03 +0000

Just yesterday , I had a discussion on the projections that are viewed to be the fruit of web 4.0 ,

haven't seen that , you can check it out here

Mahmudsudo.hashnode.dev

So to understand the assertions that my projections in my previous posts might be achieved in web 3.0 itself , I decided to get my hands dirty with solidity and rust and smart contracts which are the foundations of web 3.0, if you wanna try out this path also you can signify in the comments section and let's share ideas .

Since Rust is an intersection between C++ and Java so I can pick up in no time.

I gave myself a duration of 6 weeks due to me having an examination by February ,
See you on the other side.....

What is next after web 3.0 ?

Mahmud eyitoba bello — Fri, 28 Jan 2022 10:40:42 +0000

The Genesis of the web

WEB 1.0 (read-only web)

In the early 90s , Berners Lee started the read-only web also known as web 1.0,which was just a content delivery network (CDN) with one-way traffic.

WEB 2.0 (social web)

Barely two decades later in the fall of 2004 , the social web was introduced ,this is the web 2.0 which promotes web availability,cloud usage and two-way interaction at most with speculations of reaching a level of data security.

WEB 3.0 (semantic web / decentralized web)

Moving on to 2016 , the almighty semantic web was born, with number visions ranging from linked data and block chain development to decentralized systems , this earned it the name "decentralized web". With the few hiccups associated with the semantic web ,web development as we set is projected to undergo serious changes in its offerings and basic understanding.

This brings us to the big rhetoric , What's next after web 3.0 ? Can you guess ?

It is web 4.0

The emotional web / The smart web / The ubiquitous web /

There are numerous projections and predictions on the supposed use case for web 4.0
Ranging from IOT on the web to AI and self learning web to smart web . One thing common to all these predictions is the awkward incitement and use of AI and bots which are already a part of the unity web( web 2.0), this usage of Artificial intelligence would help with search engines on the web and helps in reducing human involvement in the decentralized world of the web . The web hasn't seen such advancement before and this would also incorporate the use of metaverse.
Apart from the IOT , the
emotional neutrality of web 3 is alternated in web 4.0 i.e there is daily emotional support and communication between users and web ,this would also need incorporating different programming languages and different use cases.

Web 4.0 services will be autonomous, proactive, content-exploring, self-learning, collaborative, and content-generating agents based on fully matured semantic and reasoning technologies as well as AI. They will support adaptive content presentation that will use the Web database via an intelligent agent.
Web 4.0 is a new evolution of the Web paradigm based on multiple models, technologies and social relationships. The concept of Web 4.0 is not totally clear and unanimous in literature, because it is composed by several dimensions. In this sense

That sounds huge right, Tune In for more updates......