You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is important to provide discovery of social connections based on data from the ethereum and cosmos networks. This is the essence of the gift - to shift social connections into a content oracle. Usually, people interact with transactions for years, but do not have consolidated information about who their friends are, who their followers are, who follows them. People need this tooling. This is to add a lot of emotions and high-quality social dynamics to interaction with cyb and cyber.
Having a proof of address, we can pull up transaction data into the client and, based on this, draw a conclusion about who the agent is potentially following (the presence of outgoing transfers), who is following him (the presence of incoming transactions), and who are his friends (the presence of incoming and outgoing).
Parsing contract data is difficult computationally and in terms of implementation, so it is necessary to simplify parsing. For starters, it's enough to filter only core token transfers (ETH, ATOM, OSMO, etc.). This greatly simplifies the implementation of parsing.
We have serious limits on the ability to pull data from web3 and cosm. It is necessary to create a continuous scheme in which data will be pulled to the client gradually, requests will not be duplicated, and the mechanism will also work for future transactions.
Parsing algorithm
Request last 42 transactions
Filter out contract calls
Expand data into `external-txs`` table:
- tx
- block
- network
- type (incoming, outgoing)
- address
- amount
- token
Based on this table, make a calculated table potential-community:
- address
- poptential (following, follower, friend)
- external-name (ens, etc.) if exist
- address.moon if exist
- name.moon if exist
Every time the community page opens or the agent clicks on the more button, the current block is checked, the difference from the last saved transaction is pulled in, and if the limit of 42 transactions is not exceeded, transactions are loaded from the most mature block to the latest one.
When it comes to the very first transaction of the agent, an entry is added to the transaction table as a transaction without a hash, with a block number of 0 network and token, so that it can be clearly understood that lookups in the past do not make sense.
Page structure
Groups
Friends - if not display text: Friendship is mutual following
Imaginable friends - if not - do not display
Followers - if not display text:
Imaginable followers - if not do not display
Following
Worth to follow - if not do not display
Fields
name or address
karma or turnover in tokens from the external-txs table
ava if available (do not show anything for external ones)
The text was updated successfully, but these errors were encountered:
Rationale
Parsing algorithm
- tx
- block
- network
- type (incoming, outgoing)
- address
- amount
- token
potential-community
:- address
- poptential (following, follower, friend)
- external-name (ens, etc.) if exist
- address.moon if exist
- name.moon if exist
more
button, the current block is checked, the difference from the last saved transaction is pulled in, and if the limit of 42 transactions is not exceeded, transactions are loaded from the most mature block to the latest one.Page structure
external-txs
tableThe text was updated successfully, but these errors were encountered: