The document discusses the evolution of the web from Web 1.0 to Web 3.0, emphasizing the transition from centralized systems to a decentralized web model that enhances user ownership and data privacy through blockchain technology. It explores the drawbacks of Web 2.0, such as the reliance on intermediaries, data breaches, and concentrated control over user data, and introduces Web 3.0 as a solution to these problems. The document highlights key concepts associated with decentralized applications (dApps) and technologies, impacting various sectors including content creation and data management.

1. Web 3.0
The beginning of the new era…
• Lipsa Chhotray
• O.P. Pachoriya
• Rahul Mohan

2. What’s This Buzz About Web3!!!
2
DECENTRALISATION

3. What Are We Going To Cover!
• Understanding the evolution of the web.
• Web 3 architecture
• Getting started as a Web 3 developer
3

4. A Brief History Of The
“Web”
A journey from towards
decentralization
4

5. Heads Up! Web Is Not Internet
● Web is an information system built on top of the
internet.
VS
● Internet is a network of networks which makes all the
information of web accessible to every corner of the
world.
5

6. Evolution of Web
6
Internet
Web 1.0
Web 2.0
Web 3
Semantic
Web (AKA
Web 3.0 )
1969 1991 1999 2004 2014

7. Why We Needed Internet?
7
● Mainframe computers were huge and
expensive.
● They ran one specific task at a time.
● For an experiment which required
multiple tasks more than one computer
was required.

8. Why We Needed Internet?
So, the solution to that…
• Connecting multiple computers to the same network.
• Getting those to speak the same language or a common
protocol to communicate with one another.
8

9. The Advent Of The Internet
9
• Before the era of internet WAN (Wide Area Network)
existed in 1950s
• Limitations with WAN
• Were constrained both to small areas
• Each machine spoke it's own language which made it impossible for it to communicate with
other machines
• Data was sent via the telephone line using a method called "Circuit switching" This method
worked just fine for phone calls but was was very inefficient for computers and the Internet.
• Using this method you could only send data as a full packet, that is data sent over the
network, and only to one computer at a time. It was common for information to get lost and
to have to re-start the whole procedure from the beginning. It was time consuming,
ineffective, and costly.
• An attack on the telephone system would destroy the whole communication system

10. 10
The solution to that problem was packet switching
It was a simple and efficient method of transferring data.
Instead of sending data as one big stream, it cuts it up
into pieces.
Then it breaks down the packets of information into
blocks and forwards them as fast as possible and in as
many possible directions, each taking its own different
routes in the network, until they reach their destination.
Once there, they are re-assembled. That's made
possible because each packet has information about the
sender, the destination, and a number. This then allows
the receiver to put them back together in their original
form.
The Advent Of The Internet

11. 11
In 1978 the Transmission Control
Protocol and Internet Protocol were
created, otherwise known as TCP/IP.
The Internet Protocol (IP) makes
locating information possible when
looking among the plethora of machines
available.
The Advent Of The Internet

12. The Advent Of The Internet
12
Without Arpa, the internet wouldn’t exist!

13. Evolution of Web
13
Internet
Web 1.0
1969 1991

14. Why We Needed Web?
● References to other documents
were in the form of documents
● It was a tedious task to search
the documents via citations.
14

15. Why We Needed Web?
15
Hyperlink!!!

16. Web 1.0: The Era Of Web Hence Begins
● The code for the World
Wide Web was written by
Tim Berners-Lee, based on
his proposal from the year
before, along with the
standards for HTML, HTTP,
and URLs in 1991.
● This was the World’s First
Web Page
16

17. Web 1.0: The Era Of Web Hence Begins
• The first stage in the WWW, which only offers
people one-way communication such as reading the
contents. Hence, it was called “Read only web”.
• The information was static.
• Client could only access info presented in servers
but could not interact with the server.
17

18. Evolution of Web
18
Internet
Web 1.0
Web 2.0
1969 1991 2004

19. Web 2.0: The Onset of Centralization
• The term Web 2.0, labeled by Tom O 'Reilly in 2004 refers to a second generation of
models of Web pages called “Read Write Web”
• Web 1.0, has a more static navigation model, this new format encourages active
participation.
• It saw advent of the term social media.
• It has ad based revenue model. Where the user is provided with free softwares to use
like social media but in the hindsight the user information is traded with the ad agencies
to churn out huge amount of revenue.
• The data and content are centralized in a small group of companies sometimes referred
to as "Big Tech".
19

