rjones (Sun, 17 Jun 2018 16:28:43 GMT):
amundson

rjones (Sun, 17 Jun 2018 16:28:51 GMT):
Has left the channel.

zac (Tue, 19 Jun 2018 20:29:35 GMT):
Has joined the channel.

zac (Tue, 19 Jun 2018 20:39:11 GMT):
@jsmitchell @kelly_ Approval to put this RFC into FCP? https://github.com/hyperledger/sawtooth-rfcs/pull/13

jsmitchell (Tue, 19 Jun 2018 20:39:11 GMT):
Has joined the channel.

kelly_ (Tue, 19 Jun 2018 20:39:11 GMT):
Has joined the channel.

jsmitchell (Tue, 19 Jun 2018 20:39:40 GMT):
approved

Mahesh-Raj (Wed, 20 Jun 2018 09:46:10 GMT):
Has joined the channel.

tungdt_socoboy (Thu, 21 Jun 2018 11:46:48 GMT):
Has joined the channel.

rootDistress (Wed, 27 Jun 2018 07:24:27 GMT):
Has joined the channel.

mengan (Wed, 27 Jun 2018 12:04:42 GMT):
Has joined the channel.

kelly_ (Thu, 28 Jun 2018 14:53:05 GMT):
approved, sorry for the delay! I didn't even know this chat channel existed :/

zac (Thu, 28 Jun 2018 14:54:52 GMT):
Approval on PR to make it official?

kelly_ (Thu, 28 Jun 2018 14:59:01 GMT):
yup

kelly_ (Thu, 28 Jun 2018 14:59:20 GMT):
I clicked the little check box near my name, do you want me to comment as well?

kelly_ (Thu, 28 Jun 2018 15:00:36 GMT):
ah nevermind, i actually did a review and approval

kelly_ (Thu, 28 Jun 2018 15:00:46 GMT):
I didn't see that I had been tagged as a reviewer

kelly_ (Thu, 28 Jun 2018 15:01:03 GMT):
all good :thumbsup:

zac (Thu, 28 Jun 2018 15:32:34 GMT):
thank you thank you

zac (Thu, 28 Jun 2018 16:24:45 GMT):
Data Type RFC has entered the final comment period: https://github.com/hyperledger/sawtooth-rfcs/pull/13

zac (Thu, 12 Jul 2018 14:53:32 GMT):
@kelly_ @jsmitchell @amundson @agunde I am proposing RFC #14 enter Final Comment Period. It is a proposal to remove FishNet and AssetTrack and replace them with a new "universal" client: https://github.com/hyperledger/sawtooth-rfcs/pull/14

agunde (Thu, 12 Jul 2018 14:53:32 GMT):
Has joined the channel.

zac (Thu, 12 Jul 2018 18:19:32 GMT):
ALERT: this proposal has entered FCP! In two weeks it will be merged if there are not substantive changes requested.

kelly_ (Thu, 12 Jul 2018 23:12:59 GMT):
@zac FCP is 1 week per Gov doc

kelly_ (Thu, 12 Jul 2018 23:13:37 GMT):
two weeks is fine with me, just figured i'd let you know it can be expedited if you'd like

zac (Thu, 12 Jul 2018 23:32:26 GMT):
Ah, README says 10 days, which I misread as 10 business days

zac (Thu, 12 Jul 2018 23:32:55 GMT):
I will update the README and the FCP end date

kelly_ (Fri, 13 Jul 2018 19:10:44 GMT):
:thumbsup:

choco_coder (Mon, 16 Jul 2018 19:38:06 GMT):
Has joined the channel.

brettdugan (Tue, 24 Jul 2018 01:02:51 GMT):
Has joined the channel.

zac (Thu, 26 Jul 2018 17:39:25 GMT):
@kelly_ @jsmitchell @amundson @agunde I am proposing that RFC #15 Supply Chain PropertyTypes enter Final Comment Period. Sound good to you guys? https://github.com/hyperledger/sawtooth-rfcs/pull/15

agunde (Thu, 26 Jul 2018 17:40:39 GMT):
sounds good to me

kelly_ (Thu, 26 Jul 2018 17:43:50 GMT):
looks good

amundson (Thu, 26 Jul 2018 20:22:59 GMT):
@zac sounds good

amundson (Thu, 26 Jul 2018 20:23:37 GMT):
@jsmitchell ^ FCP waiting on you

jsmitchell (Thu, 26 Jul 2018 22:08:06 GMT):
approved

harish.drish (Fri, 10 Aug 2018 05:26:35 GMT):
Has joined the channel.

harish.drish (Fri, 10 Aug 2018 05:28:46 GMT):
hello everyone......I have created api to create transactions and all the data is coming from client side with private key to sign the transaction...but i do not want to send private key to api because of security purpose....how this can be done can anyone help me??

zac (Fri, 10 Aug 2018 18:49:35 GMT):
@agunde @jsmitchell @amundson @kelly_ I'm proposing RFC #16, a proposal to create a Supply Chain client SDK move into final comment period: https://github.com/hyperledger/sawtooth-rfcs/pull/16

zac (Fri, 10 Aug 2018 18:49:44 GMT):
Looking for sign offs in particular from James and Kelly

zac (Fri, 10 Aug 2018 18:51:38 GMT):
@harish.drish In supply chain the private key is encrypted before sending it to the API, and that is just a storage convenience. It allows users to log in and sign with their private key on any device. However the API never sees the unencrypted private key, and if you wanted to do away with that convenience, you could just never send it to the API in any form.

harish.drish (Mon, 13 Aug 2018 08:32:20 GMT):
@zac okey thanks for your response

harish.drish (Mon, 13 Aug 2018 09:05:39 GMT):
@zac as I do not post private key to server so I have created a custom node module....so how I can call module on client side...can you help me

harish.drish (Mon, 13 Aug 2018 09:54:37 GMT):
@zac is it possible to sign transaction on browser and then send to the server...... what is the best way to do this

zac (Mon, 13 Aug 2018 11:51:36 GMT):
Yep, there are a number of apps out there you can use for reference. There is a Sawtooth SDK NPM module which will provide you with the transaction/batch protobufs. Then you can POST the bytes to the Sawtooth REST API or your own custom REST API. https://github.com/hyperledger/education-cryptomoji/blob/solution/code/part-two/client/source/services/transactions.js#L36 https://github.com/hyperledger/sawtooth-supply-chain/blob/master/asset_client/src/services/transactions.js#L65

harish.drish (Tue, 14 Aug 2018 06:08:53 GMT):
@zac hi, thank you for your response, I have gone through these example and found that every thing is happening using node module as there is different different export functions.....so I am somewhere confused that how this is signing on client end as everything happening from nodejs and node is running on server side....this is where I am getting confused....if possible for you can you please help me to understand how transaction is created on client side....isn't there should be some way to sign transaction on browser and then sent to node server as per my knowledge this is actually a client side...plaese correct if I am worng

harish.drish (Tue, 14 Aug 2018 06:08:53 GMT):
@zac hi, thank you for your response, I have gone through these example and found that every thing is happening using node module as there is different different export functions.....so I am somewhere confused that how this is signing on client end as everything happening from nodejs and node is running on server side....this is where I am getting confused....if possible for you can you please help me to understand how transaction is created on client side....isn't there should be some way to in-browser transaction signing and then sent to node server as per my knowledge this is actually a client side...plaese correct if I am worng

harish.drish (Tue, 14 Aug 2018 11:07:42 GMT):
@zac hey, would it be possible for you to provide some suggestion about the above query. Really helpless!!

zac (Tue, 14 Aug 2018 13:48:52 GMT):
Those examples use `webpack` to compile the JS, which allows you to use either Node style modules (`require`, `module.exports`), or ES6 style modules (`import`, `export`).

zac (Tue, 14 Aug 2018 13:48:52 GMT):
Those examples use `webpack` to compile the JS, which allows you to use either Node style modules (`require` , `module.exports`), or ES6 style modules (`import` , `export`).

zac (Tue, 14 Aug 2018 13:48:52 GMT):
Those examples use `webpack` to compile the JS, which allows you to use either Node style modules ( `require` , `module.exports`), or ES6 style modules ( `import` , `export`).

zac (Tue, 14 Aug 2018 13:48:52 GMT):
Those examples use `webpack` to compile the JS, which allows you to use either Node style modules ( `require`, `module.exports`), or ES6 style modules ( `import`, `export`).

zac (Tue, 14 Aug 2018 13:50:25 GMT):
The Sawtooth SDK itself is written for Node, so some sort of compilation software like `webpack` is necessary to use it in the browser.

zac (Tue, 14 Aug 2018 13:50:58 GMT):
(It is on the todo list to make slimmed-down browser only version of the SDK, but that does not exist yet)

zac (Tue, 14 Aug 2018 13:52:38 GMT):
Webpack is pretty standard these days, so there are a lot of tutorials out there for setting it up with your project. But if you wanted to go without, you could manually recreate what the SDK does without too much trouble.

zac (Tue, 14 Aug 2018 13:52:55 GMT):
Well

zac (Tue, 14 Aug 2018 13:52:56 GMT):
Maybe

zac (Tue, 14 Aug 2018 13:54:02 GMT):
You would need a Secp256k1 library and a Protobuf library. Not sure how many of those work in the browser without webpack ¯\_(ツ)_/¯

zac (Tue, 14 Aug 2018 13:55:16 GMT):
These are the two we use: - secp256k1-node: https://github.com/cryptocoinjs/secp256k1-node - protobuf.js: https://github.com/dcodeIO/protobuf.js

zac (Tue, 14 Aug 2018 13:57:13 GMT):
You would need to manually recreate the Protobufs you need (Transaction, TransactionHeader, Batch, BatchHeader, BatchList), which is just a matter of getting the right keys in the right place: - https://github.com/hyperledger/sawtooth-core/blob/master/protos/transaction.proto - https://github.com/hyperledger/sawtooth-core/blob/master/protos/batch.proto

zac (Tue, 14 Aug 2018 13:57:13 GMT):
You would need to manually recreate the Protobufs you need ( `Transaction`, `TransactionHeader`, `Batch`, `BatchHeader`, `BatchList`), which is just a matter of getting the right keys in the right place: - https://github.com/hyperledger/sawtooth-core/blob/master/protos/transaction.proto - https://github.com/hyperledger/sawtooth-core/blob/master/protos/batch.proto

zac (Tue, 14 Aug 2018 13:58:02 GMT):
Anyway, I recommend `webpack`, much easier, especially if you are new to signing/protobufs

zac (Tue, 14 Aug 2018 13:58:08 GMT):
@harish.drish ^

Gabe (Mon, 20 Aug 2018 04:15:29 GMT):
Has joined the channel.

harish.drish (Mon, 20 Aug 2018 06:34:22 GMT):
@zac thanks for your response trying to implement webpack

harish.drish (Mon, 20 Aug 2018 10:47:35 GMT):
@zac I am using webpack and when I creating bundle with const {protobuf} = require('sawtooth-sdk') and it is creating bundle.js successfully. But when running bundle.js on browser then it gives below error: Error: Cannot open /home/hyper1/Sawtooth-projects/webpkdemoo/node_modules/zeromq/build/Release/zmq.node: TypeError: global.process is undefined

zac (Mon, 20 Aug 2018 12:19:26 GMT):
What does your webpacl.config.js look like?

BrettR (Wed, 22 Aug 2018 20:03:01 GMT):
Has joined the channel.

GustavoFrederico (Tue, 28 Aug 2018 02:21:06 GMT):
Has joined the channel.

sureshtedla (Fri, 31 Aug 2018 17:00:16 GMT):
Has joined the channel.

LedgerXYZ (Sat, 01 Sep 2018 19:22:59 GMT):
Has joined the channel.

LedgerXYZ (Sat, 01 Sep 2018 19:23:41 GMT):
Hi @zac and all, really basic question: ----------------------------------- Is the hyperledger blockchain's data public?

LedgerXYZ (Sat, 01 Sep 2018 19:24:45 GMT):
specifically the `supply chain` version of it

LedgerXYZ (Sat, 01 Sep 2018 19:29:05 GMT):
AKA, if a read operation is applied to the blockchain without authentication, will it return plain text data

zac (Sun, 02 Sep 2018 05:46:34 GMT):
@LedgerXYZ With any blockchain, all on-chain data is visible to all participants in the blockchain. There are some attempts to work around this limitation, but for now at least this is pretty inherent to the way blockchain verification works.

zac (Sun, 02 Sep 2018 05:48:23 GMT):
Since Sawtooth is a permissioned blockchain, you can limit visibility somewhat by limiting who participates in the blockchain. Though I wonder about the practicality of relying on this for very sensitive data, as you have to trust every participant not to leak the information.

zac (Sun, 02 Sep 2018 05:53:24 GMT):
Hyperledger Fabric takes this idea to the extreme with a feature called channels. If you and I had data we wanted to keep private from the rest of the network, we would establish a sub-chain just between the two of us. I have my doubts about this approach. It scales very poorly as every possible combination of participants who want private data must have their own sub-chain. And I don't understand how consensus is supposed to work when only two participants are involved in a blockchain. Seems to me you must have at least three, so that two can outvote a potential third bad actor.

zac (Sun, 02 Sep 2018 05:56:48 GMT):
There are other approaches as well. Encrypting the data before you put it on-chain (bad). Or storing the data off-chain, but a hash of the data on-chain, so the blockchain becomes a source-of-validity not a source-of-truth (better, but still not great).

zac (Sun, 02 Sep 2018 06:02:28 GMT):
Honestly, I think the best approach for now is not try to come up with some sort of hack to get semi-privacy. Instead, think through your use case, and what data needs to be on-chain and what does not (you should be doing this anyway to keep storage down). Of the data that absolutely must be on-chain, ask yourself if it must also absolutely be private. If you can't come up with a data model that solves your verification, availability, and privacy needs, then a blockchain may not be the right solution for your project.

