-
-
Notifications
You must be signed in to change notification settings - Fork 7
Roadmap #1
Comments
Moving up ^^ |
I like what I see happening over here. Keep up the good work, gentlemen! |
updated rpc->ipfs TODOs |
@kumavis what is the plan for the smart contract code? Currently, the accounts in the state trie only store the Geth at least, just uses this Are we missing the IPLD codec for this element? |
@herman correct, we dont have a codec for it -- we should consider making one i've been using the raw binary codec, but turns out that was actually not supported in js-ipfs and so I created a PR for it -- for sure about go-ipfs |
got stalled, i need to get back on it |
@kumavis Will do the PR in |
@hermanjunge |
Asked by @diasdavid to make a write up on my status to-date. Did it here ipfs/notes#261 |
@kumavis just missing ipld/js-ipld#90, need your input there. All the others have been shipped. @hermanjunge thank you for the write up! ❤️ ipfs/notes#261 |
thanks/ here's the remainders |
|
udapp-ipfs is live! |
published: |
|
exists, but super crashy and not fully QA'd |
Did some editing to the first comment. Divided the goals into |
devp2p -> libp2p bridge in Go Language (a.k.a. "Hot Importer")
|
From ipfs/go-ipld-eth-import#9 (comment)
So, I've reading code starting from here and here, and I agree. Also, I learned about transports here. seemed that I was having all nomenclatures wrong in my head: We didn't want to do a different wire protocol, only a transport. I may then want to build a transport library called
That should suffice to have an example like this running, getting peers and their ethereum data. What are your thoughts @jwasinger? |
This looks good @hermanjunge . As we discussed, I will be working on writing the javascript implementation of the rlpx transport |
@hermanjunge that's the approach I was suggesting earlier, it seems tho that according to @whyrusleeping, this might end up being more involved than necessary. An alternative seems to be running both devp2p and libp2p stacks in the client and doing the bridging that way, IIUC. Just leaving this here, for future reference:
|
@hermanjunge you were looking into adding postgres support to go-ethereum via https://github.com/ethereum/go-ethereum/tree/master/ethdb Why was that strategy abandoned and this one adopted? It seems like support Thanks. |
Hi @AFDudley
The strategy of implementing RedisDB or PostgreSQL as storages in https://github.com/ethereum/go-ethereum/tree/master/ethdb was abandoned for lack of resources at that time. Now we have the capacity to commit in the area of blockchain storage. There are several ways to skin a cat. The approach you mention is correct: Instead of making a The |
break down of rpc methods and node requirements (updated)
|
Yet another writeup, older, but wiser. (they say) |
A more polished writeup: Moving to a problem of maintaining a distributed ethereum snapshot database on js-ipfs browser peers |
Moving everything here musteka-la/mustekala#2 |
CLIENT
BEACONS
BUCKETS
Next steps ipfs/go-ipld-eth#1 (comment)
Roadmap #1 (comment)
OTHER
indexing / lookup
messaging
testing
monitoring
products and devices
The text was updated successfully, but these errors were encountered: