Pre-Dev-Update Thread! Yay! :D

Github is busy today #JustSayin

13 Likes

It’s getting late… Does this mean a long Tech Update is getting polished or is everyone just busy at the Github coalface?

Certainly a lot of action here today MaidSafe · GitHub including in repos that have not featured too frequently recently

2 Likes

One might soon have to stop doing other stuff and come back to play with the SAFE APIs!

10 Likes

Just the man I need. I was looking for the Browser DOM API docs recently and got a 404. Any searches only bring forum posts from ± 2 years ago. Is that still a thing.

1 Like

I think they’ve removed links so just looking back at my old notes I found:

I’ve no idea of the usefulness of that link but it is a start. I think those docs could be generated using the corresponding repo (safe_app_nodejs).

To get the latest safe_nodejs features working I looked in the following places:

  • New data types (rust documentation)
  • safe-nodejs - neon JS bridge for SAFE API (github)
  • JS API:
    • lib.rs - SAFE API nodejs bindings/implementations (Rust) (github)
    • renderer.js - example Using electron on top of neon bridge for SAFE client Rust API (github)

The last two are the most useful for understanding the APIs and how to use them.

You will find some code which works with the new APIs (when they were v0.2.1) in the parts of SafenetworkJS which do authorisation and I think some basic file operations. Look for commits around that period May-Aug 2019 and you’ll find what I updated for the latest APIs. That code is untried for months, but was working with the new APIs at the time.

4 Likes

I thought that all this had been sidelined by breaking code changes and would be re-released after other more pressing priorities had been addressed… Though I would argue that safe_nodejs was a priority itself

1 Like

Much obliged Mr Hughes!

1 Like

Right on que lib.rs is being updated (click to load the diff):

https://github.com/maidsafe/safe-nodejs/pull/73/files#diff-f2031ff43f7358b7acc49d18ad75ab11

6 Likes

Me trying to keep up with github. Slow down :crazy_face:
giphy

17 Likes

“Show me the money!”

https://github.com/maidsafe/safe-transfers/pull/22

25 Likes

Sounds like something from a sci-fi movie!

15 Likes

Additionally, the Rewards module has been stubbed, and the system is with this more or less ready for implementing Farming .

https://github.com/maidsafe/safe-vault/pull/1024

10 Likes

Very hard to understand for a non-techie like me, but it always gets me excited when I see one of guys like you post that another Github was added!

What is still missing for the Fleming according to you Savage?

Thanks!

5 Likes

If we look at the roadmap only 2 items remain.


We know vaults from home are well underway.
Seems like implementing farming is not incredibly far off.
I am personally very excited about where things are…
I am super excited about the next test and think it is going to be pretty awesome.
That said, I have to try very hard to follow also, you should not put too much weight on my opinion :slight_smile:

12 Likes

Thanks Savage!

Maybe one of the developers can confirm?

1 Like

Hey @andreruigrok,

There are many parts in motion and the whole team are working with intense focus on various tasks.

I can confirm that paying for data with the AT2 system, and subsequently the farming, is coming along very nicely. The PR for the messaging refactor that was linked by @Josh above, contains the complete flow for paying for data using AT2 (via the new safe-transfers library), along with several long due updates to the messaging which makes it more aligned to CRDTs and event driven systems in general. (I know, that won’t say much if you’re not into the technical bits, but basically, updating the code to follow along with our recent progress in these areas.)

We have most - maybe everything - we need, in place to implement the flow for the distributed AT2 actor, which is run by a section as opposed to a client. A distributed actor run by a section, is essentially the section funds, the money held by a section to pay nodes for contributing their storage to the network. It can only be paid out when a quorum of Elders agree to do so.

We will see much more explanations on all of this soon after we’ve gotten something functional enough for all of you to try it out :slight_smile: .

31 Likes

Looks like the safe-farming crate has been worked on since mid-May

https://crates.io/crates/safe-farming

15 Likes

Thanks a lot for your thorough explanation, really appreciate all the hard work you are doing!

8 Likes

You got me really excited with your first sentence and then it turned into gobbledegook tech speak.

Keep up the hard work you guys. We are all plugging for you

5 Likes

There’s a disturbance in the force…

https://github.com/maidsafe/safe-client-libs/pull/1226

17 Likes