LedgerXYZ (Mon, 03 Sep 2018 22:57:45 GMT):
@zac happy Labor day, and I hope you don't reply to this until after you've finished enjoying the weekend. When you do get back... ...I am a little surprised that the sawtooth doesn't have a privacy configuration. The enterprise nature of if I understood to address transaction speeds, however I thought I read earlier that it also addresses privacy concerns that you've correctly pointed out are inherent in a distributed environment like a blockchain

LedgerXYZ (Mon, 03 Sep 2018 23:04:10 GMT):
So given this reality, 2 things. Can you discuss more about your opinion about: - Encrypting / decrypting on-chain data through a CRUD permission / grant schemes - Using external data houses like `IPFS` and then using sawtooth as a permission mechanism to perform CRUD operations

LedgerXYZ (Mon, 03 Sep 2018 23:04:10 GMT):
So given this reality, 2 things. Can you discuss more about your opinion about: - Encrypting / decrypting on-chain data through CRUD permission / grant schemes - Using external data houses like `IPFS` and then using sawtooth as a permission mechanism to perform CRUD operations

LedgerXYZ (Mon, 03 Sep 2018 23:04:10 GMT):
So given this reality, 2 things. Can you elaborate more on your opinion regarding: - Encrypting / decrypting on-chain data through CRUD permission / grant schemes - Using external data houses like `IPFS` and then using sawtooth as a permission / grant mechanism to CRUD that data

LedgerXYZ (Mon, 03 Sep 2018 23:26:18 GMT):
Of course encrypting / decrypting every transaction on the blockchain is expensive. However, doesn't the distributed nature of the computing effort in a blockchain make the computational cost negligible? Meaning if `c` = cost to compute, `n` = number of participants, then their relationship is ``` c = 1/ n ````

LedgerXYZ (Mon, 03 Sep 2018 23:29:11 GMT):
The entire blockchain ecosystem is built on cryptography it just seems odd that the data is left out

zac (Tue, 04 Sep 2018 05:57:29 GMT):
Blockchains are different from other peer-to-peer networks because the work is not shared.

zac (Tue, 04 Sep 2018 06:01:42 GMT):
Every node in the network does _all_ the work.

zac (Tue, 04 Sep 2018 06:02:03 GMT):
This is a big part of why blockchains face such scaling issues.

zac (Tue, 04 Sep 2018 06:02:21 GMT):
You get no benefits from scale. In fact it will tend to slow you down.

zac (Tue, 04 Sep 2018 06:04:16 GMT):
My issue with encryption though is not performance. You can't decrypt it to do any work on-chain anyway. You can only store it. If an on-chain smart contract knows how to decrypt the data and do some work with it, then _everyone_ knows how to decrypt it.

zac (Tue, 04 Sep 2018 06:08:28 GMT):
My problem with storing encrypted data on-chain is that you are just asking for it to be compromised. Assuming your blockchain is long-lived, that encrypted data is never going away. It will just be sitting out there for years and years. Maybe you accidentally leak the secret, and there is no way to take the data down. Hell, maybe someone manages to brute force it. They will have a long time to try.

zac (Tue, 04 Sep 2018 06:12:59 GMT):
Storing the sensitive data off-chain and using the blockchain as a source-of-permission and source-of-validity is a much better model I think. A pretty good middle-of-the-road solution.

zac (Tue, 04 Sep 2018 06:13:49 GMT):
You could ensure the data hasn't been tampered with. You can't use the blockchain to ensure the wrong people don't get access to the data. It will be up to whoever is storing it off-chain to follow the permissions set on-chain. But a lot of folks are looking at blockchains as a decentralized permissioning system. The blockchain also can't ensure that the data is available. Whoever is storing it off-chain could just delete it.

zac (Tue, 04 Sep 2018 06:13:49 GMT):
You could ensure the data hasn't been tampered with. Which is good. You can't ensure that the data is available. Whoever is storing it off-chain could just delete it. You also can't use the blockchain to ensure the wrong people don't get access to the data. It will be up to whoever is storing it off-chain to follow the permissions set on-chain. But a lot of folks are looking at blockchains as a decentralized permissioning system. It's a sensible application I think.

zac (Tue, 04 Sep 2018 06:18:04 GMT):
The short version is this: privacy is counter to the fundamental nature of the blockchain. A lot of people really want privacy in blockchains and are working hard to come up with clever solutions. They may work. They may also not. It may just be impossible. There are some hacky work arounds like channels available today, which might be useful for you, but for the most part data on any blockchain should be considered public.

LedgerXYZ (Tue, 04 Sep 2018 15:08:56 GMT):
@zac Thanks for your reply

LedgerXYZ (Tue, 04 Sep 2018 15:10:47 GMT):
I like the sawtooth as a permissioner approach because it can be integrated nicely with other chains that are better suited for storing encrypted data

LedgerXYZ (Tue, 04 Sep 2018 15:14:51 GMT):
I should also point out that as a consequence of your confirmation that the data on the sawtooth blockchain isn't public, users should be aware that at a minimum, their `public keys` and `names` are not private on the chain

LedgerXYZ (Tue, 04 Sep 2018 15:14:51 GMT):
I should also point out that as a consequence of your confirmation that the data on the sawtooth blockchain isn't private, users should be aware that at a minimum, their `public keys` and `names` are not private on the chain

LedgerXYZ (Tue, 04 Sep 2018 15:19:50 GMT):
So examining the sawtooth distributed ledger, reveals all transactions, the actors, timestamps, and values. Clearly this model as-is will not work in European countries that have enforced the `Right to be forgotten` laws as well as for data sensitive industries like banking, healthcare, etc

zac (Tue, 04 Sep 2018 15:35:28 GMT):
To be clear nothing I have said has been about Sawtooth

zac (Tue, 04 Sep 2018 15:35:38 GMT):
It has been about blockchains in general

zac (Tue, 04 Sep 2018 15:36:09 GMT):
I believe storing encrypted data on a blockchain to be a bad model on _any_ blockchain

zac (Tue, 04 Sep 2018 15:36:21 GMT):
It will work no worse on Sawtooth than anywhere else

zac (Tue, 04 Sep 2018 15:37:04 GMT):
Blockchains are by nature entirely transparent and immutable

jsmitchell (Tue, 04 Sep 2018 15:37:48 GMT):
To the orgs that run nodes

zac (Tue, 04 Sep 2018 15:37:57 GMT):
yes

arsulegai (Tue, 11 Sep 2018 19:02:53 GMT):
Has joined the channel.

cecchi (Wed, 12 Sep 2018 19:28:03 GMT):
Has joined the channel.

adamgering (Fri, 14 Sep 2018 19:09:22 GMT):
Has joined the channel.

adamgering (Fri, 14 Sep 2018 19:11:26 GMT):
Besides sawtooth-supply-chain, sawtooth-marketplace and sawtooth-next-directory; are there any other applications of sawtooth that use rethinkdb?

adamgering (Fri, 14 Sep 2018 19:24:31 GMT):
Are either sawtooth-supply-chain or sawtooth-marketplace being actively developed or maintained?

agunde (Fri, 14 Sep 2018 19:27:30 GMT):
Sawtooth Supply Chain is maintained and will have future development.

adamgering (Fri, 14 Sep 2018 19:34:54 GMT):
Is that being maintained at https://github.com/hyperledger/sawtooth-supply-chain ?

adamgering (Fri, 14 Sep 2018 19:34:54 GMT):
Is that being maintained at https://github.com/hyperledger/sawtooth-supply-chain?

adamgering (Fri, 14 Sep 2018 19:35:50 GMT):
Also, I didn't find a project for it at Hyperledger JIRA. Where are issues being tracked?

Rohan42 (Mon, 17 Sep 2018 08:34:57 GMT):
Has joined the channel.

amundson (Mon, 17 Sep 2018 15:20:21 GMT):
@adamgering we haven't generated a long backlog of issues for supply chain recently, though JIRA is the right place for it. however, many of the new features have RFCs - https://github.com/hyperledger/sawtooth-rfcs.

GNAC (Mon, 17 Sep 2018 16:40:54 GMT):
Has joined the channel.

Lotus (Fri, 21 Sep 2018 12:49:50 GMT):
Has joined the channel.

adave (Mon, 01 Oct 2018 17:46:15 GMT):
Has joined the channel.

sivaprasadsuggu (Thu, 04 Oct 2018 09:35:35 GMT):
Has joined the channel.

sivaprasadsuggu (Thu, 04 Oct 2018 09:36:00 GMT):
I had a sawtooth application which is named as fish-client.I just want to convert this web-page to a nodejs service...when i tried to convert its not connecting to database and application is not starting..please help me on this

Share718 (Thu, 04 Oct 2018 15:50:45 GMT):
Has joined the channel.

SanjivRao (Fri, 05 Oct 2018 12:08:19 GMT):
Has joined the channel.

Lotus (Sat, 06 Oct 2018 13:23:57 GMT):
To create Agent I have created clientside API for sending value to supplychain RESTAPI from port 8020 instead of sending UI. I am running my API via POSTMAN but I am getting below error .Please find error in image

Lotus (Sat, 06 Oct 2018 13:23:57 GMT):
To create Agent I have created clientside API for sending value to supplychain RESTAPI to port 8020 instead of sending UI. I am running my API via POSTMAN but I am getting below error .Please find error in image

Lotus (Sat, 06 Oct 2018 13:23:57 GMT):
To create Agent I have created clientside API for sending value to supplychain RESTAPI to port 8020 instead of sending by UI. I am running my API via POSTMAN but I am getting below error .Please find error in image

Lotus (Sat, 06 Oct 2018 13:23:57 GMT):
To create Agent to I am calling supplychain RESTAPI to port 8020 via POSTMAN instead of UI,but I am getting below error .Please find error in image

Lotus (Sat, 06 Oct 2018 13:24:54 GMT):

Clipboard - October 6, 2018 2:24 PM

Rexcirus (Sun, 07 Oct 2018 21:49:48 GMT):
Has joined the channel.

