Xennet / xennet-client

0 stars 0 forks source link

Development team meeting - 3.1.2015 - Zennet backend pub/pro/wallet/OS #4

Open arielnux opened 9 years ago

arielnux commented 9 years ago

hey all, If we have further comments please edit the document as follow all the best Ariel

we write here our meeting's highlights:

  1. operating system variables - which cgroup variables
  2. operating system variables - cgroup variables demo vector for specifications and rates.
  3. Linux - Send/Receive with Zennet OS (transaction, etc.)
  4. wallet - multi signature - input and output coordination
  5. wallet - pub. public key - input and output coordination
  6. wallet - pro. public key - input and output coordination
  7. wallet/OS - Zennet contract directory
  8. wallet - transaction class.
  9. wallet - refund transactions and updated transactions 10.wallet - time lock for each transaction 11.wallet - digital signatures for pro. and pub. after agreed

Types of clients known to use: SPV - https://en.bitcoin.it/wiki/Scalability#Simplified_payment_verification full node (Bitcoin B/Cli) - keeps all the previous data that was mentioned by us in the meeting.

Topics we decided about them:

  1. RPC (manual) - Alon M. will send a "manual" for the client RPC(input/output) in the upcoming days.
  2. RPC (layer) - sending a string input to EXE. and receiving a jason.
  3. Ann (process)- publisher is sending an Ann to the block chain, IP address and a string(spec), which the provider is receiving and filter those(Ann), as required.
  4. pub/pro (code) - at this development point pub/pro must communicate through cin/cout

Participants :

Ohad Asor Amnon Dafni Ravit Halmut Alon Muroch Ariel Formanovski‏

yonatanomer commented 9 years ago

Hi, could you update please regarding the EXE receiving JSON? I think this is what I started to implement in xennet-os\frontend-stub\ - there is also a client html sample here: https://github.com/Xennet/xennet-os/tree/master/frontend-stub

arielnux commented 9 years ago

hey Yonatan, Alon Muroch‏ will send a manual for RPC layer in a few days. Then we can check if this is the code required for us when it comes to RPC. All the best, A.

alonmuroch commented 9 years ago

Hey Guys, This is a link to all the RPC calls the bitcoin client has https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

yonatanomer commented 9 years ago

could you please explain what is the 'EXE' here: _"2. RPC (layer) - sending an string input to EXE._"

Is this executable running on the backend or the dedicated browser shipped with zennet (Amnon and Ohad mentioned such browser)?

On Sun, Jan 4, 2015 at 5:05 PM, arielnux notifications@github.com wrote:

hey Yonatan, Alon Muroch‏ will send a manual for RPC layer in a few days. Then we can check if this is the code required for us when it comes to RPC. All the best, A.

— Reply to this email directly or view it on GitHub https://github.com/Xennet/xennet-client/issues/4#issuecomment-68637822.

yonatanomer commented 9 years ago

So you talk only about RPC with the wallet, correct? Will this be exposed directly to the provider/publisher in the front end? What is 'EXE', where is it running?

On Sun, Jan 4, 2015 at 5:40 PM, Alon Muroch notifications@github.com wrote:

Hey Guys, This is a link to all the RPC calls the bitcoin client has https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

— Reply to this email directly or view it on GitHub https://github.com/Xennet/xennet-client/issues/4#issuecomment-68639113.

alonmuroch commented 9 years ago

Yesterday we talked about hacking a quick solution for the development, essentially running a daemon client that can provide the wallet functionality we need (via RPC calls). Later we can integrate the wallet directly, as a library, directly into the Zennet client.

We can use bitcoind to execute the RPC calls or integrate an RPC library to the Zennet client.

yonatanomer commented 9 years ago

I see. thanks.

On Sun, Jan 4, 2015 at 6:45 PM, Alon Muroch notifications@github.com wrote:

Yesterday we talked about hacking a quick solution for the development, essentially running a daemon client that can provide the wallet functionality we need (via RPC calls). Later we can integrate the wallet directly, as a library, directly into the Zennet client.

We can use bitcoind to execute the RPC calls or integrate an RPC library to the Zennet client.

— Reply to this email directly or view it on GitHub https://github.com/Xennet/xennet-client/issues/4#issuecomment-68641525.