Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Heyo Gitcoiners! With an entire city of hackers, coders and blockchain innovators relocated on our platform, the atmosphere is just buzzing with crea…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
One of the biggest problem with IPFS it's DHT scaling. It's a huge problem which we hope will be solved in a couple of next years thanks to an awesome and fast-growing community. Cyber solves discoverability of content from another side with the assumption that WHO linked also PIN content to their local IPFS node which inited with the same keys as account keys. That allows one-hop discoverability of content by design following with this assumption.
_Note_: There is no bip39 and ed25519 support by default in go-ipfs and js-ipfs for a node initialization, PR for this will be proposed by cyber•Congress later this year.
Search endpoint should also return **the node field** to each link in the search response. The node field provides the IPFS node address. Node hash converted by multihash from account's address pubkey.
_Note_: We save account which adds given link to the state. That prevents spam and abusing of rank.
This information saved as the associated account number.
The node field - IDFromPublicKey(pubkey). Check https://github.com/libp2p/go-libp2p-core/blob/master/peer/peer.go
+ "nodes": ["12D3KooWK4Jgc6FrH5aCzBZETzL1MtVXvmjdpxxDheUhd5d71ek9"]
Note: links saved with account number which create cyberlink
1. Upgrade link's index with accounts numbers
2. Setup index of account-account_number
3. Setup hooks for index updates with new accounts
4. Upgraded RPC endpoint and given struct to return/encode the accounts which linked given CIDs
5. Extra - take pubkey for a given account and convert them with multihash to IPFS node ID.
For 5 will be the extra bounty for done.
**Definition of Done:**
For each link in search response via /search endpoint, a daemon should return accounts/IPFS node addresses(*) which associated with the given accounts which linked given CIDs in a search response
At the end of our setup dev env documentation you will find needed information about how to linking and check search responses
Please, provide your PR request with branch 352-link-node to branch 0.1.5
PR discussion will be started and processed in 2-3 days, payment will be released after merging.
**Cosmos-SDK dosc and architecture:**