Workers Auto Approve
Return IPFS node address for each link in a search response
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:**
Setup your profile
Tell us a little about you:
No results found for
Type to search skills..
Required [[totalcharacter]] / 240
Are you currently looking for work?
[[ option.string ]]
Setup your profile
Our tools are based on the principles of earn (💰), learn (📖), and meet (💬).
Select the ones you are interested in. You can change it later in your settings.
I'm also an organization manager looking for a great community.
Enable your organization profile
Gitcoin products can help grow community around your brand. Create your tribe, events, and incentivize your community with bounties. Announce new and upcoming events using townsquare. Find top-quality hackers and fund them to work with you on a grant.
These are the organizations you own. If you don't see your organization here please be sure that information is public on your GitHub profile. Gitcoin will sync this information for you.
Select the products you are interested in:
Out of the box you will receive Tribes Lite for your organization. Please provide us with a contact email: