MashMesh
Web3 multidimensional relationship explorer makes entities and relationships in KNN3's Knowledge Graph accessible
Last updated
Web3 multidimensional relationship explorer makes entities and relationships in KNN3's Knowledge Graph accessible
Last updated
MashMesh is a Web3 multidimensional relationship explorer powered by KNN3 GraphX Protocol, which makes the entities and relationships in KNN3’s Knowledge Graph visual and operable without programming.
When you first visit the page of MashMesh, you can see the search box with checkboxes related to different fields. To improve the search efficiency, you may choose desired fields before your searching.
Check the following table for more information about searching.
Avatar (Next.id)
Avatar
Avatar ID (0x…)
Twitter Account
Avatar
Twitter Handle
Address (EOA & Multisig)
Address
Address (0x…)
Event (POAP)
Event
Event Name (ID)
Token
Token
Token Name / Contract Address
NFT
NFT
Collection Name / Contract Address
Organization (Snapshot Space)
Space
Space Name (ID)
ENS Domain (Owner Address)
Domain
ENS Name
.bit Domain
Domain
.bit Name
Lens Profile
Lens
Lens Handle (.lens)
When the search succeeds, the entity will be shown in the center of the screen, and its detailed information will be displayed on the left.
With the entities as the vertices, the relationships between them are displayed as the directed edges and the source and target of which are shown below.
Address
Source ⇆Target
Source
Source
Source
Source
Source
Source
Lens Profile
Target
Target
-
-
-
-
Token
-
-
Target
-
-
-
NFT
-
-
Target
-
-
-
Event
-
-
-
Target
-
-
Space
-
-
-
-
Target
-
Bits
-
-
-
-
-
Target
Avatar
-
-
-
-
-
Target
Twitter Account
-
-
-
-
-
Source
KNN3 aggregates the following relationships from RSS3 and Cyberconnect. In Mashmesh, the following relationships are turned into directed edges from the follower to the following address.
To better operate the graph and explore the web3 relationship network, we hope you are fully familiar with the following features.
You can right-click on the vertex to find Expand in the context menu.
And then you can expand any types of entities related to the vertex.
For optimal performance, the expanded entities are paging queried, you can keep expanding until it's fully expanded.