20. Okay… They Take Our Data… But
Why Do We Care?
What kind of user data floats around in web?
• Basic user info like name, date of birth,location, contact info etc.
(The info we willingly give away)
• Facial Features and voices (collected via snapchat and instagram
filters)
• Valuable intellectual properties like the content we create for blogs,
music etc.
Today, this data economy is worth trillions of dollars and fuels
the majority of the web!!
If this is our data, then this begs the question - why don’t we
own it?
20

21. Drawbacks of Web 2.0
Trust Issues And The Dangers Of Middlemen
• To trust a third party we take help of powerful
intermediaries.
• Banks are intermediaries for payments, DNS is an
intermediary between users and websites,
• Google is an intermediary for information,
• Facebook is an intermediary for community,
• YouTube and Spotify are intermediaries for content
distribution, and
• Amazon is an intermediary between consumers and
vendors.
21

22. Issues with Middlemen or Centralization?
• Selling our Data: Intermediary giants like Google, Facebook, and Amazon
collect massive amounts of sensitive information from their users with or
sometimes without our consent and sell it to ad companies.
• Data Breaches: Unsurprisingly, these large data collections are prime targets for
hackers. While these companies utilize many layers of security to keep this data
out of the wrong hands, a quick visit to haveibeenpwned.com will show you that
data breaches are alive and well.
22

23. Issues with Middlemen or Centralization?
• Concentrated Control: On top of storing data, more and more of the web itself is being stored
and served up by a small number of companies. Instead of businesses buying and maintaining
their own web servers and databases, many simply rent another company’s hardware. This is
what is known as cloud computing the delivery of content and computational resources over the
internet. The potential issues here are
• The power outages taking video streaming services offline for a few hours,
• The increased control that these providers are gaining. If the current concerns surrounding
big tech are anything to go off of, allowing those companies to own, store, and manage
even larger swaths of the web may be a path we want to rethink.
• Censorship: In a similar vein, social media sites and content platforms have turned into
battlegrounds for free speech, leaving it to CEOs and shareholders to weigh in on increasingly
complex sociopolitical issues. To respond to this, lawmakers are forced to choose between
meddling in private businesses or making those businesses accountable for censorship on their
platforms.
23

24. Issues with Middlemen or Centralization?
Concentrated Value:
● Needless to say, all of this data and control
has enabled today’s internet giants to a
mass some pretty incredible market caps.
While some of this wealth is the result of
ingenuity and breakthroughs in technology,
a large portion of it actually comes from the
creations of users.
● YouTube, TikTok, Spotify, Instagram - all of
these platforms simply act as
intermediaries between content creators
and consumers. That in and of itself is not
an issue.
● The issue becomes evident when we see
these platforms taking the lion’s share of
the value their users create.
24

25. Evolution of Web
25
Internet
Web 1.0
Web 2.0
Web 3
Semantic
Web (AKA
Web 3.0 )
1969 1991 1999 2004 2014

26. Heads up! Once again!
Semantic Web (AKA web 3.0) is
not the same as web3
26

27. A Quick Detour on Semantic Web
• Problem of data in silos:
• Our data is interconnected but it is in silos. For example
we might have same data in linkedIn and facebook but
when we updates out job status in linkedIn, facebook
does not automatically know about that.
• Redundant data entries which is difficult to maintain.
• While web 1.0 proposed to establish links between
documents while semantic web proposed to
establish link between facts or data points.
27

28. Web3: Say Hi, To Decentralization!
• The decentralized web, or Web3, is a digital world
that is owned and governed by its users.
• It will provide increased data security, scalability,
and privacy for users and combat the influence of
large technology companies.
• The building block of web3 are “blockchain”.
28

29. What Is A Blockchain?
● Blockchain is a decentralized, distributed,
immutable ledger.
○ Decentralized: It is accessible to anyone
in the network. It operates in a peer-to-peer
network
○ Distributed: As opposed to centralized
data. The data stored over blockchain is
shared across all the nodes.
○ Immutable: Once a data is entered into a
blockchain it is impossible to change it.
● It was first adopted by Satoshi Nakamoto (an
unnamed superhero types) in 2009 to create
the first digital cryptocurrency bitcoin.
29

30. How Does Blockchain Work?
30
A block in a blockchain contains:
● Data
○ The data specific to a blockchain. For eg bitcoin
blockchain stores the details about the
transaction like sender receiver and the amount.
● Hash
○ An output of a cryptographic function with data
as input.
○ With any change in data the hash value
changes.
● Hash to the previous block

31. How Does Blockchain Work?
31

32. Immutable,Secure… How?
32
It is possible to tamper with one block and calculate
the hash of all the further blocks using powerful
computers.

33. Immutable,Secure… How?
33
There are two solutions to that:
• Proof of work:
• It is a mechanism to make the hashes harder to
generate.So that they would literally be mined out.
• Typically by specifying that hashes should begin with
a set number of zeros.
• For bitcoin it proof of work takes 10 minutes.
• Peer to peer network
• Each new block is added to all the nodes in a peer to
peer network.

34. How Web3 Solves All The Problems?
An antidote to data centralization and single point of
failure
• Blockchain effectively creates a giant shared computer,
with individual devices, called nodes, replacing data
centers and server farms.
• This removes these single points of failure, as well as
the potential for a centralized figure to assert control
over the network.
34

35. How Web3 Solves All The Problems?
Middlemen! Bye Bye!
• Most importantly, blockchain bakes a level of trust into the system itself. This is
done through the use of cryptographic keys, which allow individuals to prove
their identity without handing over sensitive information. By retaining ownership
over their data, Web3 users enjoy a level of security, privacy, and data portability
that is simply not possible on today’s centralized web.
• This ability of blockchain to create trust between individuals is fundamental to the
decentralized web. By building trust into the web itself, Web3 removes the need
for intermediary figures along with the reliance on misaligned economic streams
like ad revenue.
35

36. How Web3 Solves All The
Problems?
Owning Back Our Data
On Web3, you log onto the web itself, not individual sites
and platforms. Instead of handing over data and
personal information to create separate accounts all
over the web, that data and info is all held in your wallet.
Think of your Web3 wallet like a real world wallet
combined with a real world passport - it contains your
personally identifying information as well as your digital
assets like cryptocurrencies and NFTs.
Your wallet is your master account to all of the
decentralized web, allowing you to prove your identity to
any website or application you interact with. Trust is
formed, no data collection required.
36

37. How Web3 Solves All The Problems?
HTTP
37
Our current web stores content on
centralized servers. Every time a user
wants to access a specific piece of
content, they have to send a request to
that server, and the server sends the
piece of content back to the user. This is
known as location based addressing.
IPFS
On IPFS, though, any device can store and serve the web’s
content. Every piece of content on IPFS is then given its
own unique code, called a hash. Instead of retrieving
content from a specific server, users are able to locate a
piece of content itself by sending a request for its hash.
The network then serves up the content from the nearest
node, regardless of where it originally came from. By
leveraging a distributed network of hosts and servers,
IPFS is able to remove the single points of failure and
potential for censorship that come along with centralized
web servers.
CommunityControl vs Centralized Servers

38. How Web3 Solves All The Problems?
Community Value
• The decentralized applications, or dapps, are open-source and executed on the blockchain.
• Dapps like Audius, a decentralized music streaming platform, put content creators directly in touch with
their audience and remove the need for middlemen almost entirely. While the Audius team created the
platform, they are no longer its sole operators or beneficiaries. Audius lives on the blockchain and is
owned and governed by its users through the platform’s native cryptocurrency, AUDIO.
• The ability to pay creators directly for their work and give them a say in the platforms they use is a
massive shift in the creative world. This is especially true of the music industry, where the majority of
revenue and decision making power still go to middlemen. This same method of ownership and value
distribution can be applied to any application — it won’t be long before we start seeing decentralized
alternatives to platforms like YouTube and Instagram gaining traction.
38

39. Web 2.0
39

40. Meet my friend,
Mr. Politician
40

41. Web 3.0 Arch / Politician view
41
Ethereum
Blockchain
(Data Points)
Ethereum Virtual
Machine
(Govt
Departments)
Smart
Contracts
(Election
Manifesto)
Front End
(Party Office /
Banner)
Signer
(Election
Symbol)
Provider
(Media)
Interplanetary
File System
(Personal
Assistant)

42. Web 3.0 Arch / Developer view
• Signer
• But if you want to write to the state, there’s still one more thing you need to do before you
can submit the transaction to the blockchain— “sign” the transaction using your private
key.
• Metamask is a tool that makes it easy for applications to handle key management and
transaction signing
• Provider
• The nodes that you connect with when you need to interact with the blockchain
• Set up your own node which runs the Ethereum blockchain software
• Use nodes provided by third-party services like Infura, Alchemy, and Quicknode
• Smart Contract
• A program that runs on the Ethereum blockchain
• Defines the logic behind the state changes happening on the blockchain
• Written in high-level languages, such as Solidity or Vyper.
• EVM
• Executes the logic defined in the smart contracts and processes the state changes that
happen on this globally accessible state machine.
• Compile the high-level language down into bytecode, which the EVM can then execute
42

43. Web 3.0 Arch / Developer view
• IPFS or SWARN
• IPFS is a distributed file system for storing and accessing data. So, rather than storing
data in a centralized database, the IPFS system distributes and stores the data in a peer-
to-peer network. This makes it easy for you to retrieve it when you need to
• IPFS also has an incentive layer known as “Filecoin.” This layer incentivizes nodes
around the world to store and retrieve this data.
• Swarm is similar in that it’s a decentralized storage network, but there’s one notable
difference. While Filecoin is a separate system, Swarm’s incentive system is built-in and
enforced through smart contracts on the Ethereum blockchain for storing and retrieving
data
• Block Chain
• A state machine that anyone in the world can access and write to.
• Not owned by any single entity, but collectively by everyone in the network.
• JSON-RPC
• A uniform set of methods when frontend applications want to interact with the blockchain.
• it’s a stateless, lightweight remote procedure call (RPC) protocol that defines several data
structures and the rules for their processing. It’s transport-agnostic, so the concepts can
be used within the same process, over sockets, over HTTP, or in many various message-
passing environments.
43

44. Web 3.0 Scaling
44
Source : https://etherscan.io/charts

45. Web 3.0 Scaling
• Ethereum doesn’t scale - at least, not yet.
• Building a DApp on Ethereum with high gas fees
and full blocks leads to a very bad UX.
• Instead of executing transactions on the main
blockchain, Polygon has “sidechains” that process
and execute transactions. A sidechain is a
secondary blockchain that interfaces with the main
chain. Every so often, the sidechain submits an
aggregation of its recent blocks back to the
primary chain.
• Other Solutions like
• Optimistic rollups
• ZK-rollups
45

46. Web 3.0 Scaling
46

47. So have you seen web 3 ?
Rahul Mohan

48. Well it’s complicated
48
• What can I do to start building a APP or Dapp on the block chain
• Wait we don’t need a data base ?
• Wait where will all my Instagram stories go ? Will I be hacked ?
• Wait what is Meta Mask ?
• And EVM ? What is that !!!

49. A little about myself
Twitter:
https://twitter.com/RealRahulMohan
What do we do here at Talentica ?
49

50. A real life example
• Insurance company
• People pay money
• There is a flood
• People who are effected get money
50

51. The web3 tech stack
• Auth – metamask
• Frontend – React/JS/Web3.js
• Backend/Backend language- Solidity
[hardhat/Truffle] [Open Zepline]
• Oracles
• IPFS
51

52. The Frontend
• Getting to know meta mask.
• Getting to know what web3 is.
52

53. The backend
• What is a smart contract ?
• What is the EVM ? (Ethereum Virtual machine)
• What is gas fees ?
53

54. The Oracle
• Who/what is the Oracle ?
54

55. IPFS
• We get YouTube on Mars ?
• Interplanetary file system ?
• Can’t we just store it on the blockchain ?
55

56. Queries
56

57. References
https://www.webfx.com/blog/web-design/the-history-of-the-internet-in-a-nutshell/
https://www.freecodecamp.org/news/brief-history-of-the-internet/
https://unstoppabledomains.com/blog/web3-101-part-ii-your-data-on-web2
https://unstoppabledomains.com/blog/web3-101-part-iii-the-decentralized-web
https://www.youtube.com/watch?v=V6BR9DrmUQA
https://ethereum.org/en/developers/docs/web2-vs-web3/
https://www.youtube.com/watch?v=SSo_EIwHSd4
https://www.preethikasireddy.com/post/the-architecture-of-a-web-3-0-application#Story
https://www.singlegrain.com/web3/web-3-0/
57

58. Thank You
58