Rexcirus (Sun, 07 Oct 2018 21:50:46 GMT):
Hi guys, I've cloned the repo and did docker compose up, after a while I get the following error: 'Compiling sawtooth_sdk v0.1.0 (https://github.com/hyperledger/sawtooth-core.git#ca0e8e14) error[E0451]: field `_future_options` of struct `protoc_rust::Customize` is private --> /usr/local/cargo/git/checkouts/sawtooth-core-bddd99292bb7bf5f/ca0e8e1/sdk/rust/build.rs:66:15 | 66 | ..Default::default() | ^^^^^^^^^^^^^^^^^^ field `_future_options` is private error: aborting due to previous error For more information about this error, try `rustc --explain E0451`. error: Could not compile `sawtooth_sdk`. warning: build failed, waiting for other jobs to finish... error: build failed ERROR: Service 'processor' failed to build: The command '/bin/sh -c cargo build' returned a non-zero code: 101'

SanjivRao (Mon, 08 Oct 2018 12:06:35 GMT):
Hi All, I wanted to understand the sawtooth supply chain in detail and looking for documentation. Please let me know where can I find detailed technical specs for the same. Thanks a lot.

Lotus (Mon, 08 Oct 2018 14:00:34 GMT):
Could you please tell me is it possible to run fish client on my local machine wiithout docker?

agunde (Mon, 08 Oct 2018 15:57:10 GMT):
@Rexcirus protobuf updated with a breaking change. We are working to address the issue.

agunde (Mon, 08 Oct 2018 19:42:45 GMT):
A fix has been merged

ArwaKanani (Tue, 09 Oct 2018 06:31:22 GMT):
Has joined the channel.

ArwaKanani (Tue, 09 Oct 2018 06:33:33 GMT):
Hi all , iam running sawtooth-supply-chain in Docker , everything goes fine. How can run web app as i can see dashboard.js file

Lotus (Tue, 09 Oct 2018 08:26:41 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=guuf5sR9vraYcXrzT) @ArwaKanani where you are running at that machine port 8022 you will get fish-client and at 8021 you will get asset-client

Lotus (Tue, 09 Oct 2018 08:26:41 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=guuf5sR9vraYcXrzT) @ArwaKanani where you are running docker at that machine port 8022 you will get fish-client and at 8021 you will get asset-client

sivaprasadsuggu (Tue, 09 Oct 2018 12:32:35 GMT):
Hi all, Tring to create service for supply-chain fish-client.Getting this erro:ReferenceError: wait is not defined Can any one help me in this?

agunde (Tue, 09 Oct 2018 13:51:03 GMT):
@sivaprasadsuggu can you explain more about what you are trying to do and what the problem is?

danintel (Tue, 09 Oct 2018 15:26:42 GMT):
Has joined the channel.

sassit (Tue, 09 Oct 2018 18:35:42 GMT):
Has joined the channel.

arsulegai (Tue, 09 Oct 2018 19:12:34 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=bkKyQPP95idS8RJTS) @SanjivRao I guess, this is what you are looking for https://sawtooth.hyperledger.org/docs/supply-chain/nightly/master/

sassit (Tue, 09 Oct 2018 21:17:10 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=6zfdShDpJZdNFmk8Q) @Rexcirus do a git pull and rebuild again, had the same issue, they fixed it

sivaprasadsuggu (Wed, 10 Oct 2018 13:03:08 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=7qDsPMuzohf2xyafH) @agunde I cloned sawtooth-supply-chain,in which we have one of the sample program fish-client .I executed the program,it's opened in web browser.For example we have agents tab,when i click on that tab,it fetches data from from block chain and displays those records in browser.The same think i want to do as a service instead of displaying it in browser.Please find the attachment to which i wanted to convert as API service. Thank @agunde for responding on my query

sivaprasadsuggu (Wed, 10 Oct 2018 13:03:22 GMT):

Screenshot from 2018-10-10 18-12-42.png

agunde (Wed, 10 Oct 2018 13:17:07 GMT):
I'm not very familiar with node.js (as you had mentioned you were using earlier). Can you tell were your error is coming from?

sivaprasadsuggu (Wed, 10 Oct 2018 13:21:19 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=bEqyY4g3pmrZMiQ8n) @agunde ReferenceError: wait is not defined at /home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/src/restapi/test.js:126:48 at Layer.handle [as handle_request] (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/layer.js:95:5) at next (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/route.js:137:13) at Route.dispatch (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/layer.js:95:5) at /home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/index.js:281:22 at Function.process_params (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/index.js:335:12) at next (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/index.js:275:10) at Function.handle (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/index.js:174:3) at router (/home/ganesh/sawtooth3,0/sawtooth-supply-chain/fish_client/node_modules/express/lib/router/index.js:47:12)

sivaprasadsuggu (Wed, 10 Oct 2018 13:23:21 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=bEqyY4g3pmrZMiQ8n) @agunde Same thing is working well inside block chain.but when i try to create service it's giving more and more problems

agunde (Wed, 10 Oct 2018 13:26:57 GMT):
And the restapi/test.js is what you wrote? Looks like it is being passed a wait argument but it is not defined?

AlexanderZhovnuvaty (Wed, 10 Oct 2018 14:10:32 GMT):
Has joined the channel.

Psypher246 (Wed, 10 Oct 2018 16:55:13 GMT):
Has joined the channel.

sivaprasadsuggu (Wed, 10 Oct 2018 16:58:48 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=au5Dph9AhLfyGg9ts) @agunde Yeah, that transaction?wait is the endpoint of transaction..I need to pass it right?so the same thing i'm passing it their too..

Psypher246 (Wed, 10 Oct 2018 17:03:42 GMT):
Hello all, I'm trying to decouple the docker sample to run on a cloud platform in a scalable way and having a hard time figuring out how each component first together. I have a validator, rest-api, settings-tp, rethinkdb, and server up and running (i think), but when I try get the supply-shell up and running it's failing to complete "npm run make-asset". I suspect the issue is that the docker setup is using a shared directory and i've missed something. I'm trying to understand how I can drop the shared directory and correctly build each container with the correct dependencies but having some struggles with that. for example what is the difference between the dockerfile and dockerfile-installed, I'm using the dockerfile in my process. and so I assume without compiling asset and fish client I can't get those 2 containers running either, since there is no mention of building the content in the asset or fish client dockerfiles, is this being compiled in the supply-shell This is what happens when my shell fails it's entrypoint scripts: npm run make-asset > supply_chain_server@0.0.0 make-asset /sawtooth-supply-chain/server > DATA="../../asset_client/sample_data/core_types.json" node ./scripts/seed_core_types.js http://server.local:3000 RequestError: Error: socket hang up request arrives at the server though: Received GET request for /info from ::ffff:10.180.32.146 Received POST request for /transactions?wait from ::ffff:10.180.32.146 seems like the server is answering, but not responding, any help on how I can troubleshoot this?

sassit (Wed, 10 Oct 2018 21:05:50 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=TJqNz4FwdWiiPhMaY) @Psypher246 What you mean with a scalable way? Sawtooth is on a permissioned blockchain, I would not worry about scaling in the given context. I also had massive issues on the supply-shell. For whatever reason the flag to start code to seed the db etc. was not executed even though it was some time before, so I manually execute it now until I find out why the flag does not work. I don't see any shared directories, all of them are services running in their own container, which area you assume is shared? The initial files from supply-chain are shared but nonetheless they spin up several containers which have no shared "directory". The -installed files are just not rebuilding the whole stack they just re-instantiate a built image, AFAIK. If you wanna get rid of the supply-shell then you have to move these calls to the fish client container setup with a dependency to the db and other dependencies. You also have to move the scripts that are called to the other containers then.

Psypher246 (Thu, 11 Oct 2018 07:15:46 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=2fKfs2tKkXkshQuJB) @sassit @sassit By scalable I mean a combination or redundancy for the validator and TPs and scalability for the rest-api and clients. As I understand per organisation I only need 1 tp and 1 validator correct? but the rest of the stuff would need to scale out as users interact with the interfaces. Regarding the shared directory. In the docker-compose.yaml there is constant mention of mounting the local shared directory into some of the containers, and in the dockerfile it only some of the code is copied to the containers at build time, which means they expect to be able to access the rest of the code from the shared directory. Without it nothing worked as I was wiring this stuff up, for example, the asset client does almost no building in the dockerkfile at all, just writes an httpd.conf file, yet the shell client has to d/l all the node deps and compile the asset and fish client which it stores in the mounted volume, which the asset client accesses as per the docker-compose:volumes: - ./asset_client/public/:/usr/local/apache2/htdocs/ I think you are correct though to move the build scripts from the shell to the fish and asset client. My shell seems to be seeding the DB correctly but now I'm not sure. Can anyone tell me what npm run make-asset is doing (not a node expert), where it's reading it's code from and what it's doing when it connects to the server, which then fails and hangs-up as shown in my post above? If i'm supposed to move these to the containers to build how would it connect to the server to do the build?

Psypher246 (Thu, 11 Oct 2018 15:15:13 GMT):
I've been able to narrow down the failure point to server/blockchain/index.js line 48: return stream.send( Message.MessageType.CLIENT_BATCH_SUBMIT_REQUEST, ClientBatchSubmitRequest.encode({ batches: [batch] }).finish() ) but despite help from a colleague who knows node, we weren't able to figure out why or even get any failures to report. any guidance is much appreciated. Another thing I'm trying to understand is whether the supply-tp is actually connecting properly to the validator. I see it trying: INFO | sawtooth_sdk::proces | sending TpRegisterRequest: supply_chain 1.1 INFO | sawtooth_sdk::proces | connecting to endpoint: tcp://validator.local:4004 but I don'y see anything beyond that, no confirmation on either side that it worked. Compared to the setting-tp which has a whole bunch of messages in the log back and forth. Could this be my issue?

agunde (Thu, 11 Oct 2018 15:18:16 GMT):
@zac Can you provide some guidance?

zac (Thu, 11 Oct 2018 15:18:55 GMT):
looking...

agunde (Thu, 11 Oct 2018 15:19:07 GMT):
Thank you.

zac (Thu, 11 Oct 2018 15:23:57 GMT):
@Psypher246 `-installed` is a convention we've been using internally to distinguish between docker components for development and docker components for deployment

zac (Thu, 11 Oct 2018 15:24:49 GMT):
The default components rely on `volumes` to link to the source code on your host machine. Allowing changes to be reflected without rebuilding.

zac (Thu, 11 Oct 2018 15:25:25 GMT):
However for deploying you will want to using the `-installed` version of things, as that will actually copy over the source code into the docker images.

zac (Thu, 11 Oct 2018 15:26:34 GMT):
So, without diving too deep, I think what you want to do is to deploy the installed version of things, and then from `npm run make-asset` from within the `server` component.

zac (Thu, 11 Oct 2018 15:26:34 GMT):
So, without diving too deep, I think what you want to do is to deploy the installed version of things, and then run `npm run make-asset` from within the `server` component.

zac (Thu, 11 Oct 2018 15:27:06 GMT):
That should do what you need

Psypher246 (Thu, 11 Oct 2018 15:28:09 GMT):
ok cool, thanks for confirming all those points, definitely helps. I will try -installed and run the scripts again from server. so they don't have to run from shell?

zac (Thu, 11 Oct 2018 15:30:22 GMT):
Well, the installed compose file doesn't have a shell. It's basically a big Frankenstein container with all of the source code and dependencies. It's a development tool which you probably shouldn't deploy.

zac (Thu, 11 Oct 2018 15:30:56 GMT):
However, the server-installed image _does_ copy over the JSON data from the clients, so you can run those scripts directly from within there: https://github.com/hyperledger/sawtooth-supply-chain/blob/master/server/Dockerfile-installed#L45

Psypher246 (Thu, 11 Oct 2018 16:08:59 GMT):
@zac, seems the same thing happens, it tries to connect to the server, server shows: Received GET request for /info from ::ffff:127.0.0.1 Received POST request for /transactions?wait from ::ffff:127.0.0.1 in the logs and then nothing happens. also again when my processor starts up, it still seems like it's not registered with the validator at all

jsmitchell (Thu, 11 Oct 2018 16:21:14 GMT):
ipv6

zac (Thu, 11 Oct 2018 16:29:43 GMT):
The make asset script follows this routine: 1. Fetch batcher public key from `/info` 2. Builds asset type transactions 3. Submits those transactions to `/transactions?wait` 4. Logs out: `"Types submitted: asset"`

zac (Thu, 11 Oct 2018 16:30:25 GMT):
That is sequential, so if you are getting HTTP requests to both `/info` and `/transactions` I suspect the weird ipv6 addresses are not the issue

zac (Thu, 11 Oct 2018 16:30:33 GMT):
Because the first request seems to have worked

zac (Thu, 11 Oct 2018 16:30:56 GMT):
You might be correct that the server is not talking to the validator though

zac (Thu, 11 Oct 2018 16:32:58 GMT):
Is the `VALIDATOR_URL` configured properly?

zac (Thu, 11 Oct 2018 16:34:10 GMT):
You can set it with an environment variable or a `server/config.json` file

zac (Thu, 11 Oct 2018 16:34:46 GMT):
It defaults to `tcp://localhost:4004` which will almost certainly not work

zac (Thu, 11 Oct 2018 16:34:46 GMT):
It defaults to `tcp://localhost:4004` which will almost certainly not work for your deployment

sassit (Thu, 11 Oct 2018 18:02:08 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=sGRkRuqMhGJpdKa92) @Psypher246 I am new to it too but I would say it is correct according to the docs. The code you downloaded and the volumes are connected, so if you develop and build something within the mapped volumes changes are reflected in your container. You won't need that in a released environment so the installed environment will run without building anything as the docker image will be up to date. Normally these files are copied with the COPY command in the docker world, e.g. if you have already built packages you probably will not use volumes. npm run make-asset tells npm to run the command which is in the sawtooth-supply-chain/server/package.json, the command does the seeding of data to the database, the other command does the prototype injections to node. So your command make asset fails sending the protos to the node server. "make-asset": "DATA=\"../../asset_client/sample_data/core_types.json\" node ./scripts/seed_core_types.js",

sassit (Thu, 11 Oct 2018 20:11:08 GMT):
I am getting these errors during seeding of the data, also when I wanna create a new agent: supply-server | Received POST request for /transactions?wait from ::ffff:172.18.0.8 supply-tp | INFO | sawtooth_sdk::proces | Message: 272f791dfe6a4d0ab62da0a01c6a2423 supply-tp | INFO | supply_chain_tp::han | payload: CreateAgent(name: "Ahab") 1539288001 3400de 3400de supply-tp | INFO | sawtooth_sdk::proces | TP_PROCESS_REQUEST sending TpProcessResponse: AuthorizationError: Tried to get unauthorized address: ["7ea0cfae17022a16a58c05c0e1d43bff6b20e4e6a4935d20f472bec8b8f4ac33e742da"] supply-validator | [2018-10-11 20:00:01.809 DEBUG publisher] Batch c15ec3f86e13bccb5e9d28109e09a2ae73c3ac962455e7d8ddcc4f2854733fc574259cfb61aa24dfaaeb3ba0858234d0fc9e2320d72ff8fb06571618110d09a7 invalid, not added to block. supply-validator | [2018-10-11 20:00:01.809 DEBUG publisher] Abandoning block (1, S:, P:61884993): no batches added supply-shell | StatusCodeError: 500 - {"type":"Buffer","data":[123,34,101,114,114,111,114,34,58,34,66,97,116,99,104,32,99,49,53,101,99,51,102,56,54,101,49,51,98,99,99,98,53,101,57,100,50,56,49,48,57,101,48,57,97,50,97,101,55,51,99,51,97,99,57,54,50,52,53,53,101,55,100,56,100,100,99,99,52,102,50,56,53,52,55,51,51,102,99,53,55,52,50,53,57,99,102,98,54,49,97,97,50,52,100,102,97,97,101,98,51,98,97,48,56,53,56,50,51,52,100,48,102,99,57,101,50,51,50,48,100,55,50,102,102,56,102,98,48,54,53,55,49,54,49,56,49,49,48,100,48,57,97,55,32,105,115,32,73,78,86,65,76,73,68,44,32,119,105,116,104,32,109,101,115,115,97,103,101,58,32,65,117,116,104,111,114,105,122,97,116,105,111,110,69,114,114,111,114,58,32,84,114,105,101,100,32,116,111,32,103,101,116,32,117,110,97,117,116,104,111,114,105,122,101,100,32,97,100,100,114,101,115,115,58,32,91,92,34,55,101,97,48,99,102,97,101,49,55,48,50,50,97,49,54,97,53,56,99,48,53,99,48,101,49,100,52,51,98,102,102,54,98,50,48,101,52,101,54,97,52,57,51,53,100,50,48,102,52,55,50,98,101,99,56,98,56,102,52,97,99,51,51,101,55,52,50,100,97,92,34,93,34,125]}

sassit (Thu, 11 Oct 2018 21:00:58 GMT):
I am halfway through this course and it is excellent: https://www.udemy.com/docker-and-kubernetes-the-complete-guide/

ArwaKanani (Fri, 12 Oct 2018 06:23:46 GMT):
Can we use Heperledger composer instead of Docker composer for customizing sawtooth-supply-chain

AbhinandanDarbey (Fri, 12 Oct 2018 07:02:48 GMT):
Has joined the channel.

Psypher246 (Fri, 12 Oct 2018 10:52:21 GMT):
@zac the server seems to be talking to the validator and yes I do have the `VALIDATOR_URL` set correctly: { PATH: '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', HOSTNAME: 'ip-10-180-39-100.eu-west-1.compute.internal', DB_HOST: 'rethink.local', VALIDATOR_URL: 'tcp://validator.local:4004', HOME: '/root' } WARNING! No signing key provided. Batch signing will be insecure! Set "PRIVATE_KEY" as an environment variable or in "config.json" file. WARNING! No secret provided. JWT authorization tokens will be insecure! Set "JWT_SECRET" as an environment variable or in "config.json" file. Batch signer initialized with public key: 034f355bdcb7cc0af728ef3cceb9615d90684bb5b2ca5f859ab0f0b704075871aa Successfully connected to database: supply_chain Connected to tcp://validator.local:4004 Supply Chain Server listening on port 3000 Received GET request for /info from ::ffff:127.0.0.1 Received POST request for /transactions?wait from ::ffff:127.0.0.1 Received POST request for /transactions?wait from ::ffff:10.180.31.249 But asw I said I suspect the processor isn't working. without running make-asset how do can I validate my processor and validator are working as expected?

sauravverma (Sat, 13 Oct 2018 22:41:12 GMT):
Has joined the channel.

zac (Mon, 15 Oct 2018 14:39:16 GMT):
What does the validator log when you submit a batch?

sivaprasadsuggu (Tue, 16 Oct 2018 06:03:02 GMT):
Hi every one, When i try to create my own service with sawtooth javscript sdk,there coming an syntax error, Please find the error log below (function (exports, require, module, __filename, __dirname) { const {createContext, CryptoFactory} = require('sawtooth-sdk/signing') ^ SyntaxError: Unexpected token { at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:374:25) at Object.Module._extensions..js (module.js:417:10) at Module.load (module.js:344:32) at Function.Module._load (module.js:301:12) at Function.Module.runMain (module.js:442:10) at startup (node.js:136:18) at node.js:966:3 can any one help me on this?

sivaprasadsuggu (Tue, 16 Oct 2018 10:36:28 GMT):
can anyone explain me what was the root cause of this below error { Error: getaddrinfo ENOTFOUND rest.api.domain rest.api.domain:80 at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:57:26) errno: 'ENOTFOUND', code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'rest.api.domain', host: 'rest.api.domain', port: 80 }

Psypher246 (Tue, 16 Oct 2018 15:51:21 GMT):
@zac I'm still very new at this, was first trying to get the infrastructure up to be like for like but was playing around with the basic blockchain as per the docs: https://sawtooth.hyperledger.org/docs/core/releases/latest/app_developers_guide/ubuntu.html#creating-and-submitting-transactions but that talks about intkey, where do i find those tools now using the dockerfile-installed process or are there other commands I need to use to submit a batch?

zac (Tue, 16 Oct 2018 16:02:02 GMT):
I thought you were starting up the Docker-installed components in some sort of deployment, and then running `npm run make-asset` from within the server component

Psypher246 (Tue, 16 Oct 2018 16:54:50 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=P9a766p964oevGDoB) @zac I tried but it still did the same thing, nothing. Do I just run 'npm run make-asset' or the other shell commands in docker-compose.yaml? cd asset_client/ && npm run build && cd - && cd fish_client/ && npm run build && cd - && if [ ! -f /root/.sawtooth/keys/root.priv ]; then sawtooth keygen && cd server/ && npm run init && npm run make-asset &

Psypher246 (Tue, 16 Oct 2018 16:59:45 GMT):
@zac logs on the validator after running npm run make-asset [32m[2018-10-16 16:55:41.869 INFO publisher][0m [37mClaimed Block: 5a3cda2e5e46dd885a326813c35694bd251592106309715a38fff97f8fd4b9254553c6983da90e955e24b14d22f73f8d7dc58606a6e59d56a327052a494d443f (block_num:3, state:6e49ec4a1d5531de2b075852c2e5c71e2156848afcafcdae2819bb4ed5443747, previous_block_id:5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db)[0m [32m[2018-10-16 16:55:41.870 INFO publisher][0m [37mBlock publishing is suspended until new chain head arrives.[0m [36m[2018-10-16 16:55:41.870 DEBUG chain][0m [37mBlock received: 5a3cda2e5e46dd885a326813c35694bd251592106309715a38fff97f8fd4b9254553c6983da90e955e24b14d22f73f8d7dc58606a6e59d56a327052a494d443f (block_num:3, state:6e49ec4a1d5531de2b075852c2e5c71e2156848afcafcdae2819bb4ed5443747, previous_block_id:5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db)[0m [32m[2018-10-16 16:55:41.871 INFO block_validator][0m [37mStarting block validation of : 5a3cda2e5e46dd885a326813c35694bd251592106309715a38fff97f8fd4b9254553c6983da90e955e24b14d22f73f8d7dc58606a6e59d56a327052a494d443f (block_num:3, state:6e49ec4a1d5531de2b075852c2e5c71e2156848afcafcdae2819bb4ed5443747, previous_block_id:5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db)[0m [32m[2018-10-16 16:55:41.894 INFO block_validator][0m [37mComparing current chain head '5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db (block_num:2, state:d948ad592859aed6f777c720fd50fd498cf6ff53067cc19279fd2f855fbbf39a, previous_block_id:945a8dcca0ffbc7cb795192df5e887edf86899472aff40eefa8c8f964d8e7a2a59637981eee2e9578dd3517852cb3d72b2a239800e0d48ca385e67ff9b48ff3e)' against new block '5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db (block_num:2, state:d948ad592859aed6f777c720fd50fd498cf6ff53067cc19279fd2f855fbbf39a, previous_block_id:945a8dcca0ffbc7cb795192df5e887edf86899472aff40eefa8c8f964d8e7a2a59637981eee2e9578dd3517852cb3d72b2a239800e0d48ca385e67ff9b48ff3e)'[0m [32m[2018-10-16 16:55:41.894 INFO block_validator][0m [37mFork comparison at height 3 is between - and 5a3cda2e[0m [32m[2018-10-16 16:55:41.894 INFO chain][0m [37mChain head updated to: 5a3cda2e5e46dd885a326813c35694bd251592106309715a38fff97f8fd4b9254553c6983da90e955e24b14d22f73f8d7dc58606a6e59d56a327052a494d443f (block_num:3, state:6e49ec4a1d5531de2b075852c2e5c71e2156848afcafcdae2819bb4ed5443747, previous_block_id:5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db)[0m [32m[2018-10-16 16:55:41.894 INFO publisher][0m [37mNow building on top of block: 5a3cda2e5e46dd885a326813c35694bd251592106309715a38fff97f8fd4b9254553c6983da90e955e24b14d22f73f8d7dc58606a6e59d56a327052a494d443f (block_num:3, state:6e49ec4a1d5531de2b075852c2e5c71e2156848afcafcdae2819bb4ed5443747, previous_block_id:5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db)[0m [36m[2018-10-16 16:55:41.896 DEBUG chain][0m [37mVerify descendant blocks: 5a3cda2e5e46dd885a326813c35694bd251592106309715a38fff97f8fd4b9254553c6983da90e955e24b14d22f73f8d7dc58606a6e59d56a327052a494d443f (block_num:3, state:6e49ec4a1d5531de2b075852c2e5c71e2156848afcafcdae2819bb4ed5443747, previous_block_id:5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db) ([])[0m [32m[2018-10-16 16:55:41.896 INFO block_validator][0m [37mFinished block validation of: 5a3cda2e5e46dd885a326813c35694bd251592106309715a38fff97f8fd4b9254553c6983da90e955e24b14d22f73f8d7dc58606a6e59d56a327052a494d443f (block_num:3, state:6e49ec4a1d5531de2b075852c2e5c71e2156848afcafcdae2819bb4ed5443747, previous_block_id:5d8f24986ab00a2cf4a3fe885bedfd19cfef394f8c5e90cfc3572e2677264fc70317f6aeccfcbb6eeecfa00d001f42dfbfa16d1d370d1c27a649f6efb67c23db)[0m

Psypher246 (Tue, 16 Oct 2018 17:00:23 GMT):
but then eventually: RequestError: Error: socket hang up on the server

Psypher246 (Tue, 16 Oct 2018 18:44:53 GMT):
@zac Ive torn down my stack and started from scratch, bringing up each component one by one in the following order: validator > settings-tp > rethink > processor . And when Irbing up settings-tp I see a lot of action in the validator logs, but when I bring up processor, I see no action in the validator logs at all and on the processor logs I just get: INFO | supply_chain_tp:83 | Console logging level: DEBUG INFO | sawtooth_sdk::proces | connecting to endpoint: tcp://validator.local:4004 INFO | sawtooth_sdk::proces | sending TpRegisterRequest: supply_chain 1.1 So is that expected? Not to see anything in validator's logs? Seems to me the processor is not connecting. But I can telnet from the processor to validator.local 4004

zac (Tue, 16 Oct 2018 20:36:12 GMT):
No, the TP should register

zac (Tue, 16 Oct 2018 20:36:25 GMT):
Which will log on both the processor and validator

zac (Tue, 16 Oct 2018 20:36:44 GMT):
The validator will say something like "added TP with the family . . ."

zac (Tue, 16 Oct 2018 20:37:04 GMT):
The processor will say something simpler like "registration successful"

zac (Tue, 16 Oct 2018 20:38:32 GMT):
If the processor is not registered with the validator, then your batch will just sit in the pending queue indefinitely

zac (Tue, 16 Oct 2018 20:38:48 GMT):
Which I imagine could cause the problems you are seeing

zac (Tue, 16 Oct 2018 20:38:53 GMT):
@Psypher246 ^

Psypher246 (Wed, 17 Oct 2018 07:47:16 GMT):
@zac so any clues on why it's not registering? FYI I was able to build the standard docker network as described here: https://sawtooth.hyperledger.org/docs/core/releases/latest/app_developers_guide/docker.html# and did not have any issues with the TP. IS there any way to get additional debug logs? I'm already running my validator and processor with -vv

zac (Wed, 17 Oct 2018 13:46:05 GMT):
No bullet proof debug methods come to mind. It is interesting that the server is connecting to the validator but the processor is not. Seems almost certainly to be a networking issue. Is the URL for the validator the same on the processor and server? _Should_ it be the same? Can the processor do any networking at all? The ledger sync should also be connecting to the validator. Is it able to connect?

Psypher246 (Wed, 17 Oct 2018 15:19:28 GMT):
@zac networking seems fine, yes they are all using the same url. I can also see incoming packets on the validator from the processor when I do tcpdump. It does seem that "sometimes" it connects to the validator: [32m[2018-10-17 13:23:28.739 INFO processor_handlers][0m [37mregistered transaction processor: connection_id=678dd47a67d0a3a286184408197c45641c43678e98e7986e24fbe6a304f3b66ec00562098a302bd3fe7d21d6559a3c18e4b3a6fff04bac69c8fd79e76ac91a46, family=supply_chain, version=1.1, namespaces=['3400de'][0m

Psypher246 (Wed, 17 Oct 2018 15:20:13 GMT):
13:23:28.734006 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [S], seq 4107899288, win 26883, options [mss 8961,sackOK,TS val 1560703808 ecr 0,nop,wscale 7], length 0 13:23:28.734034 IP 10.180.34.145.4004 > 10.180.27.148.46728: Flags [S.], seq 2464840875, ack 4107899289, win 28960, options [mss 1460,sackOK,TS val 3363748649 ecr 1560703808,nop,wscale 7], length 0 13:23:28.734465 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [.], ack 1, win 211, options [nop,nop,TS val 1560703809 ecr 3363748649], length 0 13:23:28.734517 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [P.], seq 1:11, ack 1, win 211, options [nop,nop,TS val 1560703809 ecr 3363748649], length 10 13:23:28.734523 IP 10.180.34.145.4004 > 10.180.27.148.46728: Flags [.], ack 11, win 227, options [nop,nop,TS val 3363748650 ecr 1560703809], length 0 13:23:28.734587 IP 10.180.34.145.4004 > 10.180.27.148.46728: Flags [P.], seq 1:12, ack 11, win 227, options [nop,nop,TS val 3363748650 ecr 1560703809], length 11 13:23:28.734981 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [.], ack 12, win 211, options [nop,nop,TS val 1560703809 ecr 3363748650], length 0 13:23:28.734999 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [P.], seq 11:65, ack 12, win 211, options [nop,nop,TS val 1560703809 ecr 3363748650], length 54 13:23:28.735034 IP 10.180.34.145.4004 > 10.180.27.148.46728: Flags [P.], seq 12:65, ack 65, win 227, options [nop,nop,TS val 3363748650 ecr 1560703809], length 53 13:23:28.735053 IP 10.180.34.145.4004 > 10.180.27.148.46728: Flags [P.], seq 65:108, ack 65, win 227, options [nop,nop,TS val 3363748650 ecr 1560703809], length 43 13:23:28.735469 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [.], ack 108, win 211, options [nop,nop,TS val 1560703810 ecr 3363748650], length 0 13:23:28.735492 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [P.], seq 65:124, ack 108, win 211, options [nop,nop,TS val 1560703810 ecr 3363748650], length 59 13:23:28.738525 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [P.], seq 124:175, ack 108, win 211, options [nop,nop,TS val 1560703813 ecr 3363748650], length 51 13:23:28.738543 IP 10.180.34.145.4004 > 10.180.27.148.46728: Flags [.], ack 175, win 227, options [nop,nop,TS val 3363748654 ecr 1560703810], length 0 13:23:28.740102 IP 10.180.34.145.4004 > 10.180.27.148.46728: Flags [P.], seq 108:134, ack 175, win 227, options [nop,nop,TS val 3363748655 ecr 1560703810], length 26 13:23:28.784189 IP 10.180.27.148.46728 > 10.180.34.145.4004: Flags [.], ack 134, win 211, options [nop,nop,TS val 1560703859 ecr 3363748655], length 0

Psypher246 (Wed, 17 Oct 2018 15:22:27 GMT):
please also confirm what all the steps are for running `npm run make-asset` on the server, is it all the steps I mentioned or just that one?

zac (Wed, 17 Oct 2018 17:24:22 GMT):
Oh yeah

zac (Wed, 17 Oct 2018 17:24:29 GMT):
Def not all those steps

zac (Wed, 17 Oct 2018 17:25:12 GMT):
Though I don't _think_ running all those would cause this issue

zac (Wed, 17 Oct 2018 17:25:32 GMT):
All you should do is `init` and `make-asset`

zac (Wed, 17 Oct 2018 17:26:11 GMT):
scratch that

zac (Wed, 17 Oct 2018 17:26:15 GMT):
just `make-asset`

zac (Wed, 17 Oct 2018 17:26:54 GMT):
assuming `init` is getting run at start up like in the installed docker-compose file: https://github.com/hyperledger/sawtooth-supply-chain/blob/master/docker-compose-installed.yaml#L57

zac (Wed, 17 Oct 2018 17:27:26 GMT):
If `init` has never been run, then you will need to run it.

zac (Wed, 17 Oct 2018 17:27:42 GMT):
It sets up the DB tables.

zac (Wed, 17 Oct 2018 17:27:58 GMT):
Everything else is `shell` stuff though. You wouldn't run it from the server.

Psypher246 (Wed, 17 Oct 2018 19:06:00 GMT):
@zac I'm starting from scratch again with sawtooth-core. But I noticed that the docker-compose.yaml in the gitbuh repo is again very different from the one in the docs and then there also again a docker-compose-installed.yaml so not sure where to go with this.

zac (Wed, 17 Oct 2018 19:31:54 GMT):
if you are deploying always use the `-installed` stuff

zac (Wed, 17 Oct 2018 19:32:55 GMT):
the default docker components are for developing locally, and will only work properly if you are running them from the repo with all of the source code handy

sivaprasadsuggu (Thu, 18 Oct 2018 08:42:07 GMT):
can any one help me in parsing error in validator sawtooth-validator[17451]: message.ParseFromString(msg_bytes) sawtooth-validator[17451]: google.protobuf.message.DecodeError: Error parsing message sawtooth-validator[17451]: [2018-10-18 14:08:45.015 ERROR interconnect] Received a message on address tcp://127.0.0.1:4004 that caused an error: Error parsing message

kelly_ (Thu, 18 Oct 2018 18:49:35 GMT):
is there documentation on how to deploy sawtooth-supply-chain to sabre?

agunde (Thu, 18 Oct 2018 18:53:08 GMT):
@kelly_ We have not upstreamed the changes needed for running sawtooth-supply-chain in sabre yet.

kelly_ (Thu, 18 Oct 2018 18:53:29 GMT):
ah ok, thanks @agunde

kelly_ (Thu, 18 Oct 2018 18:53:35 GMT):
nice job on the sawtooth update today as well

agunde (Thu, 18 Oct 2018 18:53:39 GMT):
Thanks

cecchi (Thu, 18 Oct 2018 20:16:19 GMT):
i heard something about a new proposal ??

jsmitchell (Thu, 18 Oct 2018 20:22:02 GMT):
@cecchi yep. hot topic! https://lists.hyperledger.org/g/tsc/topic/project_proposal_supply/27370692?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,27370692

cecchi (Thu, 18 Oct 2018 20:25:35 GMT):
:thumbsup:

warren13245 (Fri, 19 Oct 2018 13:36:04 GMT):
Has joined the channel.

warren13245 (Fri, 19 Oct 2018 14:38:56 GMT):

sawtooth fail.png

warren13245 (Fri, 19 Oct 2018 15:24:17 GMT):

demo.png

adamgering (Sat, 20 Oct 2018 08:26:37 GMT):
Pop over to sawtooth-next-directory, and ask about Windows dev env setup. Someone can likely get you the steps next week, and they may solve the problem here.

adamgering (Sat, 20 Oct 2018 08:28:22 GMT):
I believe the problem is with mounting your OS file system using docker volumes in the docket compose config.

adamgering (Sat, 20 Oct 2018 08:28:22 GMT):
I believe the problem is with mounting your OS file system using docker volumes in the docker compose config.

adamgering (Sat, 20 Oct 2018 08:30:20 GMT):
Are those on a fork or a feature branch? @agunde [ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=3o593nmKSksWJF4fg)

warren13245 (Sat, 20 Oct 2018 11:56:52 GMT):
what is sabre

warren13245 (Sat, 20 Oct 2018 14:10:45 GMT):

docker.png

agunde (Mon, 22 Oct 2018 13:12:31 GMT):
@adamgering not yet.

agunde (Mon, 22 Oct 2018 13:13:43 GMT):
@warren13245 Sabre is WASM smart contracts for Sawtooth. you can find the docs here https://sawtooth.hyperledger.org/docs/sabre/nightly/master/ we also have a #sawtooth-sabre channel.

zac (Mon, 22 Oct 2018 17:30:35 GMT):
@warren13245 Have you seen this info before? https://github.com/docker/for-win/issues/77

warren13245 (Mon, 22 Oct 2018 19:02:14 GMT):
@zac yes that's the exact page that helped me solve the problem :joy:

zac (Mon, 22 Oct 2018 19:03:18 GMT):
:+1:

Lotus (Tue, 23 Oct 2018 13:58:30 GMT):
Hi ,I want to know why constant batch key is used in supply chain can we create 2 diff batch key ,is it possible?

zac (Tue, 23 Oct 2018 14:03:50 GMT):
You mean the signing key?

zac (Tue, 23 Oct 2018 14:04:25 GMT):
That was a pretty arbitrary non-decision. There are a lot of ways you could structure all of that.

zac (Tue, 23 Oct 2018 14:04:45 GMT):
It's not configurable though, you would have to go in any change the code yourself.

Lotus (Tue, 23 Oct 2018 14:32:27 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=cW5hSPNhMo934kZ9o) @zac I am saying about batcherPublicKey

zac (Tue, 23 Oct 2018 15:05:09 GMT):
Well, yes

zac (Tue, 23 Oct 2018 15:05:24 GMT):
The batcher has a signing key, which is used to generate the batcherPrivateKey

zac (Tue, 23 Oct 2018 15:06:37 GMT):
I don't know what your use case is to have multiple signing keys on one server, but it is certainly possible. It is not configurable though. You would be making changes to the source code of the server component.

zac (Tue, 23 Oct 2018 15:06:57 GMT):
And probably the clients too, since they assume they are just interacting with one batcher.

Lotus (Tue, 23 Oct 2018 15:16:42 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=2BiEdx6Wrh9WJj5Rm) @zac Not any usecase I am going through coding so I was thinking about multiple batcher keys

Lotus (Tue, 23 Oct 2018 15:18:53 GMT):
Suppose if I create agent1 with batcherkey1 and agent2 with batcherkey2 in this case I want to know that is agent1 can see agent 2 and viceversa.

zac (Tue, 23 Oct 2018 15:26:29 GMT):
Well, it is certainly possible in the scope of things Sawtooth can do

zac (Tue, 23 Oct 2018 15:26:38 GMT):
clients could also batch their own transactions

zac (Tue, 23 Oct 2018 15:27:10 GMT):
The design for sawtooth happens to be that the server would have one identity, and it would batch transactions for clients which would have many

zac (Tue, 23 Oct 2018 15:27:10 GMT):
The design for Supply CHain happens to be that the server would have one identity, and it would batch transactions for clients which would have many

Lotus (Wed, 24 Oct 2018 09:00:32 GMT):
As per code may I know where should I set private key for create batcherpublickey

Lotus (Wed, 24 Oct 2018 09:01:34 GMT):
in the following class sawtooth-supply-chain-master\server\blockchain\index.js

Lotus (Wed, 24 Oct 2018 09:01:34 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=y5A92DNs3xv3icjFs) @zac Thank you

zac (Wed, 24 Oct 2018 14:36:51 GMT):
It's a configuration variable for the server component: `PRIVATE_KEY`

zac (Wed, 24 Oct 2018 14:37:28 GMT):
You can set it with an environment variable or using `server/config.json`

zac (Wed, 24 Oct 2018 14:37:30 GMT):
https://github.com/hyperledger/sawtooth-supply-chain/blob/master/server/config.json.example

ApurvTandon (Sun, 28 Oct 2018 20:14:03 GMT):
Has joined the channel.

coolsvap (Tue, 30 Oct 2018 03:40:28 GMT):
Has joined the channel.

chainsaw (Wed, 31 Oct 2018 14:31:46 GMT):
Has joined the channel.

coveloper (Wed, 31 Oct 2018 18:19:56 GMT):
Has joined the channel.

sshdtk (Fri, 02 Nov 2018 16:08:23 GMT):
Has joined the channel.

sshdtk (Fri, 02 Nov 2018 16:27:15 GMT):
I am trying to create API for fish client for creating payload and transaction. While creating record, I have passed the values through postman , record is creating but property values are not storing. While updating ,the property values are storing correctly. Can anyone please advice.

arsulegai (Tue, 06 Nov 2018 03:46:38 GMT):
I made this small change to make supply-chain use case work in proxy environment - https://github.com/hyperledger/sawtooth-supply-chain/pull/68

Psypher246 (Mon, 19 Nov 2018 12:11:06 GMT):
@zac hey how you doing? I finally got over whatever issue I had getting the core sawtooth components working, not really sure what it was but it was networking related, might have been an incorrect FW rule somewhere. Anyway I can reliably bring up a new node now running on sawtooth 1.0.5. I want to try the supply chain fork again but build it on top of the system I have now. Will the additional services from the version in the supply chain repo work on top of a sawtooth 1.0.5 validator and settings-tp? Do I just have to add the server, ledger-sync, asset-client, fish-client, rethink and supply-tp? Thanks

Psypher246 (Thu, 22 Nov 2018 14:27:10 GMT):
@zac I've been able to get most of the supply chain working on sawtooth 1.0.5 but totally stuck now trying to create an asset. While I can create agents fine when I try create an asset I get the following error on my Supply-TP: ```INFO | supply_chain_tp::han | payload: CreateRecord(record_id: "#1234" record_type: "asset" properties {name: "type" data_type: STRING string_value: "asset"} properties {name: "subtype" data_type: STRING string_value: "2"} properties {name: "weight" data_type: NUMBER number_value: 1000000} properties {name: "location" data_type: LOCATION location_value {latitude: -33944920 longitude: 18522413}}) 1542896481 3400de 3400de INFO | sawtooth_sdk::proces | TP_PROCESS_REQUEST sending TpProcessResponse: Record Type does not exist asset``` Any idea why this record type does not exist?

Psypher246 (Thu, 22 Nov 2018 14:27:10 GMT):
@zac I've been able to get most of the supply chain working on sawtooth 1.0.5 but totally stuck now trying to create an asset. While I can create agents fine when I try create an asset I get the following error on my Supply-TP: ```INFO | supply_chain_tp::han | payload: CreateRecord(record_id: "#1234" record_type: "asset" properties {name: "type" data_type: STRING string_value: "asset"} properties {name: "subtype" data_type: STRING string_value: "2"} properties {name: "weight" data_type: NUMBER number_value: 1000000} properties {name: "location" data_type: LOCATION location_value {latitude: -63944920 longitude: 21522413}}) 1542896481 3400de 3400de INFO | sawtooth_sdk::proces | TP_PROCESS_REQUEST sending TpProcessResponse: Record Type does not exist asset``` Any idea why this record type does not exist?

Psypher246 (Thu, 22 Nov 2018 15:50:04 GMT):
OK, running on sawtooth 1.0 is even more broken. Now I can't even create agents. The Supply Server shows error: ```Index out of bounds: 0 in: r.table("blocks").orderBy(r.desc("blockNum")).nth(0)("blockNum").do(function(var_154) { return r.table("agents").filter(function(var_155) { return var_155("startBlockNum").le(var_154).and(var_155("endBlockNum").gt(var_154)); }).filter(function(var_156) { return r("03ddecb4d8378e4322136b2fb56d0c5f766f3fcc883f883239dd25e1bec1477500").eq(var_156("publicKey")); }).pluck("name", "publicKey").nth(0).do(function(var_157) { return r.branch(null, var_157.merge(r.table("users").filter(function(var_158) { return r("03ddecb4d8378e4322136b2fb56d0c5f766f3fcc883f883239dd25e1bec1477500").eq(var_158("publicKey")); }).pluck("username", "email", "encryptedKey").nth(0)), var_157); }); }) ``` I would prefer to run on 1.0.5 so please any guidance here is appreciated

Psypher246 (Thu, 22 Nov 2018 15:50:04 GMT):
OK I have recreated the stack with sawtooth 1.0 and still the same error: `Record Type does not exist asset`. Any guidance here is appreciated

Psypher246 (Fri, 23 Nov 2018 13:05:29 GMT):
@zac I'm still very stuck with this and running out of time. I tried spinning up the default dev env and it works, it also populates the state with a bunch of agents and assets. So the issue I have is between the dev docker files and prod docker-installed files. Any idea why the record type does not exist? Did I miss a step?

Psypher246 (Fri, 23 Nov 2018 13:05:29 GMT):
@zac I'm still very stuck with this and running out of time. I tried spinning up the default dev local docker environment and it works, it also populates the state with a bunch of agents and assets. So the issue I have is between the dev docker files and prod docker-installed files. Any idea why the record type does not exist? Did I miss a step?

Psypher246 (Mon, 26 Nov 2018 15:53:05 GMT):
Hi @zac and anyone else who can help. I've now also tried running the `docker-compose-installed.yaml` and it too does not want to work. I got it to work up till adding and asset and then nothing happens, not even seeing any logs. But now in subsequent runs it won't work at all, keeps spitting out errors like this ```r.table("blocks").orderBy(r.desc("blockNum")).nth(0)("blockNum").do(function(var_175) { return r.table("records") .filter(function(var_176) { return var_176("startBlockNum").le(var_175).and(var_176("endBlockNum").gt(var_175)); }).filter(function(var_177 ) { return r("1").eq(var_177("recordId")); }).nth(0).do(function(var_178) { return r.table("recordTypes").filter(function(var_179) { return var_179("startBlockNum").le(var_175).and(var_179("endBlockNum").gt(var_175)); }).filter(function(var_180) { return var_178("recordType").e q(var_180("name")); }).map(function(var_181) { return var_181("properties"); }).map(function(var_182) { return var_182("name"); }).nth(0).m ap(function(var_183) { return r.table("properties").filter(function(var_184) { return var_184("startBlockNum").le(var_175).and(var_184("end BlockNum").gt(var_175)); }).filter(function(var_185) { return var_178("r...```

Psypher246 (Mon, 26 Nov 2018 15:53:05 GMT):
Hi @zac and anyone else who can help. I've now also tried running the `docker-compose-installed.yaml` and it too does not want to work. I got it to work up till adding and asset and then nothing happens. IN the logs all I see tis the post attempt: ```supply-server-installed | Received POST request for /transactions?wait from ::ffff:172.23.0.8 supply-asset-client-installed | 172.23.0.1 - - [26/Nov/2018:16:11:19 +0000] "POST /api/transactions?wait HTTP/1.1" 500 205```

Psypher246 (Mon, 26 Nov 2018 15:53:05 GMT):
Hi @zac and anyone else who can help. I've now also tried running the `docker-compose-installed.yaml` and it too does not want to work. I got it to work up till adding and asset and then nothing happens. In the logs all I see this the post attempt: ```supply-server-installed | Received POST request for /transactions?wait from ::ffff:172.23.0.8 supply-asset-client-installed | 172.23.0.1 - - [26/Nov/2018:16:11:19 +0000] "POST /api/transactions?wait HTTP/1.1" 500 205```

Psypher246 (Mon, 26 Nov 2018 15:55:07 GMT):
What are the fundamental differences between the env spun up by docker-compose.yaml vs docker-compose-installed.yaml. As advised I was to use docker-compose-installed.yaml for a production deployment but it's not working at all, so need some assistance here.

LedgerXYZ (Sat, 01 Dec 2018 22:12:44 GMT):
@zac can you please describe (loosely or focused) how the sawtooth supply chain architecture flows into deployment

LedgerXYZ (Sat, 01 Dec 2018 22:16:25 GMT):
I especially want to know how `validators` are served by the supply chain tp. The docs doesn't say, do you officially recommend ubuntu 16.04 or docker containers for deployment. If yes, what is being deployed and what are similar tools in the wild today that can help one wrap their mind around this concept

mikd (Fri, 07 Dec 2018 21:48:23 GMT):
Has joined the channel.

Gokul_Narayan (Sat, 08 Dec 2018 09:35:58 GMT):
Has joined the channel.

ayanfecrown (Sat, 15 Dec 2018 10:31:14 GMT):
Has joined the channel.

ayanfecrown (Sat, 15 Dec 2018 10:31:26 GMT):
Hello all

ayanfecrown (Sat, 15 Dec 2018 10:32:04 GMT):
i just tried to setup the lastest code on git am getting the following error

ayanfecrown (Sat, 15 Dec 2018 10:32:37 GMT):
`ERROR: Service 'shell' failed to build: manifest for hyperledger/sawtooth-shell:nightly not found`

amolk (Sat, 15 Dec 2018 11:07:24 GMT):
Has joined the channel.

AVetter (Mon, 17 Dec 2018 07:54:45 GMT):
Has joined the channel.

raccoonrat (Mon, 24 Dec 2018 04:18:35 GMT):
Has joined the channel.

LedgerXYZ (Thu, 27 Dec 2018 16:14:43 GMT):
@ayanfecrown can you post your `docker file` or `docker compose` file. Feel free to redact any info you deem private

LedgerXYZ (Thu, 27 Dec 2018 16:18:00 GMT):
Also consider I found that sometimes you have to re-login to docker (yes, I know you've logged in before).

LedgerXYZ (Thu, 27 Dec 2018 16:19:32 GMT):
command: `docker login` to login again

LedgerXYZ (Thu, 27 Dec 2018 16:20:17 GMT):
Lastly you're better off posting in the the sawtooth channel for faster responses because it seems to be more active

amolk (Fri, 28 Dec 2018 09:13:53 GMT):
@LedgerXYZ that issue's been resolved. @ayanfecrown ran into it during the Hyperledger hackathon. The resolution is to change 'nightly' to 'latest' in the Dockerfile and also change 'bionic' to 'xenial'. sawtooth-shell had still not been ported to bionic and the nightly build wasn't available.

LedgerXYZ (Fri, 28 Dec 2018 16:16:07 GMT):
@amolk awesome. I'm happy it worked out. I'm also happy that you mentioned the bionic issues because I planned to update to that version in January.

amolk (Fri, 28 Dec 2018 16:18:05 GMT):
The nightly for sawtooth-shell will be on bionic.

sandman (Fri, 04 Jan 2019 06:02:22 GMT):
Has joined the channel.

sandman (Fri, 04 Jan 2019 10:33:52 GMT):
i am trying to run sawtooth supply chain but getting http 500 error on assert creation. Using code from master with ISOLATION_ID=latest, Distro=xenial and docker-compose-installed file. Can i use any other branch/release tag/image version.

varinder (Sat, 05 Jan 2019 00:17:52 GMT):
Has joined the channel.

syk007 (Thu, 10 Jan 2019 06:15:44 GMT):
Has joined the channel.

st (Thu, 10 Jan 2019 20:51:29 GMT):
Has joined the channel.

varinder (Sat, 12 Jan 2019 00:22:27 GMT):
Are there known issues with running education-supply-chain.. out of the box? I have prereqs (docker, docker compose) installed and get the below error when running the codebase off of github. I assumed the missing dependencies install themselves but I ran ( sudo apt-get install -y --allow-unauthenticated -q curl python3-pip python3-sawtooth-cli python3-sawtooth-sdk python3-sawtooth-rest-api) by itself and still got below error on step 3 with docker-compose up Step 3/9 : RUN apt-get install -y --allow-unauthenticated -q curl python3-pip python3-sawtooth-cli python3-sawtooth-sdk python3-sawtooth-rest-api ---> Running in d8d1a584f7ef Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package curl E: Unable to locate package python3-pip E: Unable to locate package python3-sawtooth-cli E: Unable to locate package python3-sawtooth-sdk E: Unable to locate package python3-sawtooth-rest-api ERROR: Service 'simple-supply-shell' failed to build: The command '/bin/sh -c apt-get install -y --allow-unauthenticated -q curl python3-pip python3-sawtooth-cli python3-sawtooth-sdk python3-sawtooth-rest-api' returned a non-zero code: 100 Yet, when I run the command by itself - I get no errors: $ apt-get install -y --allow-unauthenticated -q curl python3-pip python3-sawtooth-cli python3-sawtooth-sdk python3-sawtooth-rest-api Reading package lists... Building dependency tree... Reading state information... curl is already the newest version (7.47.0-1ubuntu2.11). python3-pip is already the newest version (8.1.1-2ubuntu0.4). python3-sawtooth-cli is already the newest version (1.1.2-1). python3-sawtooth-rest-api is already the newest version (1.1.2-1). python3-sawtooth-sdk is already the newest version (1.1.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I am running this on Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial

danintel (Sat, 12 Jan 2019 01:57:27 GMT):
@varinder one bug fix has not been integrated... See https://github.com/hyperledger/education-sawtooth-simple-supply/pull/25 ... Off-hand your problem seens different but add the fix anyway and see.

amiec (Sat, 12 Jan 2019 16:08:44 GMT):
Has joined the channel.

varinder (Mon, 14 Jan 2019 18:22:54 GMT):
@danintel thanks, I tried with that fix but same error

amundson (Tue, 15 Jan 2019 18:42:16 GMT):
Please come join us on #grid, which will be the primary channel for Hyperledger Grid, the new project focused on supply chain

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Supply Chain REST API will be at http://localhost:8020 *http://localhost:8020/* *Cannot GET /* Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user -* it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) *supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:19:54 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304 -* I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue) @danintel

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Supply Chain REST API will be at http://localhost:8020 *http://localhost:8020/* *Cannot GET /* Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user - *it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) *supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:19:54 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304 -* I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue) @danintel

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Supply Chain REST API will be at http://localhost:8020 *http://localhost:8020/* *Cannot GET /* Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user - *it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) *supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:19:54 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304* I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue) @danintel

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Supply Chain REST API will be at http://localhost:8020 *http://localhost:8020/* *Cannot GET /* Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user - *it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) *supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:26 +0000] "GET /api/agents HTTP/1.1" 304 - supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:27 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304 - supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:29 +0000] "GET /api/agents HTTP/1.1" 304 - * I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue) @danintel

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Supply Chain REST API will be at http://localhost:8020 *http://localhost:8020/* *Cannot GET /* Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user - *it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) *supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:26 +0000] "GET /api/agents HTTP/1.1" 304 - supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:27 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304 - supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:29 +0000] "GET /api/agents HTTP/1.1" 304 -* I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue) @danintel

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Supply Chain REST API will be at http://localhost:8020 *http://localhost:8020/* *Cannot GET /* Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user - *it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:26 +0000] "GET /api/agents HTTP/1.1" 304 - supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:27 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304 - supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:29 +0000] "GET /api/agents HTTP/1.1" 304 - I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue) @danintel

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
@danintel I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Supply Chain REST API will be at http://localhost:8020 *http://localhost:8020/* *Cannot GET /* Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user - *it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:26 +0000] "GET /api/agents HTTP/1.1" 304 - supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:27 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304 - supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:29 +0000] "GET /api/agents HTTP/1.1" 304 - I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue)

varinder (Thu, 17 Jan 2019 01:32:01 GMT):
@danintel I am running https://github.com/hyperledger/sawtooth-supply-chain/tree/v0.10.3 in Ubuntu 16.04. I am able to start the docker-compose but keep seeing the error when I open the below APIs -> Sawtooth's blockchain REST API will be available at http://localhost:8024 *The webpage at http://localhost:8024/ might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKET_NOT_CONNECTED* When I run the Asset Client, I am able to create an account, create assets.. but when I transfer the asset to another user - *it doesn't actually transfer the asset. The asset remains with the original owner. * This is what I see in my terminal: (repeating error) supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:26 +0000] "GET /api/agents HTTP/1.1" 304 - supply-server | Received GET request for /records?recordType=asset from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:27 +0000] "GET /api/records?recordType=asset HTTP/1.1" 304 - supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [17/Jan/2019:01:33:29 +0000] "GET /api/agents HTTP/1.1" 304 - I suspect the error is related to ports and/or firewall. Any resolutions for this type of issue? (NOTE: i am running the above github code as is. The only change I had to make was increase the timeout time in the yaml files otherwise I was getting timeouts. Shouldn't have impacted the above issue)

danintel (Thu, 17 Jan 2019 17:53:13 GMT):
@varinder See channel #grid for a response. That is the new channel for Supply Chain.

RealDeanZhao (Fri, 18 Jan 2019 02:13:37 GMT):
Has joined the channel.

RahulToraskar (Tue, 22 Jan 2019 04:35:03 GMT):
Has joined the channel.

phinpope (Tue, 22 Jan 2019 09:47:38 GMT):
Has joined the channel.

amolk (Tue, 22 Jan 2019 09:57:31 GMT):
@muniyaraj, you need to edit the Dockerfile inside sawtooth-shell. First, change 'nightly' to 'latest'. If there are still errors, try changing 'bionic' to 'xenial' on the second line.

muniyaraj (Tue, 22 Jan 2019 09:57:31 GMT):
Has joined the channel.

amolk (Tue, 22 Jan 2019 09:58:39 GMT):
bumper-nightly will work as well, as pointed in the other channel.

muniyaraj (Tue, 22 Jan 2019 09:59:01 GMT):
@amolk But nightly not mentioned anywhere

muniyaraj (Tue, 22 Jan 2019 09:59:15 GMT):
shell: image: supply-shell container_name: supply-shell build: context: . dockerfile: shell/Dockerfile args: - http_proxy - https_proxy - no_proxy volumes: - .:/sawtooth-supply-chain - /sawtooth-supply-chain/asset_client/node_modules - /sawtooth-supply-chain/fish_client/node_modules - /sawtooth-supply-chain/server/node_modules depends_on: - rethink - rest-api environment: - VALIDATOR_URL=tcp://validator:4004 - DB_HOST=rethink - SERVER=http://server:3000 - 'http_proxy=${http_proxy}' - 'https_proxy=${https_proxy}' - 'no_proxy=rest-api,server,eth0,validator,${no_proxy}' command: | bash -c " cd asset_client/ && npm run build && cd - && cd fish_client/ && npm run build && cd - && if [ ! -f /root/.sawtooth/keys/root.priv ]; then sawtooth keygen && cd server/ && npm run init && npm run make-asset && npm run make-fish && npm run seed-sample-assets && npm run seed-sample-fish && cd - fi; tail -f /dev/null "

amolk (Tue, 22 Jan 2019 10:00:35 GMT):
cd shell

amolk (Tue, 22 Jan 2019 10:00:38 GMT):
vi Dockerfile

muniyaraj (Tue, 22 Jan 2019 10:13:02 GMT):
yes thank you so much it is working

muniyaraj (Tue, 22 Jan 2019 10:13:12 GMT):
@amolk Thank you so much

rinor (Tue, 22 Jan 2019 17:54:59 GMT):
Has joined the channel.

bdjidi (Tue, 22 Jan 2019 18:02:30 GMT):
Has joined the channel.

PaulaBanks (Wed, 23 Jan 2019 10:15:15 GMT):
Has joined the channel.

PaulaBanks (Wed, 23 Jan 2019 10:18:28 GMT):
Hi everyone. Is there somewhere I can find documentation on how to this fishnet project is collecting IoT data and integrating it into sawtooth

danintel (Wed, 23 Jan 2019 18:53:45 GMT):
As a reminder, the Supply Chain chat channel has moved to #grid

danintel (Wed, 23 Jan 2019 18:56:19 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=ZsiJ6RWtZNaLuG5G3) @PaulaBanks AFAIK, there is a web client, but no IoT client.

danintel (Wed, 23 Jan 2019 18:56:53 GMT):
*As a friendly reminder, the Supply Chain chat channel has moved to #grid *

PaulaBanks (Thu, 24 Jan 2019 04:23:22 GMT):
oh, thanks @danintel

muniyaraj (Thu, 24 Jan 2019 10:09:01 GMT):
Hi Team, How can we run documentation in sawtooth file?

muniyaraj (Thu, 24 Jan 2019 10:09:25 GMT):
sry supply chain documentation

muniyaraj (Thu, 24 Jan 2019 10:10:28 GMT):
I want to build supplychain documentation . can anyone please help me

muniyaraj (Thu, 24 Jan 2019 10:10:39 GMT):
how to build the documentation

paparent (Thu, 24 Jan 2019 14:28:43 GMT):
Has joined the channel.

paparent (Thu, 24 Jan 2019 14:30:38 GMT):
Hi ! As reading the backlog, is the sawtooth-supply-chain project has stopped in favor of sawtooth-grid ?

jsmitchell (Thu, 24 Jan 2019 14:31:55 GMT):
No

jsmitchell (Thu, 24 Jan 2019 14:32:45 GMT):
Grid is based on sawtooth supply chain to start with, but will likely diverge quickly

paparent (Thu, 24 Jan 2019 14:33:34 GMT):
" a friendly reminder, the Supply Chain chat channel has moved to #grid *" Sorry I'm confused :) I'm asking because i'm working on a Proof of concept using supply-chain and wanted to know if it's a dead project :)

jsmitchell (Thu, 24 Jan 2019 14:34:12 GMT):
I don’t know why @danintel said that

paparent (Thu, 24 Jan 2019 14:37:17 GMT):
ok! thanks ! Anyone here uses Windows a dev platform, and isn't able to start the Docker environment? Starting using master doesn't work because it seems to miss an image from sawtooth-core.. and trying v0.10.3, it kinda start, but the JS bundle from asset-client is doing free games! (some lines appear/disappear when I refresh!)... pretty weird :(

danintel (Thu, 24 Jan 2019 16:50:16 GMT):
@jsmitchell Sorry I was misinformed. I read about #grid and that #sawtooth-supply-chain will be deleted after a few weeks.

jsmitchell (Thu, 24 Jan 2019 16:53:48 GMT):
who said #sawtooth-supply-chain will be deleted?

danintel (Thu, 24 Jan 2019 16:54:26 GMT):
I'm searching for the message and haven't found it yet.

danintel (Thu, 24 Jan 2019 16:54:26 GMT):
See #grid for end of Jan. 17. My mistake--both repos are staying!

danintel (Thu, 24 Jan 2019 16:57:44 GMT):
Found it: are we gonna decom the supply-chain repo? amundson Moderator Technical Ambassador 2:47 PM not immediately it may continue to serve as a good application example, if we deviate significantly from it w/Grid (which seems very possible)

danintel (Thu, 24 Jan 2019 16:57:44 GMT):
Found it on #grid: `are we gonna decom the supply-chain repo? amundson Moderator Technical Ambassador 2:47 PM not immediately it may continue to serve as a good application example, if we deviate significantly from it w/Grid (which seems very possible)`

danintel (Thu, 24 Jan 2019 16:57:44 GMT):
Found it on #grid: ```are we gonna decom the supply-chain repo? amundson Moderator Technical Ambassador 2:47 PM not immediately it may continue to serve as a good application example, if we deviate significantly from it w/Grid (which seems very possible)```

danintel (Thu, 24 Jan 2019 16:57:44 GMT):
@mikeborg The current version of sawtooth-supply-chain repo uses Ubuntu 18 (Bionic) and the nightly (bleeding edge) Sawtooth 1.2. I prefer something more stable--Sawtooth 1.1 (latest release, "Bumper"), which is only supported on Ubuntu 16 (Xenial). To patch sawtooth-supply-chain, I do these two steps: ```git clone https://github.com/hyperledger/sawtooth-supply-chain cd sawtooth-supply-chain git diff 50c404c >bionic.patch patch --dry-run -R -p1

danintel (Thu, 24 Jan 2019 16:57:44 GMT):
@mikeborg The current version of sawtooth-supply-chain repo uses Ubuntu 18 (Bionic) and the nightly (bleeding edge) Sawtooth 1.2. I prefer something more stable--Sawtooth 1.1 (latest release, "Bumper"), which is only supported on Ubuntu 16 (Xenial). To patch sawtooth-supply-chain, follow these steps: ```git clone https://github.com/hyperledger/sawtooth-supply-chain cd sawtooth-supply-chain git diff 50c404c >bionic.patch patch --dry-run -R -p1

danintel (Thu, 24 Jan 2019 16:58:27 GMT):
Thanks for the clarification--we're keeping both, apparently.

mikeborg (Tue, 29 Jan 2019 23:25:49 GMT):
Has joined the channel.

mikeborg (Tue, 29 Jan 2019 23:26:08 GMT):
@danintel I'll give that a try. Thank you!

danintel (Tue, 29 Jan 2019 23:38:05 GMT):
FYI, live demos of sawtooth-supply-chain are available at https://demo.bitwise.io/fish/ and https://demo.bitwise.io/

mikeborg (Tue, 29 Jan 2019 23:51:40 GMT):
@danintel Your patch worked fine.

mcutrer (Wed, 30 Jan 2019 01:01:21 GMT):
Has joined the channel.

mcutrer (Wed, 30 Jan 2019 01:02:28 GMT):
are there any instructions or links on how to use the Hyperledger Sawtooth Supply Chain instance on AWS?

mcutrer (Wed, 30 Jan 2019 01:02:41 GMT):
Any help would be greatly appreciated.

rranjan3 (Wed, 30 Jan 2019 01:53:24 GMT):
Has joined the channel.

muniyaraj (Wed, 30 Jan 2019 08:42:18 GMT):
hi all, Can you please tell how to use sawtooth explorer Have any guidance for that?

robinrob (Wed, 30 Jan 2019 19:41:34 GMT):
Has joined the channel.

danintel (Wed, 30 Jan 2019 20:42:50 GMT):
@muniyaraj See #sawtooth for an answer

danintel (Wed, 30 Jan 2019 20:43:47 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=cZmMXcrn77YZXmdg3) @mcutrer No. There are instructions for Sawtooth on AWS at https://sawtooth.hyperledger.org/docs/core/releases/latest/app_developers_guide/aws.html The Sawtooth Supply Chain AWS image, for the benefit of others, is at https://aws.amazon.com/marketplace/pp/B077FLR7V5

danintel (Thu, 31 Jan 2019 02:14:12 GMT):
@mcutrer I will see what i can come up with for specific AWS Sipply Chsin instructions

danintel (Thu, 31 Jan 2019 02:14:12 GMT):
@mcutrer I will see what I can come up with for specific AWS Supply Chain instructions

mcutrer (Thu, 31 Jan 2019 02:15:20 GMT):
Thank you! That would be really helpful! @danintel

danintel (Sat, 02 Feb 2019 00:01:38 GMT):
@mcutrer (and others) *Using AWS Sawtooth Marketplace* I created a document showing how to create an AWS instance of Sawtooth Marketplace, how to login the website, and how to login with SSH. The document is here: https://gist.github.com/danintel/04c9a6b870730842c30454a8cc1e594e

danintel (Sat, 02 Feb 2019 00:01:38 GMT):
@mcutrer (and others) *Using AWS Sawtooth Supply Chain* I created a document showing how to create an AWS instance of Sawtooth Marketplace, how to login the website, and how to login with SSH. The document is here: https://gist.github.com/danintel/04c9a6b870730842c30454a8cc1e594e

danintel (Sat, 02 Feb 2019 00:01:38 GMT):
@mcutrer (and others) *Using AWS Sawtooth Supply Chain* I created a document showing how to create an AWS instance of Sawtooth Supply Chain, how to login the website, and how to login with SSH. The document is here: https://gist.github.com/danintel/04c9a6b870730842c30454a8cc1e594e

rranjan3 (Sat, 02 Feb 2019 02:58:50 GMT):
^ @danintel Could be included in in supply chain repo.

danintel (Sat, 02 Feb 2019 05:45:00 GMT):
I think the doc it is too specific and a PR with it will not be accepted. I will link to it from the Sawtooth FAQ next week.

AmimKnabben (Sun, 03 Feb 2019 16:04:16 GMT):
Has joined the channel.

AmimKnabben (Sun, 03 Feb 2019 16:05:25 GMT):
```diff --git a/shell/Dockerfile b/shell/Dockerfile index 7ea0caba..b57c2db1 100644 --- a/shell/Dockerfile +++ b/shell/Dockerfile @@ -13,10 +13,10 @@ # limitations under the License. # ------------------------------------------------------------------------------ -FROM hyperledger/sawtooth-shell:nightly +FROM hyperledger/sawtooth-shell:bumper-nightly # Install Python, Node.js, and Ubuntu dependencies -RUN echo "deb http://repo.sawtooth.me/ubuntu/1.0/stable bionic universe" >> /etc/apt/sources.list \ +RUN echo "deb http://repo.sawtooth.me/ubuntu/1.0/nightly xenial universe" >> /etc/apt/sources.list \ && (apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 44FC67F19B2466EA \ || apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 44FC67F19B2466EA) \ && apt-get update \ ```

AmimKnabben (Sun, 03 Feb 2019 16:06:00 GMT):
has the following patch to build the master version of the project, should I open a PR or they are temporary changes?

danintel (Sun, 03 Feb 2019 23:00:39 GMT):
@AmimKnabben The repo supports Bionic (Ubuntu LTS 18) and Sawtooth Nightly development (Sawtooth 1.2). See my message here on 2019-01-24 on how to reverse the changes so it works with Xenial (Ubuntu LTS 16) and Sawtooth 1.1 ("Bumper" or "latest").

prabu3192 (Mon, 04 Feb 2019 05:59:32 GMT):
Has joined the channel.

paparent (Wed, 06 Feb 2019 16:22:05 GMT):
Hi, I've done some benchmarking using custom tool I just did (I looked at Caliper but I don't understand it! :( ) ... I know about back pressure test, so I implemented a backoff retrying.. So : for about 250 create_record, I get between 3-6 item created per seconds.. I tested it locally on docker, and not on a machine on AWS... It seems quite low, isn't it ?

amundson (Wed, 06 Feb 2019 21:50:51 GMT):
@paparent we see a higher rate than that, but it is very sensitive to how the testing is done obviously. we use the workload tool within sawtooth-core to submit intkey or xo transactions typically. you could write a supply chain backend for it if you wanted to do it the same way (though, this would better be done within the context of grid perhaps). we are currently working on a high-performance version of our transaction processing capability, so stay tuned, this will look a lot different in a couple months as we shift that part of the core code to a Rust implementation.

kaushikmehta (Thu, 07 Feb 2019 01:07:37 GMT):
Has joined the channel.

DatNguyen (Thu, 14 Feb 2019 06:30:22 GMT):
Has joined the channel.

sebastiantf (Sat, 23 Feb 2019 08:14:21 GMT):
Has joined the channel.

sebastiantf (Sat, 23 Feb 2019 08:14:26 GMT):
Which is best for a farm to fork food supply chain system? Sawtooth, Fabric or just Composer?

amundson (Sun, 24 Feb 2019 00:42:53 GMT):
@sebastiantf Hyperledger Grid is a new Hyperledger project focused on supply chain. We expect to see a lot of activity there over the next year.

sebastiantf (Sun, 24 Feb 2019 12:06:37 GMT):
[ ](https://chat.hyperledger.org/channel/sawtooth-supply-chain?msg=7bZHPv63yBkNkMqTe) @amundson We're actually trying to implement the project this week/month so...

jsmitchell (Sun, 24 Feb 2019 14:43:26 GMT):
I believe Composer is an abandoned project, and as far as I know any supply chain work announced on Fabric are based on proprietary closed-source software. The sawtooth-supply-chain repo has a good example of seafood track and trace with automated sensor readings for location, temperature, etc. it might be worth looking into.

varinder (Tue, 26 Feb 2019 04:32:08 GMT):
Does anyone have experience with using the rest api to submit transactions to supply-chain tp? Is there any documentation/examples on how the payload/transactions/batches should be developed before sent to the validator via the rest call?

varinder (Tue, 26 Feb 2019 17:52:56 GMT):
Basically what I am looking for is an example process to generate a batch that can be submitter via POST/RestAPI to validator. I understand this is the command to do so "sawtooth batch submit The sawtooth batch submit subcommand sends one or more Batches to the Sawtooth REST API to be submitted to the validator. The input is a binary file with a binary-encoded BatchList protobuf, which can contain one or more batches with any number of transactions. The --wait option indicates that results should not be returned until processing is complete, with an optional timeout specified in seconds." (https://sawtooth.hyperledger.org/docs/core/releases/1.0/cli/sawtooth.html#sawtooth-batch-submit)

varinder (Tue, 26 Feb 2019 17:52:56 GMT):
Basically what I am looking for is an example process to generate a batch that can be submitted via POST/RestAPI to validator. I understand this is the command to do so "sawtooth batch submit The sawtooth batch submit subcommand sends one or more Batches to the Sawtooth REST API to be submitted to the validator. The input is a binary file with a binary-encoded BatchList protobuf, which can contain one or more batches with any number of transactions. The --wait option indicates that results should not be returned until processing is complete, with an optional timeout specified in seconds." (https://sawtooth.hyperledger.org/docs/core/releases/1.0/cli/sawtooth.html#sawtooth-batch-submit)

paparent (Tue, 05 Mar 2019 19:56:16 GMT):
Hi ! I've around 35 items in the blockchain,, when I hit the API `/api/records?recordType=assetv2` from the Assert client frontend, request take around 6.5secs... I added 3 other object, and now it take 7.5s !.... Shouldn't it be faster, especially it query rethinkdb ?

itsmemax (Thu, 07 Mar 2019 15:08:24 GMT):
Has joined the channel.

menghuanzhixing (Fri, 08 Mar 2019 12:02:22 GMT):
Has joined the channel.

menghuanzhixing (Fri, 08 Mar 2019 12:25:49 GMT):
When I require a module in a .js file, which is not in the fish_client folder at the installed Sawtooth Supply Chain, then I run docker-compose up again, and there is an error that doesn't find the module, then I add the module dependencies at the package.json file and install the module through NPM, the error present again. What's the reason about it?

menghuanzhixing (Fri, 08 Mar 2019 12:35:35 GMT):
When I require a module in a .js file, which is not in the fish_client folder at the installed Sawtooth Supply Chain, then I run docker-compose up again, and there is an error that doesn't find the module, then I add the module dependencies at the package.json file and install the module through NPM, the error present again. What's the reason about it?``` `supply-shell | ERROR in ./src/components/data.js supply-shell | Module not found: Error: Can't resolve 'baidumap' in '/sawtooth-supply-chain/fish_client/src/components' supply-shell | @ ./src/components/data.js 22:23-42 supply-shell | @ ./src/views/property_detail.js supply-shell | @ ./src/main.js supply-shell | npm ERR! code ELIFECYCLE supply-shell | npm ERR! errno 2 supply-shell | npm ERR! fish_net@0.0.0 build: `npm run generate-proto-files && webpack --env production` supply-shell | npm ERR! Exit status 2 supply-shell | npm ERR! supply-shell | npm ERR! Failed at the fish_net@0.0.0 build script.` ```

GovindPradeep (Wed, 13 Mar 2019 04:45:25 GMT):
Has joined the channel.

DennisSam (Fri, 22 Mar 2019 11:43:31 GMT):
Has joined the channel.

kh.nguyen (Wed, 27 Mar 2019 00:22:26 GMT):
Has joined the channel.

Psypher246 (Thu, 28 Mar 2019 07:36:49 GMT):
Hi all, I've got a challenge with using the Sawtooth Supply Chain Docker Compose files with regards to the differences between `docker-compose.yaml` and `docker-compose-installed.yaml`. In the `docker-compose.yaml` file the shell container runs the following commands in order to create the asset records types and seed some samples into the state (this is my rudimentary understanding and from trial and error trying to get things to work) npm run make-asset && npm run make-fish && npm run seed-sample-assets && npm run seed-sample-fish &&

Psypher246 (Thu, 28 Mar 2019 07:36:49 GMT):
Hi all, I've got a challenge with using the Sawtooth Supply Chain Docker Compose files with regards to the differences between `docker-compose.yaml` and `docker-compose-installed.yaml`. In the `docker-compose.yaml` file the shell container runs the following commands in order to create the asset records types and seed some samples into the state (this is my rudimentary understanding and from trial and error trying to get things to work) ```npm run make-asset && npm run make-fish && npm run seed-sample-assets && npm run seed-sample-fish &&```

Psypher246 (Thu, 28 Mar 2019 07:42:28 GMT):
Hi all, I've got a challenge with using the Sawtooth Supply Chain Docker Compose files with regards to the differences between `docker-compose.yaml` and `docker-compose-installed.yaml`. In the `docker-compose.yaml` file the shell container runs the following commands in order to create the asset records types and seed some samples into the state (this is my rudimentary understanding and from trial and error trying to get things to work) ```npm run make-asset && npm run make-fish && npm run seed-sample-assets && npm run seed-sample-fish &&``` But all of these steps are missing from the `docker-compose-installed.yaml` file, so in order to get your app to work, and not just receive an error in the logs about unknown asset type, you need to run a shell and manually run these steps. Is there a better way to do this that can be fully automated? Ideally without having to run a shell container? Can the asset & fish records types be created with the supply TP instead? What else are these scripts doing that are important? Thanks!

amanjain (Thu, 28 Mar 2019 12:48:08 GMT):
Has joined the channel.

Salaria_77 (Thu, 28 Mar 2019 12:52:47 GMT):
Has joined the channel.

adityasingh177 (Sat, 30 Mar 2019 15:11:45 GMT):
Has joined the channel.

Mohit_Python (Mon, 01 Apr 2019 17:15:13 GMT):
Has joined the channel.

ruairih (Tue, 02 Apr 2019 18:50:03 GMT):
Has joined the channel.

JulianGordonHK (Tue, 09 Apr 2019 06:51:58 GMT):
Has joined the channel.

CarolinNeumann (Wed, 10 Apr 2019 17:35:58 GMT):
Has joined the channel.

varubasi77 (Tue, 18 Jun 2019 18:55:31 GMT):
Has joined the channel.

desktophero (Tue, 18 Jun 2019 19:49:56 GMT):
Has joined the channel.

ozaiter (Fri, 28 Jun 2019 22:22:19 GMT):
Has joined the channel.

BobaFett (Mon, 01 Jul 2019 03:00:53 GMT):
Has joined the channel.

kenty (Thu, 04 Jul 2019 16:11:30 GMT):
Has joined the channel.

invaliduser (Sat, 13 Jul 2019 13:22:44 GMT):
Has joined the channel.

jamesbarry (Wed, 31 Jul 2019 16:27:07 GMT):
Has joined the channel.

paparent (Mon, 05 Aug 2019 12:57:00 GMT):
Has left the channel.

jpeterseni35 (Mon, 05 Aug 2019 18:35:19 GMT):
Has joined the channel.

mr_a2019 (Tue, 13 Aug 2019 09:43:05 GMT):
Has joined the channel.

mr_a2019 (Tue, 13 Aug 2019 09:43:07 GMT):
Hello, I am running hyperledger sawtooth using docker and whenever I run docker-compose up I get the following error from the supply-shell: Creating Records . . . supply-shell | StatusCodeError: 413 - {"type":"Buffer","data":[123, ...]} The data array has length of 50. I get this error whenever I add a property to the properties array in sample_data.json and there are currently 50 properties defined in the sample data. When I remove the added property, it continues to work. I am using a different node api outside of the docker environment to fetch the records from rethnkdb. Thanks in advance

mr_a2019 (Tue, 13 Aug 2019 10:42:48 GMT):
I have managed to fix the issue, see https://stackoverflow.com/questions/19917401/error-request-entity-too-large

amanjain (Thu, 05 Sep 2019 11:39:59 GMT):
Has left the channel.

mr_a2019 (Mon, 09 Sep 2019 10:48:57 GMT):
Hello, is there any way to change the record properties datatype so instead of being an array it is an object with key value pairs?

amundson (Tue, 17 Sep 2019 20:28:03 GMT):
@mr_a2019 there are some examples of that in grid product (which is very similar), where there is a list of key,value pairs

hazan (Sat, 28 Sep 2019 17:04:04 GMT):
Has joined the channel.

hazan (Sat, 28 Sep 2019 17:04:04 GMT):
Hi All! I am trying to setup the sawtooth-supplychain environment. I am currently stuck at a bug when I do docker-compose up at step 9 I am getting an error for splice_json: /bin/sh: 1: bin/splice_json: Permission denied -- I have already done chmod +x ./bin/ and chmod 777 and everything that route. I keep getting permission denied. Any guidance is appreciated!

hazan (Sat, 28 Sep 2019 17:04:04 GMT):
Hi All! I am trying to setup the sawtooth-supplychain environment. I am currently stuck at a bug when I do *docker-compose up* at step 9 I am getting an error for* splice_json: /bin/sh: 1: bin/splice_json: Permission denied* -- I have already done chmod +x ./bin/ and chmod 777 and everything that route. I keep getting permission denied. Any guidance is appreciated!

mr_a2019 (Wed, 02 Oct 2019 11:46:26 GMT):
I managed to find out how to do this Inside core_types.json, we define a struct data type object inside the properties array, and then insert our data type objects inside the structProperties array like so: { “name”: “data”, “dataType”: 6, “structProperties”: [ { “name”: “exampleProperty”, “dataType”: 4, } ] } Then in sample_data.json, we can add sample data by add our data objects into the structValues array like so: { “name”: “data”, “dataType”: 6, “structValues”: [ { “name”: “exampleProperty”, “dataType”: 4, “stringValue”: “Some value” } ] } We can also nest a struct data type within another struct. Hope this helps

mr_a2019 (Wed, 02 Oct 2019 11:47:27 GMT):
I managed to find out how to do this Inside core_types.json, we define a struct data type object inside the properties array, and then insert our data type objects inside the structProperties array like so: { “name”: “data”, “dataType”: 6, “structProperties”: [ { “name”: “exampleProperty”, “dataType”: 4, } ] } Then in sample_data.json, we can add sample data by add our data objects into the structValues array like so: { “name”: “data”, “dataType”: 6, “structValues”: [ { “name”: “exampleProperty”, “dataType”: 4, “stringValue”: “Some value” } ] } We can also nest a struct data type within another struct. Hope this helps

mr_a2019 (Wed, 02 Oct 2019 11:47:59 GMT):
I managed to find out how to do this Inside core_types.json, we define a struct data type object inside the properties array, and then insert our data type objects inside the structProperties array like so: { “name”: “data”, “dataType”: 6, “structProperties”: [ { “name”: “exampleProperty”, “dataType”: 4, } ] } Then in sample_data.json, we can add sample data by add our data objects into the structValues array like so: { “name”: “data”, “dataType”: 6, “structValues”: [ { “name”: “exampleProperty”, “dataType”: 4, “stringValue”: “Some value” } ] } We can also nest a struct data type within another struct. Hope this helps

mr_a2019 (Wed, 02 Oct 2019 11:50:34 GMT):
Hey there, I am using sawtooth-supply-chain, has anyone experienced a noticeable performance improvement by changing the core types data type to STRUCT?

Razorneck (Thu, 24 Oct 2019 15:01:07 GMT):
Has joined the channel.

Razorneck (Thu, 24 Oct 2019 15:01:08 GMT):
Hi, does anyone know how to add the supply-chain transaction processor to sawtooth on ubuntu?

Razorneck (Thu, 24 Oct 2019 15:53:38 GMT):
Or has anyone experience in connecting two hosts of sawtooth-supply chain in docker?

sanket1211 (Wed, 06 Nov 2019 11:49:52 GMT):
Has joined the channel.

AmimKnabben (Fri, 29 Nov 2019 01:11:12 GMT):
Has left the channel.

atirekg (Wed, 18 Dec 2019 13:37:24 GMT):
Has joined the channel.

Tomomi.Yamano (Sun, 02 Feb 2020 13:20:07 GMT):
Has joined the channel.

Tomomi.Yamano (Sun, 02 Feb 2020 13:20:10 GMT):
Hi guys, i am interested in sawtooth supply chin. anyone here knows any use case in real world ?

Tomomi.Yamano (Sun, 02 Feb 2020 13:20:10 GMT):
Hi guys, i am interested in sawtooth supply cha:relaxed: in. anyone here knows any use case in real world ?🙂 more specifically, coutnerfeits prevention, traceability in the pharmaceutical industry,

Tomomi.Yamano (Sun, 02 Feb 2020 13:20:10 GMT):
Hi guys, i am interested in sawtooth supply chain. Anyone here may know any use case in real world ?🙂 more specifically, coutnerfeits prevention, traceability in the pharmaceutical industry,

arsulegai (Sun, 02 Feb 2020 14:28:06 GMT):
@Tomomi.Yamano The supply-chain is one example implementation. You can use for the case you need.

Tomomi.Yamano (Sun, 02 Feb 2020 14:29:59 GMT):
@arsulegai thanks for your comment. any samples you may know which has been already implemeted at POC level?

yeiyei (Tue, 03 Mar 2020 15:33:50 GMT):
Has joined the channel.

n3s7l3 (Mon, 18 May 2020 11:56:36 GMT):
Has joined the channel.

n3s7l3 (Mon, 18 May 2020 11:56:40 GMT):
Hi everyone, I'm new to the blockchain development, i started playing around with Hyperledger Sawtooth Supply Chain application, and i need to update the Asset record from the outside of the network (using for example "curl"), can you guys pls provide me the steps to do this task. Thanks.

rajesh_kumar_p (Thu, 04 Jun 2020 14:33:00 GMT):
Has joined the channel.

hidura (Thu, 04 Jun 2020 22:59:37 GMT):
Has joined the channel.

hidura (Sun, 14 Jun 2020 03:06:19 GMT):
Hello everyone is there a way to modify the protos without rebooting the blockchain?

hidura (Sun, 14 Jun 2020 03:06:59 GMT):
I need to modify the code of the protos to add new fields but for that I can't be rebooting Everytime the docker

jmbarry (Tue, 16 Jun 2020 17:30:56 GMT):
Has joined the channel.

amundson (Wed, 17 Jun 2020 14:16:54 GMT):
@hidura try asking about developer workflows in #sawtooth

hidura (Wed, 17 Jun 2020 14:47:12 GMT):
Thanks @amundson

tranlien9999999 (Wed, 02 Dec 2020 12:48:47 GMT):
Has joined the channel.

tranlien9999999 (Wed, 02 Dec 2020 12:48:47 GMT):
hello

tranlien9999999 (Wed, 02 Dec 2020 13:42:20 GMT):
hihuuhu

ksanjayk (Sat, 17 Apr 2021 22:30:35 GMT):
Has joined the channel.

ksanjayk (Tue, 20 Apr 2021 12:41:17 GMT):
I am trying to run education-sawtooth-simple-supply and i am getting error . sawtooth-simple-supply-rest-api , sawtooth-simple-supply-tp , sawtooth-simple-supply-subscriber are exiting as soon as they are bought up

ksanjayk (Tue, 20 Apr 2021 12:41:49 GMT):

Screenshot from 2021-04-18 03-45-06.png

ksanjayk (Tue, 20 Apr 2021 12:41:55 GMT):

Screenshot from 2021-04-18 03-45-58.png

gusBar (Thu, 06 May 2021 05:13:44 GMT):
Has joined the channel.

lcvalves (Sun, 30 May 2021 16:39:45 GMT):
Has joined the channel.

indranil32 (Wed, 23 Jun 2021 05:14:55 GMT):
Has joined the channel.

indranil32 (Wed, 23 Jun 2021 05:15:41 GMT):
are there any samples for EDI consumtion by hyperledger sawtooth ?

indranil32 (Wed, 23 Jun 2021 05:15:47 GMT):
related to Supplychain

amundson (Tue, 29 Jun 2021 17:27:50 GMT):
@indranil32 no, but in Grid there are some related things like Product and upcoming Purchase Order which are grounded in GS1 standards

indranil32 (Fri, 02 Jul 2021 05:48:36 GMT):
Can you kindly point me to the source code, if possible >

amundson (Thu, 08 Jul 2021 16:04:59 GMT):
@indranil32 https://github.com/hyperledger/grid

ErikValiquette (Sat, 15 Jan 2022 00:37:43 GMT):
Has joined the channel.

Junior-nitcheu (Mon, 31 Jan 2022 11:42:04 GMT):
Has joined the channel.

rjones (Wed, 09 Mar 2022 03:05:06 GMT):