Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Sameroom
    @sameroom-bot
    <Sameroom> I've connected 1 new room _#bluzelle_opensource (Bluzelle)_ on Slack. See map
    amastracci
    @amastracci
    :point_up: Connecting our internal slack to gitter :)
    Sameroom
    @sameroom-bot
    [Isabel Scroggin, Bluzelle] Hello world!
    [Richard Nistuk, Bluzelle] I refuse to type “Hello, world!”
    [Richard Nistuk, Bluzelle] shit
    isabelsavannah
    @isabelsavannah
    Awh, come on. Hello world is tradition and good luck ;)
    amastracci
    @amastracci
    @weininghu1012 @wlwanpan @lotharthesavior We will be releasing some client changes for pubsub and PBFT in the coming weeks. I'd like to schedule some time with you 3 to go over changes necessary for our PHP, Python and Ruby SDKs to support.
    Colin Charles
    @byte
    @amastracci these changes, are they also documented? And of course the APIs versioned?
    amastracci
    @amastracci
    @byte These changes are not in production and documentation is coming closer to the release. The goal here is to review the intended changes with our open source team. API is versioned to the swarmdb application version and as of right now there is now implied forwards or backward compatibility. Let me know if you have any further questions.
    Colin Charles
    @byte
    thanks @amastracci
    Warren
    @wlwanpan
    @amastracci Sure, just keep me up to date sometime next week.
    amastracci
    @amastracci
    @wlwanpan @lotharthesavior @weininghu1012 I am putting together a meeting for us to discuss the new wire protocol on Wednesday Nov 7th at 2pm. https://meet.google.com/bnw-moed-dvg.
    amastracci
    @amastracci
    @wlwanpan @lotharthesavior @weininghu1012 A reminder that I would like to meet everyone today at 2pm PST
    amastracci
    @amastracci
    @wlwanpan @lotharthesavior @weininghu1012 Monty and I are on the call. Please join if you can.
    Warren
    @wlwanpan
    @amastracci Sorry couldnt make it today. Are you planning another one soon (preferably during lunch time / weekends) ?
    weininghu1012
    @weininghu1012
    Same request regarding the call
    amastracci
    @amastracci
    @weininghu1012 @weininghu1012 How about noon PST on Friday?
    weininghu1012
    @weininghu1012
    Hmm, do you mind make it during the weekends because that’s in my working hours? Thank you very much!
    Colin Charles
    @byte
    did the wire protocol communication eventually happen? did it get documented?
    Warren
    @wlwanpan
    As of date no. Awaiting @amastracci to schedule another one but its a bit hard to sync during work hours.
    amastracci
    @amastracci
    Happy New Year! @wlwanpan @weininghu1012 @lotharthesavior My apologies for the lack of interaction leading up to the Bernoulli release we have had a lot on our plate internally. I would be very interested in hosting the forum for client library updates either this weekend or the next depending on your availability. Let me know what works best.
    amastracci
    @amastracci
    Hi folks. @wlwanpan @weininghu1012 @lotharthesavior let me know if the weekend after this week would work for a client library forum. We would also like your feedback on our OSS processes.
    Warren
    @wlwanpan
    No worries @amastracci the Bernoulli update was pretty beefy. This sunday or the next work great for me :)
    amastracci
    @amastracci
    @wlwanpan I am going to commit to next week. I'll send out the invite to all interested.
    Warren
    @wlwanpan
    Alright no problem.
    amastracci
    @amastracci
    @/all I am confirming a Bernoulli/Curie client summit for Sunday the 27th at 5:30PM PST
    Agenda will be: 1. Introduction to Bernoulli feature set 2. Discussion around upgrades to supported languages 3. What's next for Curie.
    Monty Thibault
    @MontyThibault
    @/all Here is the updated version of the client development guide for the Bernoulli release.
    Warren
    @wlwanpan
    Awesome 👍
    Warren
    @wlwanpan
    Question: What is the use case of the field "point_of_contact" in "database_header" in database.proto ?
    @MontyThibault
    isabelsavannah
    @isabelsavannah
    @wlwanpan It's internal. It identifies the node that the client would like the replies sent to so that they may be collated and forwarded to the client.
    Monty Thibault
    @MontyThibault
    @wlwanpan My mistake, I linked to the devel branch of the proto files when I should have linked to the master branch. The point_of_contact field does not appear in the Bernoulli release.
    Warren
    @wlwanpan
    @isabelsavannah Thanks for the clarification.
    @MontyThibault Ah gotcha, no worries :)
    Subhasis Banik
    @subhasisbanik
    Any docs to build a private network ?
    Warren
    @wlwanpan

    Hello @MontyThibault, I have a few questions concerning the signature generation (layer 2, step 5):

    i) The second argument of signature is payloadCase. Could you clarify what it is ? I cannot find it in the proto message (https://github.com/wlwanpan/bluzelle-go/blob/master/cproto/bluzelle.pb.go) or figure out the difference between payload and
    payloadCase.

    ii) For step 5 (Convert this string to binary with ascii as the encoding): Did you mean convert to bytes / byte array, not binary correct?

    Thank you.

    Matt
    @matteyu

    hey @wlwanpan ! Maybe I can help out with your questions because I had to go through this with the C# client.

    i) payloadCase indicates the type of payload. However, in your "deterministic string", you need to provide the value of it. For the C# client, i had to do a switch case.
    So for example: if payload type = database_msg, then payloadcase in the string will be 10. For reference, have a look at https://github.com/bluzelle/swarmDB/blob/devel/proto/bluzelle.proto

    ii) This would be byte array i believe but @MontyThibault can verify. In C#, I had to convert it to ByteString which was a google protobuf specific type. But it's essentially a sequence of immutable bytes (byte array i guess to put it simply)

    Monty Thibault
    @MontyThibault

    Thanks @matteyu

    ii) bytes/binary should be the same thing. The result is not embedded anywhere in protobuf, but instead signed with ECDSA, and it's the signature that's embedded.

    most programming languages use abstractions that address binary data as groups of bytes, so yeah
    isabelsavannah
    @isabelsavannah
    @subhasisbanik it's really just a matter of running several daemon instances and giving them an appropriate peers list. My script for that is here - https://github.com/isabelsavannah/swarmdb-local/blob/master/scripts/run-swarm.rb
    Warren
    @wlwanpan
    @matteyu @MontyThibault thanks for the quick response. Got it, the payloadCase is the proto index of the payload type. Things are clearer now thanks :)
    Yarco Hayduk
    @yarco
    Hey Warren, nice to meet you. I'm one of the people responsible for providing Bluzelle client integration in different languages
    Please let me know if you have any questions. I've been told that you are interested in Golang support, is that correct?
    amastracci
    @amastracci
    @wlwanpan meet @yarco who is working on the internal python <> bzapi wrapper. Let's start the discussion on what it would take to add Go or Ruby to our supported wrapped languages.
    Warren
    @wlwanpan
    Hello @yarco nice to meet you as well :) Sure will do, correct, I’ve been working on the golang client and im stuck on the signing/encoding part (crypto layer). After signing the payload and sending it through the socket. I keep hitting the error "close 1007 (invalid payload data) “ even though the payload does not contain non-utf8 data. Could you provide some examples of the raw data at the signing + encoding step ? That would be really helpful thank you!
    Sameroom
    @sameroom-bot
    <Sameroom> I've connected 1 new room _#bluzelle_opensource (Bluzelle)_ on Slack. See map
    Neeraj Murarka
    @njmurarka
    Hello everyone!
    Sameroom
    @sameroom-bot
    [Richard Nistuk, Bluzelle] Helloo