rjones (Fri, 04 Jun 2021 21:47:18 GMT):
DavidBoswell
davidwboswell (Fri, 04 Jun 2021 21:54:06 GMT):
Has joined the channel.
nguyer (Mon, 07 Jun 2021 12:46:30 GMT):
Has joined the channel.
nickgaski (Mon, 07 Jun 2021 15:09:55 GMT):
Has joined the channel.
nickgaski (Mon, 07 Jun 2021 15:09:56 GMT):
:punch:
shorsher (Mon, 07 Jun 2021 15:48:22 GMT):
Has joined the channel.
shorsher (Mon, 07 Jun 2021 15:48:23 GMT):
:rocket:
peterbroadhurst (Mon, 07 Jun 2021 15:57:13 GMT):
Has joined the channel.
jimthematrix (Mon, 07 Jun 2021 16:02:11 GMT):
Has joined the channel.
Andrew.Richardson (Tue, 08 Jun 2021 17:25:24 GMT):
Has joined the channel.
nguyer (Wed, 09 Jun 2021 17:35:23 GMT):
Now that the repos are moved over, Docker Hub builds are not triggering automatically. Ry suggested we move to GitHub Actions / GitHub Artifacts for our Docker images. I'm going to work on this now, because as of right now, the CLI won't be able to grab any newer builds from this point on.
rjones (Wed, 09 Jun 2021 17:47:59 GMT):
we can go back and set up dockerhub for the labs, it's just with. the recent changes for free projects, I don't think we can do ci/cd with it
nguyer (Wed, 09 Jun 2021 17:50:48 GMT):
Ah that makes sense. It might be nice to just do everything in GitHub anyway
rjones (Wed, 09 Jun 2021 17:50:54 GMT):
OK.
rjones (Wed, 09 Jun 2021 17:51:16 GMT):
https://www.docker.com/blog/changes-to-docker-hub-autobuilds/
rjones (Wed, 09 Jun 2021 18:09:08 GMT):
@nguyer [here is an example of docker CI/CD](https://github.com/hyperledger-labs/minifabric/blob/main/.github/workflows/main.yml) from minifab
nguyer (Wed, 09 Jun 2021 18:12:12 GMT):
PR for Data Exchange support in the CLI is open here: https://github.com/hyperledger-labs/firefly-cli/pull/21
nguyer (Wed, 09 Jun 2021 18:13:30 GMT):
User User_1 added by nguyer.
nguyer (Wed, 09 Jun 2021 19:15:26 GMT):
The CLI is still setting `kld-from` rather than `fly-from` so it doesn't work with the current version of `firefly-ethconnect`. Fixing that now...
nguyer (Wed, 09 Jun 2021 19:18:57 GMT):
@peterbroadhurst We also need to change the Go module names too
shorsher (Wed, 09 Jun 2021 20:13:58 GMT):
docs are live at http://labs.hyperledger.org/firefly/
shorsher (Wed, 09 Jun 2021 20:13:58 GMT):
docs are live at https://labs.hyperledger.org/firefly/
nguyer (Wed, 09 Jun 2021 20:14:42 GMT):
Can we link to the https version when we share the link?
nguyer (Wed, 09 Jun 2021 20:15:03 GMT):
Doesn't look like an auto-redirect is set up
shantaraam (Wed, 09 Jun 2021 20:19:41 GMT):
Has joined the channel.
shantaraam (Wed, 09 Jun 2021 20:19:41 GMT):
Excited about this project guys :woo:
rjones (Wed, 09 Jun 2021 20:38:15 GMT):
https looks like it's working tri==o me?
rjones (Wed, 09 Jun 2021 20:38:57 GMT):
@nguyer I went here: https://github.com/hyperledger-labs/firefly/settings/pages and enabled `https only`
shorsher (Wed, 09 Jun 2021 20:46:06 GMT):
thanks!
Andrew.Richardson (Wed, 09 Jun 2021 20:59:27 GMT):
another small URL update in wake of the move: https://github.com/hyperledger-labs/firefly/pull/56
Andrew.Richardson (Wed, 09 Jun 2021 21:05:36 GMT):
The sample UI application also got an overhaul today and gives a good hands-on of the broadcast capability. Once the remaining migration issues are sorted out in the CLI, this is hopefully a really easy way for people to get a quick touch at a high level.
https://github.com/hyperledger-labs/firefly-samples/tree/main/private-data-transfer-ui
Need to add actual private transfer capabilities to this sample next.
Andrew.Richardson (Wed, 09 Jun 2021 21:05:52 GMT):
Screen Shot 2021-06-09 at 5.02.50 PM.png
nguyer (Wed, 09 Jun 2021 21:44:34 GMT):
Awesome thank you!
nguyer (Wed, 09 Jun 2021 22:20:57 GMT):
Easy PR to update a few links in the README for review: https://github.com/hyperledger-labs/firefly/pull/58
nguyer (Wed, 09 Jun 2021 23:37:11 GMT):
Updated docker images for FireFly repos can be found here now: https://github.com/orgs/hyperledger-labs/packages?tab=packages&q=firefly
nguyer (Wed, 09 Jun 2021 23:37:29 GMT):
The `latest` tag is automatically updated when new code is merged into `main`
nguyer (Wed, 09 Jun 2021 23:42:22 GMT):
The CLI has been updated now so if you run:
```go get github.com/hyperledger-labs/firefly-cli/ff```
and `init` a new stack, you should get the new images from ghcr
shorsher (Thu, 10 Jun 2021 16:04:14 GMT):
PR for some explorer dashboard updates @Andrew.Richardson https://github.com/hyperledger-labs/firefly-ui/pull/32
shorsher (Thu, 10 Jun 2021 16:04:14 GMT):
PR for some explorer dashboard updates @Andrew.Richardson https://github.com/hyperledger-labs/firefly-ui/pull/33
nguyer (Thu, 10 Jun 2021 19:59:34 GMT):
Just opened a PR for the CLI to add some useful new commands: https://github.com/hyperledger-labs/firefly-cli/pull/29
ksanjayk (Fri, 11 Jun 2021 14:12:28 GMT):
Has joined the channel.
jbkal (Fri, 11 Jun 2021 15:54:07 GMT):
Has joined the channel.
RuiPanNewbie (Fri, 11 Jun 2021 15:55:18 GMT):
Has joined the channel.
nguyer (Fri, 11 Jun 2021 16:12:45 GMT):
Welcome to the new folks that joined! :wave: Thanks for attending the workshop!
luis.settlemint (Fri, 11 Jun 2021 16:18:36 GMT):
Has joined the channel.
luis.settlemint (Fri, 11 Jun 2021 16:18:37 GMT):
The slides presented today, will they be shared?
nguyer (Fri, 11 Jun 2021 16:24:24 GMT):
Yes! We can definitely share them. I will find a link and post it here
luis.settlemint (Fri, 11 Jun 2021 16:29:40 GMT):
thx
Andrew.Richardson (Fri, 11 Jun 2021 16:41:27 GMT):
Here are the slides from the Demo and Workshop: https://drive.google.com/file/d/1OM3Ne5tj_xUPtfcFgwUB7u5N6lGO6leX/view?usp=sharing
And here is the guide from the Workshop again: http://bit.ly/firefly-start
We'll get Peter to share the deep-dive technical deck after some of the other sessions wrap.
ksanjayk (Fri, 11 Jun 2021 19:42:22 GMT):
Screenshot from 2021-06-12 00-47-41.png
ksanjayk (Fri, 11 Jun 2021 19:42:42 GMT):
Screenshot from 2021-06-12 01-07-30.png
ksanjayk (Fri, 11 Jun 2021 19:42:47 GMT):
Screenshot from 2021-06-12 01-07-50.png
ksanjayk (Fri, 11 Jun 2021 19:43:13 GMT):
Screenshot from 2021-06-12 01-08-13.png
ksanjayk (Fri, 11 Jun 2021 19:45:34 GMT):
really excited about ur project
nguyer (Fri, 11 Jun 2021 20:52:17 GMT):
Thanks @ksanjayk! I reproduced this earlier today and will definitely look into this
nguyer (Sat, 12 Jun 2021 13:51:03 GMT):
I opened https://github.com/hyperledger-labs/firefly-cli/issues/35 to track this issue
ksanjayk (Sat, 12 Jun 2021 14:16:30 GMT):
oh thank you, I will subscribe to it and follow it
nguyer (Thu, 17 Jun 2021 12:27:10 GMT):
I'm working on tackling open issues against FireFly CLI, specifically bugs related to startup in various types of dev environments. It looks like several open issues have their root cause in permissions issues around the postgresql data directory. I'm investigating that now.
nguyer (Thu, 17 Jun 2021 14:43:47 GMT):
Looks like a lot of the current issues we're seeing can be solved by using named volumes rather than creating volume mounts on the local file system. The current behavior of the CLI using the file system is especially convoluted when running Docker inside WSL on Linux.
nguyer (Thu, 17 Jun 2021 14:43:47 GMT):
Looks like a lot of the current issues we're seeing can be solved by using named volumes rather than creating volume mounts on the local file system. The current behavior of the CLI using the file system is especially convoluted when running Docker inside WSL on Windows.
VijayKrishnan (Thu, 17 Jun 2021 16:36:32 GMT):
Has joined the channel.
downTheFallLine (Tue, 22 Jun 2021 01:28:24 GMT):
Has joined the channel.
downTheFallLine (Tue, 22 Jun 2021 01:28:24 GMT):
are issues raised growing faster than issues resolved, or other way around?
nguyer (Tue, 22 Jun 2021 13:51:39 GMT):
We're trying to get better at documenting issues in GitHub as we discover them, especially if we can't get to them immediately. We're also trying to use GitHub issues to track planned future enhancements, to make the roadmap clear to anyone who's interested.
nguyer (Tue, 22 Jun 2021 14:28:17 GMT):
Just wanted to share the link to our weekly community calls. They will be on Wednesdays at 11:00am EDT. You can find the agenda and joining info on the Hyperledger Wiki here: https://wiki.hyperledger.org/display/labs/Firefly
sauveergoel (Tue, 22 Jun 2021 14:38:13 GMT):
Has joined the channel.
sauveergoel (Tue, 22 Jun 2021 14:39:10 GMT):
I egt the following error: `Error: read |0: file already closed ` when i try to run `ff start
sauveergoel (Tue, 22 Jun 2021 14:39:10 GMT):
I get the following error: `Error: read |0: file already closed ` when i try to run `ff start
nguyer (Tue, 22 Jun 2021 14:44:51 GMT):
Happy to help! It may be helpful to start with turning on verbose logs by adding a `-v` to your start command. Can you try that and share your output?
saif_32 (Wed, 23 Jun 2021 05:09:52 GMT):
Has joined the channel.
saif_32 (Wed, 23 Jun 2021 05:13:38 GMT):
`ff start
saif_32 (Wed, 23 Jun 2021 05:13:46 GMT):
Clipboard - June 23, 2021 10:43 AM
saif_32 (Wed, 23 Jun 2021 05:14:09 GMT):
need some help on this!
nguyer (Wed, 23 Jun 2021 11:53:00 GMT):
Hi @saif_32 I'm happy to help. It looks like it failed when trying to pull docker images. Is docker running, and do you have docker-compose installed?
saif_32 (Wed, 23 Jun 2021 13:52:04 GMT):
@nguyer its working now! was missing docker-compose
nguyer (Wed, 23 Jun 2021 13:53:25 GMT):
Glad to hear it! I will make a note of that in the `README.md`.
saif_32 (Wed, 23 Jun 2021 13:56:16 GMT):
Thanks a lot!
shemnon (Wed, 23 Jun 2021 15:33:39 GMT):
Has joined the channel.
Bobbijn (Wed, 23 Jun 2021 15:59:10 GMT):
Has joined the channel.
nguyer (Wed, 23 Jun 2021 16:36:21 GMT):
Thanks to all who attended our first community call today! Glad to have you a part of this community!
nguyer (Wed, 23 Jun 2021 17:13:48 GMT):
The PR for a bunch of CLI fixes is up for review here now: https://github.com/hyperledger-labs/firefly-cli/pull/47
nguyer (Wed, 23 Jun 2021 19:45:10 GMT):
v0.0.17 of the CLI has been released now and should address many of the open issues on GitHub.
shemnon (Wed, 23 Jun 2021 20:39:56 GMT):
Is there any need for the KAT code in the firefly repo? The depend on vendor services and the kat code lives in the kaleido-io version of the repo, so it is still accessible otherwise.
nguyer (Wed, 23 Jun 2021 20:40:49 GMT):
I think @peterbroadhurst had some thoughts on keeping it there initially. Perhaps he can comment on it
shemnon (Wed, 23 Jun 2021 20:46:08 GMT):
Why onboard code with no future release plans? References exist elsewhere.
Rabax55 (Wed, 23 Jun 2021 21:47:39 GMT):
Has joined the channel.
saif_32 (Thu, 24 Jun 2021 07:03:22 GMT):
Hello! The firefly core container logs is giving this error `Error: FF10111: Error from ethconnect: {"error":"Failed to find installed contract address for 'firefly'"}`
saif_32 (Thu, 24 Jun 2021 07:19:03 GMT):
ff start is giving the below error-
saif_32 (Thu, 24 Jun 2021 07:19:08 GMT):
Clipboard - June 24, 2021 12:49 PM
saif_32 (Thu, 24 Jun 2021 07:19:08 GMT):
ff start is showing the following error:
Clipboard - June 24, 2021 12:49 PM
nguyer (Thu, 24 Jun 2021 12:26:44 GMT):
@saif_32 Which version of the CLI are you running? You can check by looking to see what version is listed on the `firefly-cli` directory in your `go` directory: ```ls ~/go/pkg/mod/github.com/hyperledger-labs/```
nguyer (Thu, 24 Jun 2021 12:27:21 GMT):
A new version was released yesterday that has a bunch of fixes in it. If you haven't updated to `v0.0.18`, try running: ```go install github.com/hyperledger-labs/firefly-cli/ff@latest```
nguyer (Thu, 24 Jun 2021 12:28:04 GMT):
I would also try to remove and re-create that stack. If that still doesn't work for you with the latest CLI, please let me know and I'll help you debug more
saif_32 (Thu, 24 Jun 2021 16:47:59 GMT):
Clipboard - June 24, 2021 10:17 PM
saif_32 (Thu, 24 Jun 2021 16:49:41 GMT):
Clipboard - June 24, 2021 10:18 PM
saif_32 (Thu, 24 Jun 2021 16:49:41 GMT):
Clipboard - June 24, 2021 10:18 PM
nguyer (Thu, 24 Jun 2021 17:53:47 GMT):
Was this stack originally created with the older version of the CLI? If the DB got into a bad migration state due to a previous timing issue (fixed in the most recent CLI), you'll need to recreate the DB for that node. The easiest thing to do is probably `ff remove ffstack` then `ff init ffstack` and `ff start ffstack`
saif_32 (Thu, 24 Jun 2021 18:08:06 GMT):
This was created using v0.0.18
saif_32 (Fri, 25 Jun 2021 03:58:50 GMT):
Clipboard - June 25, 2021 9:28 AM
saif_32 (Fri, 25 Jun 2021 03:58:50 GMT):
Clipboard - June 25, 2021 9:28 AM
saif_32 (Fri, 25 Jun 2021 12:02:08 GMT):
It's working now!
nguyer (Fri, 25 Jun 2021 12:02:32 GMT):
:clap:
nguyer (Fri, 25 Jun 2021 12:03:54 GMT):
@saif_32 Since you've been running through setting all this up, we would love to hear feedback if you have feedback on things that we can do (documentation, code enhancements, etc.) to make it easier to get up and running with FireFly
nguyer (Fri, 25 Jun 2021 12:03:54 GMT):
@saif_32 Since you've been running through setting all this up, we would love to hear if you have feedback on things that we can do (documentation, code enhancements, etc.) to make it easier to get up and running with FireFly
saif_32 (Fri, 25 Jun 2021 12:10:54 GMT):
First of all I really appreciate the amount of work that has been put in! Feedback - *1*. If we can have a use-case/demo that can show where firefly fits in the onchain-offchain scheme of things - just to know and understand the usability of firefly in a better way! *2*. If we can have a live session which can demonstrate how we connect firefly to a blockchain - that will be great!
davidwboswell (Fri, 25 Jun 2021 22:21:03 GMT):
FYI, there is now a playlist of Firefly videos on the Hyperledger YouTube channel at: https://www.youtube.com/playlist?list=PL0MZ85B_96CFVEdBNsHRoX_f15AJacZJD
saif_32 (Sat, 26 Jun 2021 06:33:19 GMT):
Clipboard - June 26, 2021 12:02 PM
saif_32 (Sat, 26 Jun 2021 06:35:07 GMT):
Clipboard - June 26, 2021 12:04 PM
saif_32 (Sat, 26 Jun 2021 12:22:03 GMT):
This is working now with v0.0.19! Thank you!
nguyer (Mon, 28 Jun 2021 12:42:55 GMT):
I meant to post this Friday, but accidentally sent it in the wrong channel: CLI v0.0.19 was just released! This release fixes some issues with Git Bash on Windows and also enhances some validation which should make for a smoother first-start experience.
Andrew.Richardson (Mon, 28 Jun 2021 13:34:50 GMT):
We do have https://github.com/kaleido-io/firefly-samples to demonstrate the basic concept of some off-chain message (either public or private) with the hash pinned to the chain. Planning to eventually add some more "real world" samples as well.
Andrew.Richardson (Mon, 28 Jun 2021 13:34:50 GMT):
We do have https://github.com/hyperledger-labs/firefly-samples to demonstrate the basic concept of some off-chain message (either public or private) with the hash pinned to the chain. Planning to eventually add some more "real world" samples as well.
saif_32 (Mon, 28 Jun 2021 16:39:56 GMT):
@Andrew.Richardson yeah checked that... it helps! It is good for getting started. If we can have some workshop where we do the connections between different components from scratch, we can have a clearer idea!!
saif_32 (Mon, 28 Jun 2021 16:39:56 GMT):
@Andrew.Richardson yeah checked that... it helps! It is good for getting started. If we can have some workshop where we do the connections between different components of firefly from scratch, we can have a clearer idea!!
jcarpenter (Tue, 29 Jun 2021 19:29:26 GMT):
Has joined the channel.
urkizu (Wed, 30 Jun 2021 07:25:44 GMT):
Has joined the channel.
Andrew.Richardson (Wed, 30 Jun 2021 20:37:41 GMT):
Recording and slides from this morning's call are on the wiki: https://wiki.hyperledger.org/display/labs/2021-06-30+FireFly+Community+Call
nguyer (Thu, 01 Jul 2021 13:09:09 GMT):
I just opened a PR that adds the swagger file to the repo, and also integrates it into the docs pages: https://github.com/hyperledger-labs/firefly/pull/107
rjones (Thu, 01 Jul 2021 14:26:59 GMT):
https://github.com/hyperledger-labs/firefly-fabconnect
rjones (Thu, 01 Jul 2021 14:27:05 GMT):
@jimthematrix ^^^
nguyer (Thu, 01 Jul 2021 14:56:24 GMT):
Open API spec for FireFly has now been integrated into the docs pages: https://labs.hyperledger.org/firefly/swagger/swagger.html
nguyer (Wed, 07 Jul 2021 12:53:46 GMT):
Details for today's Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-07-07+FireFly+Community+Call
Today's topic for the first half will be: *Event Sequencing and Aggregation*
shorsher (Wed, 07 Jul 2021 18:40:00 GMT):
could use a review on updating the explorer version in ff core: https://github.com/hyperledger-labs/firefly/pull/118
nguyer (Fri, 09 Jul 2021 16:21:59 GMT):
@Andrew.Richardson I just opened a PR for some changes to the E2E test script which you may be interested in looking at: https://github.com/hyperledger-labs/firefly/pull/122
shantaraam (Fri, 09 Jul 2021 21:18:19 GMT):
https://github.com/hyperledger-labs/firefly-cordaconnect/pull/5
shantaraam (Fri, 09 Jul 2021 21:19:04 GMT):
Hi guys, I am trying to understand lgtm java build failure on the PR above?
shantaraam (Fri, 09 Jul 2021 21:19:30 GMT):
Can I get some information on what version of jdk lgtm is configured with
nguyer (Mon, 12 Jul 2021 12:34:34 GMT):
Hi @shantaraam, the details of why the check failed can be found here: https://lgtm.com/projects/g/hyperledger-labs/firefly-cordaconnect/logs/rev/pr-613dd587028877f860e04020123aa5c255243945/lang:java/stage:Build%20merge_181c4dec7e60360bb7322dc1954c35f133d63f66
It looks like the check failed because the code will not build after merging the PR, even though the code in the PR itself builds correctly.
shantaraam (Mon, 12 Jul 2021 13:52:42 GMT):
Thanks nicko for the information. I am trying to figure out why that is. ? I am not seeing the build errors locally and figuring out why that might be so.
nguyer (Mon, 12 Jul 2021 13:55:29 GMT):
Off the top of my head I'm not sure. So you're saying you've tried merging the branch into main locally and that builds correctly?
shantaraam (Mon, 12 Jul 2021 14:15:51 GMT):
yes. I tried merge and build locally
shantaraam (Mon, 12 Jul 2021 14:46:34 GMT):
Update to gradle source compatibility (JDK 11) , worked . Updated PR with change and also couple of changes to fix analysis warning
nguyer (Mon, 12 Jul 2021 14:46:45 GMT):
Nice. Glad you got it working
davidwboswell (Tue, 13 Jul 2021 00:03:29 GMT):
plans for a virtual meetup about firefly have just been posted and everyone here is welcome to attend on thursday, july 22 at 11 EDT. please also help spread the word about the meetup and invite others to join. https://www.meetup.com/Hyperledger-Denver/events/279429841/
jimthematrix (Tue, 13 Jul 2021 20:30:13 GMT):
For this week's community call, we will discuss the current architecture design for the Fabric connector. the repository has been updated with the diagrams that we will walk through tomorrow: https://github.com/hyperledger-labs/firefly-fabconnect. implementation is being done in parallel. hope the first code drop can be pushed soon. but of course we'll take into account any feedback we might get in the meanwhile, before getting committed to the current design
janrockdev (Wed, 14 Jul 2021 15:55:32 GMT):
Has joined the channel.
nguyer (Thu, 15 Jul 2021 16:03:28 GMT):
Hi all! I just wanted to reach out and see if there were any specific topics that folks would like to see covered in upcoming community calls?
janrockdev (Fri, 16 Jul 2021 13:33:55 GMT):
Hi, maybe when will be Jim's initial code push available, integration with Firefly (cli, UI to show connector state and config + Kafka micro UI to manage topics > life cycle management), Firefly security (+ Kafka SSL etc), also a transactions generator for dev and test the API/benchmark/code optimisation, non-functional requirements - throughput/supported version/OS etc., documentation + error conventions etc.
nguyer (Fri, 16 Jul 2021 17:51:08 GMT):
Good question! I'll nudge @jimthematrix on this one :slight_smile:
zandercreations (Fri, 16 Jul 2021 18:56:21 GMT):
Has joined the channel.
janrockdev (Mon, 19 Jul 2021 13:25:33 GMT):
@jimthematrix "first-cut" :thumbsup:
jimthematrix (Mon, 19 Jul 2021 14:26:29 GMT):
thanks Jan for noticing already! Nicko is going to review and merge it soon, in the meanwhile, please take a look and let me know your thoughts. I think some options for you to get started in contributing:
- adding tests: since a lot of the code are refactored from `firefly-ethconnect`, we should be able to borrow a lot of the test code as well. even thought none of the packages are done yet, some of them are pretty agnostic to the DLT, like `kvstore`, `rest/receipt`, and `ws`, so adding tests for those packages should be possible now
- implementing the signing identity management component: this one is currently missing entirely, as it's pretty independent from the rest. create a package, say `internal/identity`, and implement the handler to POST/GET signing identities, to register and enroll users
jimthematrix (Mon, 19 Jul 2021 14:26:29 GMT):
thanks Jan for noticing already! Nicko is going to review and merge it soon, in the meanwhile, please take a look and let me know your thoughts.
jimthematrix (Mon, 19 Jul 2021 14:27:31 GMT):
I think some options for folks who are interested in contributing to get started:
- adding tests: since a lot of the code are refactored from `firefly-ethconnect`, we should be able to borrow a lot of the test code as well. even thought none of the packages are done yet, some of them are pretty agnostic to the DLT, like `kvstore`, `rest/receipt`, and `ws`, so adding tests for those packages should be possible now
- implementing the signing identity management component: this one is currently missing entirely, as it's pretty independent from the rest. create a package, say `internal/identity`, and implement the handler to POST/GET signing identities, to register and enroll users
jimthematrix (Mon, 19 Jul 2021 14:27:31 GMT):
I think some options for folks who are interested in contributing to get started:
- adding tests: since a lot of the code are refactored from `firefly-ethconnect`, we should be able to borrow a lot of the test code as well. even though none of the packages are done yet, some of them are pretty agnostic to the DLT, like `kvstore`, `rest/receipt`, and `ws`, so adding tests for those packages should be possible now
- implementing the signing identity management component: this one is currently missing entirely, as it's pretty independent from the rest. create a package, say `internal/identity`, and implement the handler to POST/GET signing identities, to register and enroll users
janrockdev (Mon, 19 Jul 2021 14:44:05 GMT):
Thanks, I was too fast and raised an issue with too many unused dependencies in mod - probably from ethconnect ;) re-init of go mod fix the problem. I will wait for Nicko to finish the merge. ;)
shantaraam (Mon, 19 Jul 2021 23:23:27 GMT):
bravenewworld
nguyer (Tue, 20 Jul 2021 12:58:34 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-07-21+FireFly+Community+Call
Thursday, July 21, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Deploying FireFly in Cloud-Native Environments (Hayden Fuss)
- Open Discussion
Thank you all for your participation in these calls! We hope to see you there!
janrockdev (Tue, 20 Jul 2021 22:14:54 GMT):
https://github.com/defidbpub/firefly-fabconnect/blob/main/images/arch-1.jpg have you considered to return event/insert state (e.g 202 Accepted / 200 Ok) also back to Kafka?
janrockdev (Wed, 21 Jul 2021 12:32:48 GMT):
Hi, is this something known and easy to fix - I'm trying to send broadcast message and it seems to struggle to share it. Please help ;)
```
package main
import (
"fmt"
"github.com/go-resty/resty/v2"
)
func main() {
client := resty.New()
resp, err := client.R().
SetHeader("Content-Type", "application/json").
SetBody([]byte(`{"value":"test"}`)).
Post("http://192.168.0.234:5000/api/v1/namespaces/default/broadcast/message")
if err != nil {
fmt.Printf("%v", err)
} else {
fmt.Printf("%v", resp.Status)
}
}
```
janrockdev (Wed, 21 Jul 2021 12:32:57 GMT):
Clipboard - July 21, 2021 1:32 PM
nguyer (Wed, 21 Jul 2021 12:46:39 GMT):
@janrockdev I'm just tried the same request on my machine. I'm not sure why it's `pending` on one node but `succeeded` on the other. I'll look into that though. But the body of your request is not quite right. You're sending:
```json
{
"value": "Hello world"
}
```
But it should be:
```json
{
"data": [
{
"value": "Hello world"
}
]
}
```
janrockdev (Wed, 21 Jul 2021 13:02:03 GMT):
```SetBody([]byte(`{"data":[{"value":"Hello world"}]}`)).``` makes no difference on the pending status, rebuild (ff stop/remove/init/start) makes no difference too :(
janrockdev (Wed, 21 Jul 2021 13:02:34 GMT):
```# curl -i -H "Accept: application/json" -H "Content-Type: application/json" --data '{"data":[{"value":"Hello world"}]}' -X POST http://192.168.0.234:5000/api/v1/namespaces/default/broadcast/message
HTTP/1.1 202 Accepted
Content-Type: application/json
Vary: Origin
Date: Wed, 21 Jul 2021 12:56:51 GMT
Content-Length: 545
{"header":{"id":"dc03954e-b118-4a62-b944-4d76f438fcb3","type":"broadcast","txtype":"batch_pin","author":"0x116456697fe0faed7fa3a05218542489ef6ecc16","created":"2021-07-21T12:56:51.02361128Z","namespace":"default","topics":["default"],"datahash":"a68b605298d1284a8f265a4c58e7f15af644d8b46faff489051f4779f9b8524f"},"hash":"03cb5e931326dddcd360d8799c3f8598f9d4bea3efe3975b75a0b291f744d6d4","local":true,"pending":true,"data":[{"id":"6d0f515d-a9a0-4472-baec-86d52ba6ae00","hash":"b58f34e73579dcfb700daacadd50fa7503f1e4c6c881cb4d720fe84a57be306d"}]}```
janrockdev (Wed, 21 Jul 2021 13:03:01 GMT):
curl has the same result
nguyer (Wed, 21 Jul 2021 13:04:30 GMT):
Hmm let me try real quick....
janrockdev (Wed, 21 Jul 2021 13:05:47 GMT):
it's a bug in FF, because firefly-samples(private-data-transfer-cli) crashed as well
```
> private-data-transfer-cli@1.0.0 start
> ts-node src/index.ts
Broadcasting data values from firefly1: Hello,World
Failed to run: Error: No message received
```
janrockdev (Wed, 21 Jul 2021 13:07:58 GMT):
few times restart will help ... I noticed similar behaviour yesterday as well
janrockdev (Wed, 21 Jul 2021 13:08:27 GMT):
docker containers up, no visible issue
nguyer (Wed, 21 Jul 2021 13:24:05 GMT):
After I attempted a broadcast with an HTTP body of
```json
{
"value": "Hello world"
}
```
It seemed like all broadcasts after that (with proper message payloads) also got stuck in `pending` on the node I was sending from. However, I was able to reset my stack and things are working normally. I'm guessing that initial message didn't get processed correctly and caused everything after that to get stuck. Obviously this is not expected. I'll see if I can figure out why that message got stuck in pending. Thanks for reporting this!
janrockdev (Wed, 21 Jul 2021 13:50:24 GMT):
I think it's related to ff stop/start
janrockdev (Wed, 21 Jul 2021 13:50:34 GMT):
Thanks!
janrockdev (Wed, 21 Jul 2021 13:53:18 GMT):
All works perfectly now. I will try to replicate the error later and check the containers' logs.
nguyer (Wed, 21 Jul 2021 13:59:13 GMT):
:+1:
davidwboswell (Thu, 22 Jul 2021 15:02:07 GMT):
The virtual meetup featuring Firefly is starting now and people are welcome to dial-in at: https://zoom.us/my/hyperledger.community.backup?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
mianko (Thu, 22 Jul 2021 16:02:01 GMT):
Has joined the channel.
mianko (Thu, 22 Jul 2021 16:02:01 GMT):
I had to logout early. Can I receive the slides and chat log?
davidwboswell (Thu, 22 Jul 2021 16:33:10 GMT):
@mianko -- the recording of the meetup is on youtube at https://www.youtube.com/watch?v=VefFjLPzkzI if you'd like to watch parts you missed. i'll let nicko or peter respond about the slides.
davidwboswell (Thu, 22 Jul 2021 16:33:51 GMT):
firefly_meetup_july22_2021_chat.txt
davidwboswell (Thu, 22 Jul 2021 16:33:58 GMT):
and here's the chat log from today's meetup
nguyer (Thu, 22 Jul 2021 18:04:17 GMT):
Intro to Firefly.pdf
nguyer (Thu, 22 Jul 2021 18:04:20 GMT):
Here are the slides from today's meetup. Thanks for attending!
amyth (Thu, 22 Jul 2021 18:09:24 GMT):
Has joined the channel.
amyth (Fri, 23 Jul 2021 18:35:18 GMT):
Hello!
I've been interested in firefly, awesome work!
I'm very interested,
I'll try to solve look at some issues and dig around the codebase through the weekend.
amyth (Fri, 23 Jul 2021 18:36:09 GMT):
I'm new to go, but i've been used to typescript for a good while now...
rjones (Fri, 23 Jul 2021 18:37:11 GMT):
@amyth welcome aboard!
amyth (Fri, 23 Jul 2021 18:39:51 GMT):
I heard that we are really looking for production-ready example applications to be built using firefly.
do you have some preexisting ideas that you'd like to share?
rjones (Fri, 23 Jul 2021 18:40:10 GMT):
@nguyer ?
nguyer (Fri, 23 Jul 2021 18:41:48 GMT):
Hey @amyth! Welcome! Really glad to hear you want to get involved!
nguyer (Fri, 23 Jul 2021 18:43:44 GMT):
We have a couple of repos in TypeScript if you want to jump in with a language you're already familiar with:
https://github.com/hyperledger-labs/firefly-dataexchange-https
https://github.com/hyperledger-labs/firefly-ui
nguyer (Fri, 23 Jul 2021 18:44:26 GMT):
Our existing sample apps are in this repo: https://github.com/hyperledger-labs/firefly-samples
nguyer (Fri, 23 Jul 2021 18:45:39 GMT):
Like you said, a "production-ready" example would be awesome if building an app on top of FireFly would be interesting to you. TypeScript would also be perfect for this.
Jess_Hurwitz (Fri, 23 Jul 2021 22:43:05 GMT):
Has joined the channel.
merq (Sat, 24 Jul 2021 01:13:34 GMT):
Has joined the channel.
janrockdev (Sun, 25 Jul 2021 14:03:07 GMT):
#fabconnect Hi, I have ready docker-compose.yaml for standalone Kafka with UI and support code to create topics + tests (I think we will need at least 3 topics, ffin/ffout/fflog). I can add it to fabconnect cli to install it (as optional) maybe with future alternative e.g. https://github.com/dgraph-io/badger if someone does not want to have Kafka in the stack. I can open new PR and you can decide.
jimthematrix (Sun, 25 Jul 2021 20:09:15 GMT):
thanks Jan! this would be very useful in local integration tests. if they can be saved under a folder "test/integration" that'd be ideal. don't think installing integration test fixture via the CLI is necessary. Looking forward to seeing a PR for this!
janrockdev (Mon, 26 Jul 2021 10:32:11 GMT):
I'm thinking to add two things:
1) option to create/remove Kafka standalone node for the purpose of the connector using CLI (I think it would be nice to have this option if Kafka will be part of the connector and FireFly is about "autoinstall all")
2) add a local integration test (test/integration/kafka) to test Kafka created from CLI (1) and run a test: create topics (ffin/ffout/fflog) > produce a message to ffin > consume message from ffin > remove the topics (expected connector will create them when start).
janrockdev (Mon, 26 Jul 2021 10:32:38 GMT):
I'm thinking to add two things:
1) option to create/remove Kafka standalone node for the purpose of the connector using CLI (I think it would be nice to have this option if Kafka will be part of the connector and FireFly is about "autoinstall all")
2) add a local integration test (test/integration/kafka) to test Kafka created from CLI (1) and run a test: create topics (ffin/ffout/fflog) > produce a message to ffin > consume message from ffin > remove the topics (expected connector will create them when start).
nguyer (Mon, 26 Jul 2021 12:28:22 GMT):
It would be great to be able to create a FireFly stack with the CLI that uses Fabric/fabconnect. Right now it's only limited to Ethereum/ethconnect, but it would be awesome to have options to pick one or the other
sukrutsathaye (Mon, 26 Jul 2021 16:24:49 GMT):
Has joined the channel.
nguyer (Mon, 26 Jul 2021 17:36:24 GMT):
[ ](https://chat.hyperledger.org/channel/firefly-lab?msg=5zWb8ug2Wvrrss8Px) @janrockdev Just wanted to follow up on this issue. This got fixed in a PR that was recently merged. Here is the commit that contained the fix: https://github.com/hyperledger-labs/firefly/pull/142/commits/97e398f193a390fd1b23d915ca1563c325bf54da
janrockdev (Mon, 26 Jul 2021 17:44:35 GMT):
It has been a mix of two issues. One was the format, which was my mistake :) and the second related to firefly and issue to broadcast messages after stop and start. Thanks, I will retest it.
nguyer (Mon, 26 Jul 2021 17:45:44 GMT):
Yes, this fix was for the latter. The issue was that a message with no data elements would end up getting "stuck" on the sender's node and never confirmed
jimthematrix (Tue, 27 Jul 2021 12:40:27 GMT):
agree that the option to stand up a local stack integrating fabconnect would be a logical step. can have the kafka setup as part of the FireFly CLI experience. obviously it wouldn't be the default config for using fabconnect (direct handler for the async requests should be the default which would be the case if kafka config is not present)
jimthematrix (Tue, 27 Jul 2021 12:40:27 GMT):
agree that the option to stand up a local stack integrating fabconnect would be a logical step. can have the kafka setup as part of the developer experience with FireFly CLI. obviously it wouldn't be the default config for using fabconnect (direct handler for the async requests should be the default which would be the case if kafka config is not present)
jimthematrix (Tue, 27 Jul 2021 12:42:36 GMT):
when I said "don't think installing integration test fixture via the CLI is necessary", I was referring to the `fabconnect` executable itself. setting up Kafka should be outside of the fabconnect functionalities. sorry if that was confusing earlier
nguyer (Tue, 27 Jul 2021 13:53:56 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-07-28+FireFly+Community+Call
Thursday, July 28, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
FireFly Plugin Architecture and Configuration (Nicko Guyer)
Open Discussion
As always, thank you all for your participation in these calls! We hope to see you there!
nguyer (Tue, 27 Jul 2021 13:53:56 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-07-28+FireFly+Community+Call
Thursday, July 28, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- FireFly Plugin Architecture and Configuration (Nicko Guyer)
- Open Discussion
As always, thank you all for your participation in these calls! We hope to see you there!
nguyer (Tue, 27 Jul 2021 13:53:56 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-07-28+FireFly+Community+Call
Thursday, July 28, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- FireFly Plugin Architecture and Configuration (Nicko Guyer)
- Open Discussion
As always, thank you all for your participation in these calls! We hope to see you there!
nguyer (Tue, 27 Jul 2021 13:53:56 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-07-28+FireFly+Community+Call
Wednesday, July 28, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- FireFly Plugin Architecture and Configuration (Nicko Guyer)
- Open Discussion
As always, thank you all for your participation in these calls! We hope to see you there!
janrockdev (Tue, 27 Jul 2021 14:11:38 GMT):
@jimthematrix I agree. It would be clean solution. I can add it to Firefly-cli if you will like it. The integration test is basically spinning latest Kafka with UI, creating topic, producing and consuming message and removing all Kafka containers after the test. If it will be optional part of Firefly-cli, then the test will be without the docker-compose part. Hopefully I will have time tonight. It works now, but I have to put the code to firefly style - e.g. no comments, etc :D
jimthematrix (Wed, 28 Jul 2021 15:43:09 GMT):
awesome, thanks @janrockdev, sounds a good plan and looking forward to seeing the PR
nguyer (Wed, 28 Jul 2021 18:46:38 GMT):
Slides and recording from today's call are up at: https://wiki.hyperledger.org/display/labs/2021-07-28+FireFly+Community+Call
janrockdev (Wed, 28 Jul 2021 23:25:17 GMT):
Please, could you have a look first to my repo: https://github.com/defidbpub/firefly-fabconnect/tree/main/test/integration/cli where is temporary the Kafka deployment. Integration test will evaluate if this Kafka server is up, topic ready, and using Kafka client from /internal/kafka. Please, let me know if it is useful and what to improve. It passed your workflow test. ;)
janrockdev (Wed, 28 Jul 2021 23:25:17 GMT):
Please, @jimthematrix could you have a look first to my repo: https://github.com/defidbpub/firefly-fabconnect/tree/main/test/integration/cli where is temporary the Kafka deployment. Integration test will evaluate if this Kafka server is up, topic ready, and using Kafka client from /internal/kafka. Please, let me know if it is useful and what to improve. It passed your workflow test. ;)
janrockdev (Wed, 28 Jul 2021 23:25:17 GMT):
Please, @jimthematrix could you have a look first to my repo: https://github.com/janrockdev/firefly-fabconnect/tree/main/test/integration/cli where is temporary the Kafka deployment. Integration test will evaluate if this Kafka server is up, topic ready, and using Kafka client from /internal/kafka. Please, let me know if it is useful and what to improve. It passed your workflow test. ;)
DevendranM (Thu, 29 Jul 2021 15:15:12 GMT):
Has joined the channel.
bhavesh.c (Thu, 29 Jul 2021 19:28:21 GMT):
Has joined the channel.
nguyer (Thu, 29 Jul 2021 19:30:20 GMT):
:wave: Welcome to the new folks joining the channel! Glad to have you here!
nguyer (Fri, 30 Jul 2021 19:49:27 GMT):
A new update to the FireFly CLI was just published (`v0.0.25`). Some changes in this version include:
- Ganache CLI has been replaced by a proper geth node - This fixes some edge cases where ganache-cli behaved differently causing problems for Firefly.
- The ability to run a FireFly core process outside of docker. This lets developers run the FireFly core with their IDE debugger while connecting that core process to a FireFly network where the rest of the processes are running inside docker. This should speed up the development cycle and make it easier for new contributors to get involved. Documentation on how to do this is in the process of being merged, but for now, you can read how to use this new feature here: https://github.com/hyperledger-labs/firefly/blob/785a35aea84a8081ad946ca01fcadaf9c4e0ee69/docs/contributors/dev_environment_setup.md
nguyer (Fri, 30 Jul 2021 19:51:14 GMT):
Note: Because of the switch from ganache-cli to geth, you will likely not be able to run `reset` and then `start` on old stacks created with previous versions of the CLI. If you run into this case, we recommend you simply `remove` the stack and `init` it again.
shemnon (Fri, 30 Jul 2021 19:51:52 GMT):
Could a Hyperledger Besu node also serve as a Ethereum Node?
nguyer (Fri, 30 Jul 2021 19:53:29 GMT):
Yes! It could, but someone would need to add a flag to the CLI as well as generate the config to wire that up. Shouldn't be too hard to add though.
nguyer (Fri, 30 Jul 2021 19:54:54 GMT):
If someone who was very familiar with Besu wanted to contribute to FireFly that sounds like it would be a great thing to add :wink:
jimthematrix (Mon, 02 Aug 2021 16:45:10 GMT):
thanks @janrockdev, was heads down on coding for the event stream, will take a look later today
jimthematrix (Mon, 02 Aug 2021 16:45:10 GMT):
thanks @janrockdev, great to see this available in your repo. I was heads down on coding for the event stream, will take a look later today
jimthematrix (Mon, 02 Aug 2021 17:35:24 GMT):
hi @janrockdev , I must be missing something here, but I can't seem to find the new content you pushed to your repo, as there's no `/test/integration/cli` folder in any of the branches (I found `main` and `first-cut`)
janrockdev (Mon, 02 Aug 2021 19:42:12 GMT):
hi, I did small cosmetic PR and the signoff is expecting unchanged main on my side, so I had to remove it. I will create new branch and share it. I will look to the listed issues instead of making distraction or more issues :D
nguyer (Tue, 03 Aug 2021 14:45:28 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-08-04+FireFly+Community+Call
Wednesday, August 4, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Event Driven Application Design (Peter Broadhurst)
- This topic will discuss how to design apps in an event driven manner, highlighting its advantages over other models, and how it's a natural fit for enterprise multi-party systems.
- Open Discussion
As always, thank you all for your participation in these calls! We hope to see you there!
janrockdev (Tue, 03 Aug 2021 20:59:50 GMT):
Hi, a question to the ff-cli team:
I'm currently testing my grpc "fastconnect" which is sending 1000 messages/sec to Kafka buffer to be reinserted to Hypeledger via API (:5000/api).
I can see all the messages in the Explorer, also data in Data, however, the main stats not updating at all, or I can see just 100 increments instead of 1000.
The speed is not bad, data are in, just the UI main stats are confusing. Any idea, what could be wrong?
janrockdev (Tue, 03 Aug 2021 21:00:27 GMT):
Screenshot 2021-08-03 at 21.48.08.png
janrockdev (Tue, 03 Aug 2021 21:01:03 GMT):
Last messages shows correct status, timestamps etc.
nguyer (Tue, 03 Aug 2021 21:02:37 GMT):
I think the API does pagination (so that it doesn't have to do a select on the whole table). I'm guessing the UI still needs some work to actually account for many pages of data. @shorsher can you comment on that?
janrockdev (Tue, 03 Aug 2021 21:05:14 GMT):
(version latest from this morning build)
janrockdev (Tue, 03 Aug 2021 21:07:21 GMT):
The donut chart shows some activity that I believe is correct during the load, just the number inside is not correct.
janrockdev (Tue, 03 Aug 2021 21:23:30 GMT):
One more question related to throughput. What could be the best way to get faster insert? I don't want to move back to manual installation of Hyperledger cluster ;)
shorsher (Tue, 03 Aug 2021 21:30:43 GMT):
Hi @janrockdev, thanks for pointing this out. Currently, there's no good way to get the total number of anything (messages, etc.) from the API (see https://github.com/hyperledger-labs/firefly/issues/43). So I believe I just picked some arbitrarily high (not high enough :sweat_smile:) pagination limit when trying to get totals for the dashboard.
shorsher (Tue, 03 Aug 2021 21:31:51 GMT):
It definitely can be improved, I'll see what I can do this week. If you have any suggestions, I'd love to hear them.
janrockdev (Tue, 03 Aug 2021 21:33:06 GMT):
Cool, no worries, it's super useful now - Last messages and preview is all what I need. ;)
shorsher (Tue, 03 Aug 2021 21:33:21 GMT):
Paging through the tables for messages, transactions, etc. should allow you to see all of them however.
janrockdev (Tue, 03 Aug 2021 21:34:05 GMT):
All works! Except the main top 4 stats and donut stat in the middle.
shorsher (Tue, 03 Aug 2021 21:36:44 GMT):
Glad to hear! If you run into any more issues or have suggestions, please feel free to pop them in an issue.
janrockdev (Tue, 03 Aug 2021 21:37:20 GMT):
I will put it straight to #43. Thanks!
janrockdev (Tue, 03 Aug 2021 21:45:00 GMT):
just on 2 nodes I can insert 1000 100byte messages in 110 seconds. ~9/sec ...how to get to ±50? wsocket connector?
janrockdev (Tue, 03 Aug 2021 21:47:03 GMT):
@jimthematrix Will that be a similar challenge for the fabconnect?
jimthematrix (Wed, 04 Aug 2021 14:58:33 GMT):
ah got you, the signoff check is a pain for adding additional commits to a PR. what I ended up doing was using a branch in my own fork, and create the PR from there against the main in the official repo. that way you are allowed to add additional commits to an outstanding PR, as long as each commit is properly signed off
janrockdev (Wed, 04 Aug 2021 16:29:09 GMT):
I will do the same next time ;)
jimthematrix (Wed, 04 Aug 2021 20:25:55 GMT):
@janrockdev I assume the transactions were submitted as async request (`fly-sync=false`)? were you using the `fabconnect` with a Kafka handler or the direct handler for the test run? some of the things to tweak for higher parallelism:
- `maxInFlight`: how many txs can enter the internal queue and be managed
- `sendCurrency`: how may txs can be sent to the Fabric network in parallel
jimthematrix (Wed, 04 Aug 2021 20:25:55 GMT):
@janrockdev I assume the transactions were submitted as async request (`fly-sync=false`)? were you using the fabconnect with a Kafka handler or the direct handler for the test run? some of the things to tweak for higher parallelism:
- `maxInFlight`: how many txs can enter the internal queue and be managed
- `sendCurrency`: how may txs can be sent to the Fabric network in parallel
jimthematrix (Wed, 04 Aug 2021 20:26:34 GMT):
these 2 parameters work the same with in both `ethconnect` and `fabconnect`
jimthematrix (Wed, 04 Aug 2021 20:26:34 GMT):
these 2 parameters work the same with in both ethconnect and fabconnect
sukrutsathaye (Tue, 10 Aug 2021 09:08:04 GMT):
can i change the docker-compose file generated after creating a new stack to suit my specific use-case, i.e using with hyperledger besu?
nguyer (Tue, 10 Aug 2021 17:35:19 GMT):
You can definitely edit the docker-compose file after you run `ff init`. If you replace geth with something else, you will have still have some work to do, to get a working stack.
When you run `ff start
nguyer (Tue, 10 Aug 2021 19:10:24 GMT):
Hi all! Starting this week, we are changing our community call to an every-other-week schedule. We will skip this week so there will be *no community call tomorrow*. Our next meeting will be Wednesday 2021-08-18.
sukrutsathaye (Wed, 11 Aug 2021 07:48:44 GMT):
exactly! I am having a hard time unlocking the account after I replace geth image with that of the besu. Although I had replaced all the addresses and keys which geth had with that of besu.
nguyer (Wed, 11 Aug 2021 13:15:12 GMT):
If you're interested in getting the FireFly CLI to generate a stack with Hyperledger Besu, I'd love to work together on that, or at least help point you in the right direction. It's something we really want to support, but just haven't had the cycles to tackle yet
sukrutsathaye (Wed, 11 Aug 2021 15:46:32 GMT):
Yes lets work on it. I would very much like that
nguyer (Wed, 11 Aug 2021 16:21:53 GMT):
Awesome! Want to have a zoom call at some point to talk through what we would need to do?
sukrutsathaye (Wed, 11 Aug 2021 16:54:12 GMT):
Yeah sure! Lets do it. Let me know when you would be available for a call
nguyer (Wed, 11 Aug 2021 16:55:42 GMT):
My schedule is pretty flexible. I'm in EDT but I'm also okay meeting early/late in the day if that works better for you
sukrutsathaye (Wed, 11 Aug 2021 17:03:20 GMT):
Lets meet tomorrow. I am also flexible for tomorrow
gabriel.indik (Thu, 12 Aug 2021 15:59:50 GMT):
@amyth it's great to see other collaborators with Typescript skills. We have an open issue for the FireFly data exchange repo. https://github.com/hyperledger-labs/firefly-dataexchange-https/issues/36
gabriel.indik (Thu, 12 Aug 2021 15:59:50 GMT):
@amyth it's great to see other collaborators with Typescript skills. We have an open issue for the FireFly data exchange repo. https://github.com/hyperledger-labs/firefly-dataexchange-https/issues/36 when you get a chance, please let me know if you would like to collaborate together on that new feature.
nguyer (Thu, 12 Aug 2021 20:56:50 GMT):
@sukrutsathaye I just pushed a decently sized refactor to this branch https://github.com/hyperledger-labs/firefly-cli/tree/blockchain-refactor
This creates a generic interface for various blockchain providers and moves all of the `geth` specific code out of the stack logic directly. I stubbed out a `BesuProvider` here: https://github.com/hyperledger-labs/firefly-cli/blob/blockchain-refactor/internal/blockchain/ethereum/besu/besuProvider.go It just needs the functions filled out.
There was a lot of code change in this branch, and it's largely untested. I just got it to compile again. Will do some thorough testing tomorrow to make sure I didn't break anything, but wanted to give you a heads up because I think this will be helpful to you when you get to the point of writing the code to automate the Besu setup.
sukrutsathaye (Fri, 13 Aug 2021 10:15:39 GMT):
Thanks a lot for this. I ll start cracking!
nguyer (Fri, 13 Aug 2021 11:55:41 GMT):
There are definitely some bugs in the refactor, so I'll push another commit here shortly. Testing now.
sukrutsathaye (Fri, 13 Aug 2021 12:10:43 GMT):
perfect! then I ll pull it once you commit the current changes
nguyer (Fri, 13 Aug 2021 12:15:28 GMT):
Okay the geth code path should be working again
nguyer (Fri, 13 Aug 2021 12:15:34 GMT):
I just pushed another commit
sukrutsathaye (Fri, 13 Aug 2021 12:48:09 GMT):
awesome!
nguyer (Fri, 13 Aug 2021 12:48:58 GMT):
I'll still be making a few changes to this branch. Hopefully they won't be too disruptive. I need to work out a different way to do logging now that we have the interface abstraction
sukrutsathaye (Fri, 13 Aug 2021 12:51:07 GMT):
I don't mind, you can continue the way you have planned. I would be a bit slow initially, because I have no experience with go. But I can try to wrap my head around it, and ask you about the code which I don't understand
nguyer (Fri, 13 Aug 2021 14:53:20 GMT):
Just pushed another commit that adds a logging interface so the blockchain implementations can log to whichever method the CLI is currently using (stdout or the fancy spinner thingy)
nguyer (Fri, 13 Aug 2021 19:37:34 GMT):
@sukrutsathaye and @Andrew.Richardson I just pushed another decent update to that branch. Andrew, this one has your recently merged changes in it as well (though some of that code has moved). There may be a bit more code to shuffle around as I get further into the Fabric implementation (member/identity generation?) but the current code builds, starts a stack, and all the E2E tests pass when run against that stack so I feel like it's shaping up well now
nguyer (Fri, 13 Aug 2021 19:37:44 GMT):
https://github.com/hyperledger-labs/firefly-cli/tree/blockchain-refactor
nguyer (Fri, 13 Aug 2021 19:39:15 GMT):
@Andrew.Richardson, there are also some other CLI PRs hanging around out there. The longer they sit unapproved the worse these merges are going to get. Do you mind looking at the other two?
Andrew.Richardson (Fri, 13 Aug 2021 19:41:34 GMT):
I only saw one unapproved PR, but I approved it 👍
nguyer (Fri, 13 Aug 2021 19:42:06 GMT):
Thanks! I missed the fact that you had already approved the other one. Thank you!
Andrew.Richardson (Fri, 13 Aug 2021 19:55:24 GMT):
I opened two small PRs on ethconnect:
- README changes: https://github.com/hyperledger-labs/firefly-ethconnect/pull/138
- Allow passing in a request ID instead of being assigned one: https://github.com/hyperledger-labs/firefly-ethconnect/pull/139
The latter may help avoid race conditions in the case where the blockchain provider sends events _before_ resolving the HTTP request. If an event comes in before FireFly has resolved and parsed the HTTP response that triggered it, it's impossible to correlate (currently we hold the event for some time and poll to see if the ID becomes known, which is messy). But if we can provide the ID from FireFly, then every event should be recognized no matter whether the HTTP request or the async events come back first.
rjones (Fri, 13 Aug 2021 20:01:37 GMT):
@Andrew.Richardson I don't know if you've seen this new view of PRs in github: https://github.dev/hyperledger-labs/firefly-ethconnect/pull/139
Andrew.Richardson (Fri, 13 Aug 2021 20:02:09 GMT):
whoa, I had not
rjones (Fri, 13 Aug 2021 20:02:38 GMT):
if you go to any PR and press `.` you get VSCode running in-browser
nguyer (Fri, 13 Aug 2021 20:03:02 GMT):
Yeah I need to play around with this some more. Looks very cool. I've been tinkering with running my own VS Code in a browser instance for a few years on and off in my free time. Having GitHub run one for me sounds nice
rjones (Fri, 13 Aug 2021 20:04:16 GMT):
it's much like Gerrit in that on a PR, it shows only the diffs and comments inline
nguyer (Fri, 13 Aug 2021 20:04:31 GMT):
Screen Shot 2021-08-13 at 4.04.23 PM.png
rjones (Fri, 13 Aug 2021 20:05:02 GMT):
yeah, it's distinct from codespaces.
rjones (Fri, 13 Aug 2021 20:05:13 GMT):
look at this one: https://github.dev/hyperledger/fabric/pull/2805 it has comments etc
nguyer (Fri, 13 Aug 2021 20:05:57 GMT):
That's cool
Andrew.Richardson (Mon, 16 Aug 2021 16:50:05 GMT):
@nguyer I'm currently getting an error when attempting to init a stack with the latest version of CLI:
```
andrew@Andrews-MacBook:~/workspace/firefly-cli$ go run ff/main.go init -e1 token 2
initializing new FireFly stack...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x68 pc=0x13d1fad]
```
Is this fallout from your merge?
nguyer (Mon, 16 Aug 2021 16:52:32 GMT):
Let me check. I know that branch was good before the merge, but that doesn't look right...
nguyer (Mon, 16 Aug 2021 16:53:10 GMT):
There's a bug with the external flag. Let me fix that real quick
Andrew.Richardson (Mon, 16 Aug 2021 16:54:57 GMT):
ok. I also notice that it's trying to use postgres even if I pass sqlite3
Andrew.Richardson (Mon, 16 Aug 2021 16:55:10 GMT):
maybe related?
nguyer (Mon, 16 Aug 2021 16:55:19 GMT):
Okay I'll look at that too
Andrew.Richardson (Mon, 16 Aug 2021 16:55:57 GMT):
but didn't the unit tests pass on the... oh wait 😜
nguyer (Mon, 16 Aug 2021 16:56:22 GMT):
That's a known issue https://github.com/hyperledger-labs/firefly-cli/issues/7
Andrew.Richardson (Mon, 16 Aug 2021 16:57:42 GMT):
Thanks. I think I got [#79](https://github.com/hyperledger-labs/firefly-cli/pull/79) rebased onto the latest, just want to test it before I re-upload.
Andrew.Richardson (Mon, 16 Aug 2021 16:58:20 GMT):
Well, more of a "redo" than a "rebase" since I added token providers alongside the blockchain providers.
nguyer (Mon, 16 Aug 2021 17:26:18 GMT):
@Andrew.Richardson This should fix those problems https://github.com/hyperledger-labs/firefly-cli/pull/84
avadam (Mon, 16 Aug 2021 17:27:57 GMT):
Has joined the channel.
Andrew.Richardson (Mon, 16 Aug 2021 18:55:26 GMT):
https://github.com/hyperledger-labs/firefly-cli/pull/79 is now reworked on top of the latest, and adds basic support for token providers to the CLI.
nguyer (Tue, 17 Aug 2021 15:15:42 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-08-18+FireFly+Community+Call
Thursday, August 18, 2021 8:00 AM PTJoin link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:Project UpdatesTokens supportFabric / fabconnectFireFly CLI multi-ledger supportEvent Sequencing and Aggregation - Part II (Peter Broadhurst)We'll do a deeper dive to talk about exactly how FireFly provides its ordering guaranteesOpen discussionAs always, thank you all for your participation in these calls! We hope to see you there!
nguyer (Tue, 17 Aug 2021 15:17:08 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-08-18+FireFly+Community+Call
Thursday, August 18, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Project Updates
- Tokens supportFabric / fabconnect
- FireFly CLI multi-ledger support
- Event Sequencing and Aggregation - Part II (Peter Broadhurst)
- We'll do a deeper dive to talk about exactly how FireFly provides its ordering guarantees
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
nguyer (Tue, 17 Aug 2021 15:17:08 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-08-18+FireFly+Community+Call
Wednesday, August 18, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Project Updates
- Tokens supportFabric / fabconnect
- FireFly CLI multi-ledger support
- Event Sequencing and Aggregation - Part II (Peter Broadhurst)
- We'll do a deeper dive to talk about exactly how FireFly provides its ordering guarantees
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
mona15 (Thu, 19 Aug 2021 23:24:35 GMT):
Has joined the channel.
mona15 (Thu, 19 Aug 2021 23:24:35 GMT):
Hi,
mona15 (Thu, 19 Aug 2021 23:25:06 GMT):
I have a question regarding ff cli. I have docker and latest golang installed on my mac
mona15 (Thu, 19 Aug 2021 23:25:48 GMT):
I successfully did go install of github cli, however when I attempt to execute any ff cmd it does not recognize it in terminal
mona15 (Thu, 19 Aug 2021 23:26:40 GMT):
even weirder was randomly it recognized the ff init command for me to create a stack, however I reopened terminal and now it is again not recognizing the ff command
mona15 (Thu, 19 Aug 2021 23:26:56 GMT):
has anyone come across this issue before? I am a total new comer to firefly
mona15 (Fri, 20 Aug 2021 00:02:31 GMT):
Hello everyone!
nguyer (Fri, 20 Aug 2021 12:35:55 GMT):
Hi @mona15 ! :wave: Welcome!
LeslytH (Tue, 24 Aug 2021 11:23:34 GMT):
Has joined the channel.
LeslytH (Tue, 24 Aug 2021 11:23:34 GMT):
Hello!
nguyer (Tue, 24 Aug 2021 12:41:57 GMT):
Welcome @LeslytH ! :wave:
davidwboswell (Thu, 26 Aug 2021 15:45:11 GMT):
there is a meetup happening next thursday, sep 2 being hosted by the hyperledger india chapter about firefly: "Getting started building apps on FireFly and contributing to Open Source". everyone here is welcome to attend. and if the timing doesn't work for you to join live, we'll share the recording after. and it would be great to get your help sharing the word about this. please feel free to share the link to the meetup: https://www.meetup.com/Hyperledger-Bangalore/events/280318418/
nguyer (Thu, 26 Aug 2021 15:48:43 GMT):
Thanks @davidwboswell !
KingAlawaka (Sun, 29 Aug 2021 21:10:18 GMT):
Has joined the channel.
KingAlawaka (Sun, 29 Aug 2021 21:10:19 GMT):
Hello everyone, I am new to open source projects and Blockchain... So my questions sound bad but I will ask them anyway. 1) I recently up firefly CLI stack and I am trying to use some API calls... but 127.0.0.1:5000/ui is working but not the /api/v1 am I missing something here? 2) if I want to change the look and feel of the web interface how can change those things? Thanks in advance and sorry for asking very generic questions...hope to engage more with the firefly community :D
Andrew.Richardson (Mon, 30 Aug 2021 14:22:06 GMT):
@KingAlawaka welcome! You should be able view the generated API at http://127.0.0.1:5000/api. The web interface is provided by the UI project at https://github.com/hyperledger-labs/firefly-ui - if you want to play around with it, you can clone and run another instance of the UI and point it toward your backend by modifying the UI's proxy port here: https://github.com/hyperledger-labs/firefly-ui/blob/9168e9cb8501461666d5f99a4e39322281ab553f/package.json#L70
Andrew.Richardson (Mon, 30 Aug 2021 14:22:45 GMT):
Hope that helps, definitely feel free to ask more questions.
KingAlawaka (Mon, 30 Aug 2021 14:33:46 GMT):
Thanks a lot Andrew :D I will try this... Thanks again
nguyer (Tue, 31 Aug 2021 14:58:20 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-09-01+FireFly+Community+Call
Wednesday, September 1, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Demo of fabconnect and FireFly using Fabric
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
sukrutsathaye (Wed, 01 Sep 2021 13:18:43 GMT):
I noticed that when I restart the stacks after a system restart, the ui and api urls aren't reachable until I reset the stack. This happened two times now. And I think I hadn't stopped the stacks while shutting down the computer. Maybe someone can also try it out and check
nguyer (Wed, 01 Sep 2021 13:19:25 GMT):
Hmm is this with Besu only or any configuration?
sukrutsathaye (Wed, 01 Sep 2021 13:19:43 GMT):
no with geth
nguyer (Wed, 01 Sep 2021 13:20:10 GMT):
Okay that sounds like a problem. Do you see the same behavior if you `ff stop` and then `ff start` the same stack without rebooting?
sukrutsathaye (Wed, 01 Sep 2021 13:21:18 GMT):
I never tested it without rebooting. I ll test it now and get back to you
sukrutsathaye (Wed, 01 Sep 2021 13:22:15 GMT):
I did however try stopping and starting stacks again after rebooting, but same issue, unless I reset
nguyer (Wed, 01 Sep 2021 13:22:38 GMT):
Okay. I'll try to reproduce that here in a few minutes too
nguyer (Wed, 01 Sep 2021 13:22:59 GMT):
That's definitely not the expected behavior
sukrutsathaye (Wed, 01 Sep 2021 13:23:03 GMT):
so The same behavior is observed after stopping and starting again
sukrutsathaye (Wed, 01 Sep 2021 13:23:14 GMT):
I just checked
nguyer (Wed, 01 Sep 2021 13:23:29 GMT):
Interesting. Well at least it's consistent :)
sukrutsathaye (Wed, 01 Sep 2021 13:23:47 GMT):
hahaha yeah, could be easier to debug
nguyer (Wed, 01 Sep 2021 13:23:59 GMT):
I'll look into it. Thanks for reporting it
sukrutsathaye (Wed, 01 Sep 2021 13:24:21 GMT):
my pleasure! :)
nguyer (Wed, 01 Sep 2021 14:17:14 GMT):
@sukrutsathaye I've repro'd the issue you reported with stopping and starting a stack. Looks like the new tokens connector is not coming up cleanly the second time.
nguyer (Wed, 01 Sep 2021 14:17:14 GMT):
@sukrutsathaye I've repro'd the issue you reported with stopping and starting a stack. Looks like firefly core is having trouble connecting to the tokens connector when it comes up the second time
sukrutsathaye (Wed, 01 Sep 2021 14:17:52 GMT):
perfect!
sukrutsathaye (Wed, 01 Sep 2021 16:02:56 GMT):
Great job guys!
It was a very information packed call! Thanks Peter for answering my question
nguyer (Thu, 02 Sep 2021 12:02:53 GMT):
Good morning! The FireFly CLI was updated to v0.0.30 last night, which fixes an issue reported above regarding restarting a stack. The CLI can be upgraded by running `go install github.com/hyperledger-labs/firefly-cli/ff@latest`
nguyer (Thu, 02 Sep 2021 12:04:19 GMT):
Also, just a reminder, we have a Developer Workshop starting in about 25 minutes. It's a great chance to get together and get a local development environment set up to start building apps on FireFly or contributing to the FireFly codebase itself. Details are here: https://www.meetup.com/Hyperledger-Bangalore/events/280318418 Hope to see a lot of you there!
nguyer (Thu, 02 Sep 2021 12:04:19 GMT):
*Also, just a reminder, we have a Developer Workshop starting in about 25 minutes.* It's a great chance to get together and get a local development environment set up to start building apps on FireFly or contributing to the FireFly codebase itself. Details are here: https://www.meetup.com/Hyperledger-Bangalore/events/280318418 Hope to see a lot of you there!
janrockdev (Thu, 02 Sep 2021 13:18:59 GMT):
[ ](https://chat.hyperledger.org/channel/firefly-lab?msg=CFnQKZnrTsw8s4svP) fabric branch? ;)
nguyer (Thu, 02 Sep 2021 13:34:42 GMT):
I will merge the fix into that branch this morning as well
nguyer (Thu, 02 Sep 2021 20:28:18 GMT):
Hi all! I have uploaded the recording from yesterday's community call to our wiki page: https://wiki.hyperledger.org/display/labs/2021-09-01+FireFly+Community+Call This has the recording of the demo of FireFly using Fabric. There was a lot of interest around this, so just wanted to let folks know in case they didn't get to watch it live.
davidwboswell (Mon, 06 Sep 2021 15:24:06 GMT):
the video of the recent firefly workshop hosted by the hyperledger india chapter is now available at: https://www.youtube.com/watch?v=GATt2kq8D3c
ROHAN_SHROTHRIUM (Mon, 06 Sep 2021 18:18:26 GMT):
Has joined the channel.
mwklein (Fri, 10 Sep 2021 14:24:17 GMT):
Has joined the channel.
shemnon (Tue, 14 Sep 2021 16:37:04 GMT):
Sorry for missing the past few community calls, I have a work meeting at that time now. Has there been any discussion of raising the incubation discussion on the TSC call? I think the two biggest concerns (fabric smart client overlap and time as open source) have been resolved from my perspective. Interested to hear the maintainers take.
nguyer (Tue, 14 Sep 2021 16:56:47 GMT):
No worries! Good question. It hasn't come up in detailed discussion, but we are actually planning on talking about it a bit in tomorrow's call (I'm about to send out the agenda for that).
nguyer (Tue, 14 Sep 2021 17:48:06 GMT):
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/labs/2021-09-15+FireFly+Community+Call
Wednesday, September 15, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- FireFly project update and progress toward Incubation (Nicko Guyer)
- Update on progress of Tokens in FireFly and demo (Andrew Richardson)
- Giving Chain project update and use of FireFly (Bobbi Muscara)
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
bobbh (Thu, 16 Sep 2021 12:30:34 GMT):
Has joined the channel.
nguyer (Thu, 16 Sep 2021 16:51:35 GMT):
Hi @bobbh welcome! :wave:
OscarTBallester (Fri, 17 Sep 2021 13:08:11 GMT):
Has joined the channel.
OscarTBallester (Fri, 17 Sep 2021 13:08:12 GMT):
HI every one!
OscarTBallester (Fri, 17 Sep 2021 13:09:46 GMT):
I was working with firefly the last week and I need some guidance, where can I look to know how to add new nodes to an existent network? Thanks!
nguyer (Fri, 17 Sep 2021 14:18:09 GMT):
Hi @OscarTBallester welcome! :wave:
nguyer (Fri, 17 Sep 2021 14:20:27 GMT):
You can register a node with the network by posting to the `/network/register/node/organization/` endpoint. You can see the code in the FireFly CLI that does this here: https://github.com/hyperledger-labs/firefly-cli/blob/main/internal/stacks/firefly_identity.go#L27
nguyer (Fri, 17 Sep 2021 14:51:35 GMT):
Actually, that URL is for registering the Org. To add a node to the org the URL is `/network/register/node`
OscarTBallester (Fri, 17 Sep 2021 15:03:42 GMT):
Thanks for your answer, I saw that endpoint but appears as deprecated and with no info about payload, I mean in the API Spec
OscarTBallester (Fri, 17 Sep 2021 15:04:02 GMT):
So what payload I should use?
nguyer (Fri, 17 Sep 2021 21:37:21 GMT):
Good question. I didn't realize that one was deprecated now. Let me get back to you on that in a bit
OscarTBallester (Mon, 20 Sep 2021 11:11:14 GMT):
Ok, thanks. We are very interested in Firefly and the register node endpoint is a key feature for us.
nguyer (Mon, 20 Sep 2021 13:18:37 GMT):
Okay. I had a chance to test this. The new API endpoints are very similar. There is a new query parameter that you can include `?confirm=true` which will cause the HTTP request to block until registration succeeds, so you don't have to write polling code either.
nguyer (Mon, 20 Sep 2021 13:19:19 GMT):
So to register the org, `POST` to `network/organizations/self`. Then to register the node, `POST` to `network/nodes/self`
OscarTBallester (Mon, 20 Sep 2021 13:20:34 GMT):
Ok, so I need to call this endpoint from another node, isn't it?
nguyer (Mon, 20 Sep 2021 13:27:15 GMT):
Something just needs to call this endpoint after the node starts up, to tell the node that it should register itself
nguyer (Mon, 20 Sep 2021 13:27:46 GMT):
It doesn't need to be another FireFly node. It could be curl, postman, or your own custom app
OscarTBallester (Mon, 20 Sep 2021 13:29:35 GMT):
I mean, if I have a network working and I want to add a new node, how can I do it?
nguyer (Mon, 20 Sep 2021 13:46:58 GMT):
You just have to run the node, and post to that endpoint. If the node belongs to an org that is already registered, you can skip the call to `/network/organizations/self` when adding the new node
OscarTBallester (Mon, 20 Sep 2021 13:54:12 GMT):
So the node should be in the same eth network? Or how the node knows into which network should register itself?
nguyer (Mon, 20 Sep 2021 14:12:01 GMT):
The FireFly config file should have a `blockchain` section defined which allows it to connect to the same blockchain that the rest of the FireFly nodes in the network are connected to. This is what allows the new node to broadcast its presence to the other nodes, through a blockchain event
OscarTBallester (Mon, 20 Sep 2021 14:15:07 GMT):
Ah! Ok thanks, so where is this file located?
nguyer (Mon, 20 Sep 2021 14:24:22 GMT):
It can be anywhere on the filesystem. To point to the config file, use the `-f
OscarTBallester (Mon, 20 Sep 2021 14:24:54 GMT):
Ok, thank you so much!
nguyer (Mon, 20 Sep 2021 14:25:14 GMT):
https://github.com/hyperledger-labs/firefly/blob/main/internal/config/config.go#L332-L352
nguyer (Mon, 20 Sep 2021 14:26:33 GMT):
Sure! happy to help
OscarTBallester (Mon, 20 Sep 2021 17:50:15 GMT):
Hi again, I read about a strong member governance in Firefly but I can't find any info about that in the API spec, can you say me how it works? Thank you again!
nguyer (Mon, 20 Sep 2021 17:59:58 GMT):
Hi Oscar. This is an area that is being very actively worked on right now. There are quite a few details in https://github.com/hyperledger-labs/firefly/issues/187
OscarTBallester (Mon, 20 Sep 2021 18:02:43 GMT):
Ok, thank you. I thought it was available now because I read about it as a current feature in the Firefly webpage.
nguyer (Mon, 20 Sep 2021 18:04:08 GMT):
Which page are you looking at? Maybe I can elaborate a bit more on that
OscarTBallester (Mon, 20 Sep 2021 18:04:37 GMT):
https://www.kaleido.io/hyperledger-firefly
OscarTBallester (Mon, 20 Sep 2021 18:06:17 GMT):
There is some features marked as "Coming soon" but Member Governance is there as a current feature.
OscarTBallester (Mon, 20 Sep 2021 18:07:11 GMT):
But I mean is ok, it is interesting for us but we can do it at the application level.
nguyer (Mon, 20 Sep 2021 18:07:39 GMT):
Ah yeah. The short answer is, there are some things that page talks about that are still under development.
OscarTBallester (Mon, 20 Sep 2021 18:09:19 GMT):
So, maybe the API spec is a better information source, right?
nguyer (Mon, 20 Sep 2021 18:10:33 GMT):
Yes. Things on GitHub or the docs site (https://labs.hyperledger.org/firefly/)(which is automatically built from source on merge to `main`) are the most accurate and up to date
nguyer (Mon, 20 Sep 2021 18:10:33 GMT):
Yes. Things on GitHub or the docs site (https://labs.hyperledger.org/firefly/) (which is automatically built from source on merge to `main`) are the most accurate and up to date
OscarTBallester (Mon, 20 Sep 2021 18:11:31 GMT):
Thanks, I really appreciate your help
nguyer (Mon, 20 Sep 2021 18:13:02 GMT):
Sure!
OscarTBallester (Tue, 21 Sep 2021 15:13:29 GMT):
Hi Nicko,
I was testing with data_types and data and I have a couple of questions:
- POST to namespace/default/data, I have a data_type called company and I want to create a company and then "modify it", I know we cannot edit the data itself but I'm trying to use de dataid to send again the info with changes but this creates another different id so I lost the trace.
- POST to namespace/default/data, the system checks if the data_type is defined but is not checking yet if the attributes are correct, right?
Thanks again and sorry, I'm working on an mvp and I really want to push forward with Firefly.
nguyer (Tue, 21 Sep 2021 20:50:07 GMT):
Hey sorry just saw this
nguyer (Tue, 21 Sep 2021 20:54:31 GMT):
There is no way to update or modify uploaded data without assigning it a new ID. If there was, this would allow someone to "rewrite history". If this data was pinned to the blockchain, you can't change what the blockchain points to.
nguyer (Tue, 21 Sep 2021 20:54:58 GMT):
If you could describe your use case a bit more, perhaps I could guide you to a pattern that does work in firefly.
OscarTBallester (Tue, 21 Sep 2021 21:01:18 GMT):
It is just what I said, we have some companies and I want to have the possibility to update some data
OscarTBallester (Tue, 21 Sep 2021 21:01:37 GMT):
Thanks!
nguyer (Tue, 21 Sep 2021 21:05:02 GMT):
On your second question, if the data is JSON and you have defined a custom data type, FireFly will validate that the required fields are present when you upload the data
OscarTBallester (Tue, 21 Sep 2021 21:06:12 GMT):
I defined a datatype company with the fields we need and I sent it using the data endpoint. Maybe there is a better way to do it.
OscarTBallester (Tue, 21 Sep 2021 21:06:33 GMT):
I'm talking about first question
nguyer (Tue, 21 Sep 2021 21:20:49 GMT):
Makes sense. You probably also want to define another datatype that is something like `CompanyUpdateEvent` which is what you would send any time you want to update the existing company record.
nguyer (Tue, 21 Sep 2021 21:21:39 GMT):
If each message related to a specific company is sent using the same `topic`, they will be ordered, and you can also query the messages on that topic via the API to see the update history
OscarTBallester (Tue, 21 Sep 2021 21:22:45 GMT):
aaaaa ok
OscarTBallester (Tue, 21 Sep 2021 21:22:52 GMT):
Thank you so much
OscarTBallester (Tue, 21 Sep 2021 21:23:01 GMT):
That's a good point
OscarTBallester (Tue, 21 Sep 2021 21:26:05 GMT):
Which endpoint I should use?
OscarTBallester (Tue, 21 Sep 2021 21:33:18 GMT):
Ok, I think I got it, I need to post the type and then broadcast with the topic, and ask the message by topic, I'm right?
OscarTBallester (Tue, 21 Sep 2021 21:34:52 GMT):
post data between type and message, between typew and message posting*
OscarTBallester (Tue, 21 Sep 2021 21:34:52 GMT):
post data between type and message posting*
scaraclette (Tue, 21 Sep 2021 21:44:47 GMT):
Has joined the channel.
nguyer (Wed, 22 Sep 2021 12:39:13 GMT):
Yes that's exactly right
nguyer (Wed, 22 Sep 2021 12:40:45 GMT):
You _could_ also just put the data inline in your message when you POST to `messages/broadcast`. This would be a simpler flow. But what you described would allow a bit more flexibility if you wanted to send the same data item again in another message later for example
OscarTBallester (Wed, 22 Sep 2021 12:42:08 GMT):
Yes, but I need the id to set the reference.
nguyer (Wed, 22 Sep 2021 12:42:25 GMT):
Welcome @scaraclette :wave:
OscarTBallester (Wed, 22 Sep 2021 12:42:40 GMT):
Thank you so much, it was really helpful.
nguyer (Wed, 22 Sep 2021 12:43:39 GMT):
Yes, if you want to give the _data itself_ (separate of them message it was sent in) a unique ID in the system, this is when it makes sense to post the data ahead of time, and then attach it to a message after
OscarTBallester (Wed, 22 Sep 2021 12:44:53 GMT):
Yes, I'm working on that way now.
nguyer (Wed, 22 Sep 2021 12:45:08 GMT):
:+1:
nguyer (Wed, 22 Sep 2021 12:45:25 GMT):
Good luck on your MVP and I'm here to help if you have more questions about FireFly
OscarTBallester (Wed, 22 Sep 2021 12:46:23 GMT):
Thank you! I´ll keep you updated :)
scaraclette (Wed, 22 Sep 2021 15:03:36 GMT):
Hi, @nguyer thank you for the welcome! I'm Scarlett and currently a rising senior CS student.
I'm here because I'm hoping Firefly can be my first open source contribution since it's still early on in development, has great documentation, and what I think the project is trying to achieve is super awesome. Right now, I'm just going through the YouTube videos for demos and will be testing out local development.
I have experience in TypeScript from past internships and am currently learning Golang (used Rust in a previous internship, and so far I love how straight forward Go looks). Definitely interested in joining the next meetup whenever it happens.
nguyer (Wed, 22 Sep 2021 15:05:56 GMT):
Awesome! So glad you're here! I'd be happy to help you get started contributing. Let me know how I can help!
scaraclette (Wed, 22 Sep 2021 15:13:24 GMT):
Thanks, I'm planning to run things locally to test out dev environment today. If something looks confusing, will go through chat to see if anyone had a similar issue, and/or create a new thread for dev setup :pray:
nguyer (Wed, 22 Sep 2021 15:45:45 GMT):
Sounds good!
OscarTBallester (Wed, 22 Sep 2021 20:26:10 GMT):
Hi again!
The update system works like a charm, I just need some help uploading big files from PHP... any example? Thanks again Nicko!
nguyer (Wed, 22 Sep 2021 20:28:18 GMT):
Great! Hmm I haven't written anything in PHP in the better part of a decade now... I don't have any examples readily available of uploading a file using PHP, but I'm sure Google could turn up some examples
OscarTBallester (Wed, 22 Sep 2021 20:41:11 GMT):
But I mean, which fields are waiting for the endpoint? I know is the data endpoint but where I should put the file value?
nguyer (Wed, 22 Sep 2021 20:50:13 GMT):
FireFly uses a standard multi-part form post to upload a file to the data endpoint
nguyer (Wed, 22 Sep 2021 20:50:37 GMT):
There's an example of how to do it using `curl` here: https://labs.hyperledger.org/firefly/gettingstarted/private_send.html#multipart-form-post-of-a-file
OscarTBallester (Wed, 22 Sep 2021 20:53:47 GMT):
I tried to replicate this example in PHP but it returns {"error":"FF10130: Invalid content type"} ... I keep it trying, thank you
nguyer (Wed, 22 Sep 2021 21:08:29 GMT):
Okay sounds good. If you do suspect there's an issue with FireFly feel free to post here in RocketChat or open an issue on GitHub. I suspect it's just the way the client code is doing the upload though. I haven't heard of any issues with uploading to the /data endpoint
OscarTBallester (Thu, 23 Sep 2021 17:41:43 GMT):
I'm trying with postman but gives me this error: "error": "FF10116: Database insert failed: NOT NULL constraint failed: data.value".
I'm using: form-data, adding a file with "file" as a key, and the auto-generated headers. What I'm doing wrong? Thanks again!
nguyer (Thu, 23 Sep 2021 18:01:55 GMT):
Are you able to send me the postman request that you're using so I can try?
OscarTBallester (Thu, 23 Sep 2021 19:29:21 GMT):
{
"info": {
"_postman_id": "a9f0b237-c08c-4f34-b780-fb9af85cabfe",
"name": "MVP",
"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
},
"item": [
{
"name": "localhost:5000/api/v1/namespaces/default/data",
"request": {
"method": "POST",
"header": [],
"body": {
"mode": "formdata",
"formdata": [
{
"key": "file",
"type": "file",
"src": "/C:/Users/Oscar/Downloads/Untitled Diagram.jpg"
}
],
"options": {
"raw": {
"language": "json"
}
}
},
"url": {
"raw": "localhost:5000/api/v1/namespaces/default/data",
"host": [
"localhost"
],
"port": "5000",
"path": [
"api",
"v1",
"namespaces",
"default",
"data"
]
}
},
"response": []
}
]
}
OscarTBallester (Thu, 23 Sep 2021 19:30:18 GMT):
Sorry I tried to attach the file but I couldn't
nguyer (Thu, 23 Sep 2021 19:30:46 GMT):
np
nguyer (Thu, 23 Sep 2021 19:30:50 GMT):
Let me try this
OscarTBallester (Thu, 23 Sep 2021 19:37:49 GMT):
Thank!
nguyer (Thu, 23 Sep 2021 19:39:20 GMT):
Try adding another field on your multi-part form called `autometa` with a value of `true`
nguyer (Thu, 23 Sep 2021 19:39:20 GMT):
Try adding another field on your multi-part form called `autometa` with a value of `true` and make it the first field in the form (before `file`)
OscarTBallester (Thu, 23 Sep 2021 19:39:43 GMT):
ok
OscarTBallester (Thu, 23 Sep 2021 19:41:47 GMT):
"error": "FF10218: Error reading multi-part form input: EOF"
nguyer (Thu, 23 Sep 2021 19:42:08 GMT):
Hmm that worked for me in postman
OscarTBallester (Thu, 23 Sep 2021 19:43:24 GMT):
Oh, I don't know....
nguyer (Thu, 23 Sep 2021 19:43:45 GMT):
Did you try it with Postman too and you got that error?
OscarTBallester (Thu, 23 Sep 2021 19:43:58 GMT):
yup
nguyer (Thu, 23 Sep 2021 19:45:23 GMT):
Hmm. I'm using the same exact postman request you sent me, except I added autometa: true before the file, and I selected a different file on my disk
nguyer (Thu, 23 Sep 2021 19:45:43 GMT):
Have you tried a different file?
OscarTBallester (Thu, 23 Sep 2021 19:46:14 GMT):
I changed the file and worked
OscarTBallester (Thu, 23 Sep 2021 19:46:35 GMT):
thank you
nguyer (Thu, 23 Sep 2021 19:48:30 GMT):
Perfect!
OscarTBallester (Thu, 23 Sep 2021 19:48:52 GMT):
Can I add a datatype to this?
nguyer (Thu, 23 Sep 2021 19:49:55 GMT):
Yes
OscarTBallester (Thu, 23 Sep 2021 19:50:35 GMT):
I can do it posting another data linked with the file ID maybe
nguyer (Thu, 23 Sep 2021 19:54:32 GMT):
There's a way to do it in the same request... it's not in the docs yet though :( hold on...
nguyer (Thu, 23 Sep 2021 20:02:36 GMT):
Okay, so there is actually an open issue around this. I think Peter is planning on tackling this one in the next day or two: https://github.com/hyperledger/firefly/issues/198
OscarTBallester (Thu, 23 Sep 2021 20:03:32 GMT):
Ok, I'll check it
OscarTBallester (Thu, 23 Sep 2021 20:03:52 GMT):
And any clues about how get the file from Firefly?
nguyer (Thu, 23 Sep 2021 20:07:38 GMT):
Sure, if you want to download the original file again, you can do a GET to localhost:5000/api/v1/namespaces/default/data/{dataId}/blob
nguyer (Thu, 23 Sep 2021 20:07:38 GMT):
Sure, if you want to download the original file again, you can do a GET to http://localhost:5000/api/v1/namespaces/default/data/{dataId}/blob
OscarTBallester (Thu, 23 Sep 2021 20:09:21 GMT):
Oh, thanks!
OscarTBallester (Thu, 23 Sep 2021 20:11:25 GMT):
It was really helpful, thank you again for your patience! :)
nguyer (Thu, 23 Sep 2021 20:13:24 GMT):
Sure! Happy to help
rjones (Thu, 23 Sep 2021 20:16:41 GMT):
Room name changed to: firefly by rjones
reddevil (Fri, 24 Sep 2021 15:06:44 GMT):
Has joined the channel.
scaraclette (Fri, 24 Sep 2021 18:00:08 GMT):
@nguyer dev environment setup thread:
scaraclette (Fri, 24 Sep 2021 18:04:50 GMT):
So based on the contributor workshop, I managed to follow it and have done the following steps (putting it here in case it might be useful for others in the future):
1. Fork repository
2. Clone forked
3. Run `make`
4. Run `go install`
5. Create a new stack with the command `ff init --external 1`. Choose the name and number of nodes. For example, use the name `dev_1` as stack name and 2 number of nodes.
6. Start stack within repo folder. `ff start dev_1`
7. Set environment variable in `launch.json` to point to that debug stack. By default it's pointed to `${env:HOME}/.firefly/stacks/dev/configs/firefly_core_0.yml`, change the `stacks/dev` to the new debug stack name `stacks/dev_1`
8. Create config file and place it in...?
So, everything looks good but it's asking for a `firefly.core` config file. I'm assuming we create the config file based on an example seen in the test/data/config folder https://github.com/hyperledger/firefly/blob/main/test/data/config/firefly.core.yaml. If that's the case, where is the best place to put the config?
If I did `go install` it'll move it to my GOPATH, so I wasn't sure where to put the config file.
Right now, the error when running Core Firefly is:
FF10101: Failed to read config: Config File "firefly.core" Not Found in "[/etc/firefly /Users/scarlett/.firefly /Users/scarlett/Desktop/open_source/project_firefly/firefly]"
scaraclette (Fri, 24 Sep 2021 18:04:50 GMT):
So based on the contributor workshop, I managed to follow it and have done the following steps (putting it here in case it might be useful for others in the future):
1. Fork repository
2. Clone forked
3. Run `make`
4. Run `go install`
5. Create a new stack with the command `ff init --external 1`. Choose the name and number of nodes. For example, use the name `dev_1` as stack name and 2 number of nodes.
6. Start stack within repo folder. `ff start dev_1`
7. Set environment variable in `launch.json` to point to that debug stack. By default it's pointed to `${env:HOME}/.firefly/stacks/dev/configs/firefly_core_0.yml`, change the `stacks/dev` to the new debug stack name `stacks/dev_1`
8. Create config file and place it in...?
So, everything looks good but it's asking for a `firefly.core` config file. I'm assuming we create the config file based on an example seen in the test/data/config folder https://github.com/hyperledger/firefly/blob/main/test/data/config/firefly.core.yaml. If that's the case, where is the best place to put the config?
If I did `go install` it'll move it to my GOPATH, so I wasn't sure where to put the config file.
Right now, the error when running Core Firefly is:
FF10101: Failed to read config: Config File "firefly.core" Not Found in "[/etc/firefly /Users/scarlett/.firefly /Users/scarlett/Desktop/open_source/project_firefly/firefly]"
scaraclette (Fri, 24 Sep 2021 18:04:50 GMT):
So based on the contributor workshop, I managed to follow it and have done the following steps (putting it here in case it might be useful for others in the future):
1. Fork repository
2. Clone forked
3. Run `make`
4. Run `go install`
5. Create a new stack with the command `ff init --external 1`. Choose the name and number of nodes. For example, use the name `dev_1` as stack name and 2 number of nodes.
6. Start stack within repo folder. `ff start dev_1`
7. Set environment variable in `launch.json` to point to that debug stack. By default it's pointed to `${env:HOME}/.firefly/stacks/dev/configs/firefly_core_0.yml`, change the `stacks/dev` to the new debug stack name `stacks/dev_1`
8. Create config file and place it in...?
So, everything looks good but it's asking for a `firefly.core` config file. I'm assuming we create the config file based on an example seen in the test/data/config folder https://github.com/hyperledger/firefly/blob/main/test/data/config/firefly.core.yaml. If that's the case, where is the best place to put the config?
If I did `go install` it'll move it to my GOPATH, so I wasn't sure where to put the config file.
Right now, the error when running Core Firefly is:
FF10101: Failed to read config: Config File "firefly.core" Not Found in "[/etc/firefly /Users/scarlett/.firefly /Users/scarlett/Desktop/open_source/project_firefly/firefly]"
**[UPDATE: revised and completed steps]**
Got a bit confused understanding how a config file was pointed, it turns out we're suppose to run Firefly to point to the generated config file from CLI.
Steps:
1. Fork repository
2. Clone forked
3. Run `make`
4. Run `go install`
5. Create a new stack with the command `ff init --external 1`. Choose the name and number of nodes. For example, use the name `dev_1` as stack name and 2 number of nodes.
6. Run `ff start dev_1`, wait until the stack starts, and copy-paste config location when running Firefly core. Example message `please start your firefly core with the config file for this stack: firefly -f /Users/scarlett/.firefly`
7. Within repo directory, run: `firefly -f /Users/scarlett/.firefly`
8. [For VSCode, to enable debugger]: Change `launch.json` file to point out to stack.
scaraclette (Fri, 24 Sep 2021 18:04:50 GMT):
So based on the contributor workshop, I managed to follow it and have done the following steps (putting it here in case it might be useful for others in the future):
1. Fork repository
2. Clone forked
3. Run `make`
4. Run `go install`
5. Create a new stack with the command `ff init --external 1`. Choose the name and number of nodes. For example, use the name `dev_1` as stack name and 2 number of nodes.
6. Start stack within repo folder. `ff start dev_1`
7. Set environment variable in `launch.json` to point to that debug stack. By default it's pointed to `${env:HOME}/.firefly/stacks/dev/configs/firefly_core_0.yml`, change the `stacks/dev` to the new debug stack name `stacks/dev_1`
8. Create config file and place it in...?
So, everything looks good but it's asking for a `firefly.core` config file. I'm assuming we create the config file based on an example seen in the test/data/config folder https://github.com/hyperledger/firefly/blob/main/test/data/config/firefly.core.yaml. If that's the case, where is the best place to put the config?
If I did `go install` it'll move it to my GOPATH, so I wasn't sure where to put the config file.
Right now, the error when running Core Firefly is:
FF10101: Failed to read config: Config File "firefly.core" Not Found in "[/etc/firefly /Users/scarlett/.firefly /Users/scarlett/Desktop/open_source/project_firefly/firefly]"
**[UPDATE: revised and completed steps]**
Got a bit confused understanding how a config file was pointed, it turns out we're suppose to run Firefly to point to the generated config file from CLI.
Steps:
1. Fork repository
2. Clone forked
3. Run `make`
4. Run `go install`
5. Create a new stack with the command `ff init --external 1`. Choose the name and number of nodes. For example, use the name `dev_1` as stack name and 2 number of nodes.
6. Run `ff start dev_1`, wait until the stack starts, and copy-paste config location when running Firefly core. Example message `please start your firefly core with the config file for this stack: firefly -f /Users/scarlett/.firefly`
7. Within repo directory, run: `firefly -f /Users/scarlett/.firefly`
8. [For VSCode, to enable debugger]: Change `launch.json` file to point out to stack name.
nguyer (Fri, 24 Sep 2021 18:18:44 GMT):
Looks like you're doing great!
nguyer (Fri, 24 Sep 2021 18:19:04 GMT):
So if you ran `ff init -e 1 ...` the CLI should have generated the config file for you
nguyer (Fri, 24 Sep 2021 18:19:29 GMT):
When you run `ff start ...` it will pause at the point where you need to run FireFly on your host machine
nguyer (Fri, 24 Sep 2021 18:19:50 GMT):
The CLI will also print out the command you should run, including the path to the config file
nguyer (Fri, 24 Sep 2021 18:20:27 GMT):
If you're using VS Code, I would recommend using the launch configuration that's in the repo, as it's already set up to point to a config file for a stack called `dev`
scaraclette (Fri, 24 Sep 2021 18:24:31 GMT): nguyer (Fri, 24 Sep 2021 18:24:54 GMT): nguyer (Fri, 24 Sep 2021 18:25:10 GMT): scaraclette (Fri, 24 Sep 2021 18:25:23 GMT): nguyer (Fri, 24 Sep 2021 18:26:01 GMT): scaraclette (Fri, 24 Sep 2021 18:43:54 GMT): nguyer (Fri, 24 Sep 2021 18:48:16 GMT): janrockdev (Mon, 27 Sep 2021 13:49:58 GMT): nguyer (Mon, 27 Sep 2021 15:51:30 GMT): upmagupta (Mon, 27 Sep 2021 16:36:49 GMT): upmagupta (Mon, 27 Sep 2021 16:36:49 GMT): upmagupta (Mon, 27 Sep 2021 16:37:25 GMT): upmagupta (Mon, 27 Sep 2021 16:37:34 GMT): upmagupta (Mon, 27 Sep 2021 16:37:43 GMT): upmagupta (Mon, 27 Sep 2021 16:37:59 GMT): upmagupta (Mon, 27 Sep 2021 16:38:17 GMT): upmagupta (Mon, 27 Sep 2021 16:38:51 GMT): nguyer (Mon, 27 Sep 2021 16:42:11 GMT): nguyer (Mon, 27 Sep 2021 16:42:57 GMT): upmagupta (Mon, 27 Sep 2021 16:43:25 GMT): upmagupta (Mon, 27 Sep 2021 16:44:21 GMT): nguyer (Mon, 27 Sep 2021 16:45:22 GMT): upmagupta (Mon, 27 Sep 2021 16:46:31 GMT): upmagupta (Mon, 27 Sep 2021 16:46:42 GMT): nguyer (Mon, 27 Sep 2021 16:47:28 GMT): upmagupta (Mon, 27 Sep 2021 16:47:29 GMT): upmagupta (Mon, 27 Sep 2021 16:48:03 GMT): nguyer (Mon, 27 Sep 2021 16:50:29 GMT): upmagupta (Mon, 27 Sep 2021 16:50:41 GMT): upmagupta (Mon, 27 Sep 2021 16:50:50 GMT): upmagupta (Mon, 27 Sep 2021 16:50:53 GMT): upmagupta (Mon, 27 Sep 2021 16:51:05 GMT): nguyer (Mon, 27 Sep 2021 16:51:58 GMT): upmagupta (Mon, 27 Sep 2021 16:52:11 GMT): nguyer (Mon, 27 Sep 2021 16:52:22 GMT): upmagupta (Mon, 27 Sep 2021 16:52:33 GMT): nguyer (Mon, 27 Sep 2021 16:52:33 GMT): nguyer (Mon, 27 Sep 2021 16:53:20 GMT): upmagupta (Mon, 27 Sep 2021 16:53:46 GMT): upmagupta (Mon, 27 Sep 2021 16:53:47 GMT): nguyer (Mon, 27 Sep 2021 16:54:12 GMT): upmagupta (Mon, 27 Sep 2021 16:54:27 GMT): nguyer (Mon, 27 Sep 2021 16:54:44 GMT): upmagupta (Mon, 27 Sep 2021 16:55:01 GMT): nguyer (Mon, 27 Sep 2021 16:55:25 GMT): nguyer (Mon, 27 Sep 2021 16:55:48 GMT): nguyer (Mon, 27 Sep 2021 16:56:27 GMT): nguyer (Mon, 27 Sep 2021 16:57:06 GMT): upmagupta (Mon, 27 Sep 2021 17:11:30 GMT): upmagupta (Mon, 27 Sep 2021 17:11:35 GMT): upmagupta (Mon, 27 Sep 2021 17:11:36 GMT): upmagupta (Mon, 27 Sep 2021 17:11:59 GMT): nguyer (Mon, 27 Sep 2021 17:12:03 GMT): upmagupta (Mon, 27 Sep 2021 17:12:05 GMT): upmagupta (Mon, 27 Sep 2021 17:12:12 GMT): nguyer (Mon, 27 Sep 2021 17:12:19 GMT): upmagupta (Mon, 27 Sep 2021 17:12:25 GMT): nguyer (Mon, 27 Sep 2021 17:12:37 GMT): upmagupta (Mon, 27 Sep 2021 17:14:14 GMT): upmagupta (Mon, 27 Sep 2021 17:14:18 GMT): upmagupta (Mon, 27 Sep 2021 17:14:36 GMT): upmagupta (Mon, 27 Sep 2021 17:15:13 GMT): upmagupta (Mon, 27 Sep 2021 17:15:14 GMT): nguyer (Mon, 27 Sep 2021 17:15:20 GMT): upmagupta (Mon, 27 Sep 2021 17:15:25 GMT): upmagupta (Mon, 27 Sep 2021 17:15:53 GMT): upmagupta (Mon, 27 Sep 2021 17:15:55 GMT): nguyer (Mon, 27 Sep 2021 17:15:59 GMT): nguyer (Mon, 27 Sep 2021 17:15:59 GMT): upmagupta (Mon, 27 Sep 2021 17:16:04 GMT): nguyer (Mon, 27 Sep 2021 17:16:06 GMT): nguyer (Mon, 27 Sep 2021 17:16:10 GMT): upmagupta (Mon, 27 Sep 2021 17:16:16 GMT): upmagupta (Mon, 27 Sep 2021 17:16:21 GMT): nguyer (Mon, 27 Sep 2021 17:16:49 GMT): upmagupta (Mon, 27 Sep 2021 17:17:21 GMT): upmagupta (Mon, 27 Sep 2021 17:17:29 GMT): upmagupta (Mon, 27 Sep 2021 17:17:38 GMT): nguyer (Mon, 27 Sep 2021 17:17:53 GMT): upmagupta (Mon, 27 Sep 2021 17:18:04 GMT): nguyer (Mon, 27 Sep 2021 17:19:06 GMT): janrockdev (Mon, 27 Sep 2021 17:24:28 GMT): upmagupta (Mon, 27 Sep 2021 17:32:31 GMT): upmagupta (Mon, 27 Sep 2021 17:32:34 GMT): upmagupta (Mon, 27 Sep 2021 17:32:44 GMT): upmagupta (Mon, 27 Sep 2021 17:32:54 GMT): upmagupta (Mon, 27 Sep 2021 17:33:01 GMT): upmagupta (Mon, 27 Sep 2021 17:33:03 GMT): upmagupta (Mon, 27 Sep 2021 17:33:35 GMT): upmagupta (Mon, 27 Sep 2021 17:34:08 GMT): upmagupta (Mon, 27 Sep 2021 17:34:10 GMT): upmagupta (Mon, 27 Sep 2021 17:38:00 GMT): nguyer (Mon, 27 Sep 2021 17:39:14 GMT): upmagupta (Mon, 27 Sep 2021 17:39:33 GMT): nguyer (Mon, 27 Sep 2021 17:39:35 GMT): upmagupta (Mon, 27 Sep 2021 17:39:43 GMT): nguyer (Mon, 27 Sep 2021 17:39:45 GMT): upmagupta (Mon, 27 Sep 2021 17:39:50 GMT): nguyer (Mon, 27 Sep 2021 17:40:05 GMT): upmagupta (Mon, 27 Sep 2021 17:47:38 GMT): upmagupta (Mon, 27 Sep 2021 17:49:06 GMT): nguyer (Mon, 27 Sep 2021 17:49:49 GMT): upmagupta (Mon, 27 Sep 2021 17:50:07 GMT): upmagupta (Mon, 27 Sep 2021 17:50:13 GMT): upmagupta (Mon, 27 Sep 2021 17:50:17 GMT): upmagupta (Mon, 27 Sep 2021 17:50:21 GMT): nguyer (Mon, 27 Sep 2021 17:51:08 GMT): upmagupta (Mon, 27 Sep 2021 17:51:10 GMT): upmagupta (Mon, 27 Sep 2021 17:51:15 GMT): upmagupta (Mon, 27 Sep 2021 17:51:15 GMT): nguyer (Mon, 27 Sep 2021 17:51:33 GMT): upmagupta (Mon, 27 Sep 2021 17:51:37 GMT): nguyer (Mon, 27 Sep 2021 17:52:29 GMT): nguyer (Mon, 27 Sep 2021 17:52:39 GMT): nguyer (Mon, 27 Sep 2021 17:52:43 GMT): upmagupta (Mon, 27 Sep 2021 17:52:54 GMT): upmagupta (Mon, 27 Sep 2021 17:53:07 GMT): upmagupta (Mon, 27 Sep 2021 17:59:35 GMT): upmagupta (Mon, 27 Sep 2021 17:59:40 GMT): upmagupta (Mon, 27 Sep 2021 17:59:40 GMT): nguyer (Mon, 27 Sep 2021 18:03:36 GMT): upmagupta (Mon, 27 Sep 2021 18:04:14 GMT): nguyer (Mon, 27 Sep 2021 18:04:52 GMT): nguyer (Mon, 27 Sep 2021 18:05:09 GMT): upmagupta (Mon, 27 Sep 2021 18:05:48 GMT): upmagupta (Mon, 27 Sep 2021 18:05:50 GMT): nguyer (Mon, 27 Sep 2021 18:05:52 GMT): nguyer (Mon, 27 Sep 2021 18:06:00 GMT): nguyer (Mon, 27 Sep 2021 18:06:19 GMT): upmagupta (Mon, 27 Sep 2021 18:06:45 GMT): upmagupta (Mon, 27 Sep 2021 18:06:46 GMT): upmagupta (Mon, 27 Sep 2021 18:09:46 GMT): upmagupta (Mon, 27 Sep 2021 18:09:59 GMT): upmagupta (Mon, 27 Sep 2021 18:16:35 GMT): upmagupta (Mon, 27 Sep 2021 18:16:36 GMT): upmagupta (Mon, 27 Sep 2021 18:17:08 GMT): upmagupta (Mon, 27 Sep 2021 18:17:14 GMT): nguyer (Mon, 27 Sep 2021 18:17:49 GMT): nguyer (Mon, 27 Sep 2021 18:18:16 GMT): upmagupta (Mon, 27 Sep 2021 18:19:08 GMT): nguyer (Mon, 27 Sep 2021 18:19:54 GMT): upmagupta (Mon, 27 Sep 2021 18:20:00 GMT): upmagupta (Mon, 27 Sep 2021 18:20:24 GMT): nguyer (Mon, 27 Sep 2021 18:20:55 GMT): upmagupta (Mon, 27 Sep 2021 18:21:13 GMT): upmagupta (Mon, 27 Sep 2021 18:21:23 GMT): upmagupta (Mon, 27 Sep 2021 18:21:31 GMT): nguyer (Mon, 27 Sep 2021 18:21:50 GMT): nguyer (Mon, 27 Sep 2021 18:22:24 GMT): upmagupta (Mon, 27 Sep 2021 18:22:35 GMT): upmagupta (Mon, 27 Sep 2021 18:23:14 GMT): upmagupta (Mon, 27 Sep 2021 18:23:15 GMT): upmagupta (Mon, 27 Sep 2021 18:23:23 GMT): nguyer (Mon, 27 Sep 2021 18:24:40 GMT): upmagupta (Mon, 27 Sep 2021 18:24:54 GMT): upmagupta (Mon, 27 Sep 2021 19:09:09 GMT): upmagupta (Mon, 27 Sep 2021 19:09:14 GMT): nguyer (Mon, 27 Sep 2021 19:45:28 GMT): nguyer (Mon, 27 Sep 2021 19:45:28 GMT): upmagupta (Mon, 27 Sep 2021 19:45:43 GMT): upmagupta (Mon, 27 Sep 2021 19:45:50 GMT): upmagupta (Mon, 27 Sep 2021 19:45:57 GMT): upmagupta (Mon, 27 Sep 2021 19:46:17 GMT): nguyer (Mon, 27 Sep 2021 19:46:43 GMT): upmagupta (Mon, 27 Sep 2021 19:47:11 GMT): upmagupta (Mon, 27 Sep 2021 19:47:15 GMT): upmagupta (Mon, 27 Sep 2021 19:47:18 GMT): nguyer (Mon, 27 Sep 2021 19:47:56 GMT): upmagupta (Mon, 27 Sep 2021 19:48:10 GMT): upmagupta (Mon, 27 Sep 2021 19:52:56 GMT): upmagupta (Mon, 27 Sep 2021 19:52:56 GMT): upmagupta (Mon, 27 Sep 2021 19:53:05 GMT): upmagupta (Mon, 27 Sep 2021 19:53:14 GMT): upmagupta (Mon, 27 Sep 2021 19:53:15 GMT): nguyer (Tue, 28 Sep 2021 19:32:41 GMT): nguyer (Tue, 28 Sep 2021 19:32:45 GMT): nguyer (Tue, 28 Sep 2021 19:33:41 GMT): scaraclette (Tue, 28 Sep 2021 19:34:27 GMT): nguyer (Tue, 28 Sep 2021 19:34:43 GMT): nguyer (Tue, 28 Sep 2021 19:35:13 GMT): nguyer (Tue, 28 Sep 2021 19:35:20 GMT): nguyer (Tue, 28 Sep 2021 19:35:20 GMT): scaraclette (Tue, 28 Sep 2021 19:36:41 GMT): OscarTBallester (Wed, 29 Sep 2021 11:18:26 GMT): OscarTBallester (Wed, 29 Sep 2021 11:18:43 GMT): OscarTBallester (Wed, 29 Sep 2021 11:21:21 GMT): chakshujain (Wed, 29 Sep 2021 15:48:00 GMT): nguyer (Wed, 29 Sep 2021 16:58:15 GMT): nguyer (Wed, 29 Sep 2021 17:01:51 GMT): nguyer (Wed, 29 Sep 2021 17:38:13 GMT): OscarTBallester (Thu, 30 Sep 2021 11:33:49 GMT): OscarTBallester (Thu, 30 Sep 2021 11:41:18 GMT): nguyer (Thu, 30 Sep 2021 13:29:34 GMT): nguyer (Thu, 30 Sep 2021 13:30:02 GMT): OscarTBallester (Thu, 30 Sep 2021 13:53:46 GMT): nguyer (Thu, 30 Sep 2021 13:55:21 GMT): nguyer (Thu, 30 Sep 2021 13:55:44 GMT): nguyer (Thu, 30 Sep 2021 13:55:44 GMT): OscarTBallester (Thu, 30 Sep 2021 13:57:05 GMT): OscarTBallester (Thu, 30 Sep 2021 14:00:01 GMT): nguyer (Thu, 30 Sep 2021 14:00:42 GMT): nguyer (Thu, 30 Sep 2021 14:01:10 GMT): OscarTBallester (Thu, 30 Sep 2021 14:01:18 GMT): OscarTBallester (Fri, 01 Oct 2021 12:13:39 GMT): Andrew.Richardson (Fri, 01 Oct 2021 14:39:00 GMT): rjones (Fri, 01 Oct 2021 21:22:14 GMT): guri (Sat, 02 Oct 2021 04:11:49 GMT): RakshitaKaulgud (Sat, 02 Oct 2021 18:43:14 GMT): shorsher (Mon, 04 Oct 2021 12:57:23 GMT): shorsher (Mon, 04 Oct 2021 12:57:23 GMT): upmagupta (Tue, 05 Oct 2021 12:23:53 GMT): upmagupta (Tue, 05 Oct 2021 12:24:52 GMT): upmagupta (Tue, 05 Oct 2021 12:36:11 GMT): upmagupta (Tue, 05 Oct 2021 12:36:23 GMT): upmagupta (Tue, 05 Oct 2021 12:36:24 GMT): upmagupta (Tue, 05 Oct 2021 12:36:44 GMT): upmagupta (Tue, 05 Oct 2021 12:36:56 GMT): upmagupta (Tue, 05 Oct 2021 12:39:10 GMT): Andrew.Richardson (Tue, 05 Oct 2021 13:04:46 GMT): upmagupta (Tue, 05 Oct 2021 13:05:16 GMT): Andrew.Richardson (Tue, 05 Oct 2021 13:05:16 GMT): upmagupta (Tue, 05 Oct 2021 13:05:42 GMT): upmagupta (Wed, 06 Oct 2021 12:16:25 GMT): upmagupta (Wed, 06 Oct 2021 12:16:31 GMT): upmagupta (Wed, 06 Oct 2021 12:16:38 GMT): nguyer (Wed, 06 Oct 2021 13:37:51 GMT): nguyer (Wed, 06 Oct 2021 13:38:44 GMT): upmagupta (Wed, 06 Oct 2021 13:38:55 GMT): nguyer (Wed, 06 Oct 2021 13:41:09 GMT): upmagupta (Wed, 06 Oct 2021 13:41:25 GMT): upmagupta (Wed, 06 Oct 2021 13:41:46 GMT): upmagupta (Wed, 06 Oct 2021 13:41:52 GMT): nguyer (Wed, 06 Oct 2021 13:46:50 GMT): upmagupta (Wed, 06 Oct 2021 13:48:19 GMT): upmagupta (Wed, 06 Oct 2021 13:48:47 GMT): nguyer (Wed, 06 Oct 2021 13:49:54 GMT): upmagupta (Wed, 06 Oct 2021 13:51:01 GMT): upmagupta (Wed, 06 Oct 2021 13:52:42 GMT): nguyer (Wed, 06 Oct 2021 13:53:47 GMT): nguyer (Wed, 06 Oct 2021 13:54:03 GMT): upmagupta (Wed, 06 Oct 2021 13:55:57 GMT): upmagupta (Wed, 06 Oct 2021 13:56:10 GMT): upmagupta (Wed, 06 Oct 2021 13:56:13 GMT): upmagupta (Wed, 06 Oct 2021 13:56:22 GMT): nguyer (Wed, 06 Oct 2021 13:58:19 GMT): upmagupta (Wed, 06 Oct 2021 13:58:47 GMT): upmagupta (Wed, 06 Oct 2021 13:59:17 GMT): upmagupta (Wed, 06 Oct 2021 13:59:32 GMT): upmagupta (Wed, 06 Oct 2021 14:00:07 GMT): nguyer (Wed, 06 Oct 2021 14:00:35 GMT): jimthematrix (Mon, 11 Oct 2021 15:09:15 GMT): jimthematrix (Mon, 11 Oct 2021 15:09:15 GMT): mona15 (Tue, 12 Oct 2021 15:38:34 GMT): nguyer (Tue, 12 Oct 2021 15:41:24 GMT): mona15 (Tue, 12 Oct 2021 15:43:05 GMT): nguyer (Tue, 12 Oct 2021 15:44:47 GMT): nguyer (Tue, 12 Oct 2021 18:49:05 GMT): OscarTBallester (Wed, 13 Oct 2021 12:14:51 GMT): nguyer (Wed, 13 Oct 2021 12:20:24 GMT): nguyer (Wed, 13 Oct 2021 12:21:16 GMT): OscarTBallester (Wed, 13 Oct 2021 12:22:05 GMT): OscarTBallester (Wed, 13 Oct 2021 12:22:30 GMT): shorsher (Wed, 13 Oct 2021 23:54:21 GMT): KingAlawaka (Tue, 19 Oct 2021 13:18:13 GMT): rjones (Tue, 19 Oct 2021 14:53:03 GMT): shorsher (Thu, 21 Oct 2021 21:30:34 GMT): KingAlawaka (Fri, 22 Oct 2021 03:23:40 GMT): shorsher (Fri, 22 Oct 2021 13:07:31 GMT): nguyer (Tue, 26 Oct 2021 15:52:09 GMT): Andrew.Richardson (Fri, 29 Oct 2021 14:00:10 GMT): KingAlawaka (Sun, 07 Nov 2021 01:12:34 GMT): nguyer (Mon, 08 Nov 2021 13:33:56 GMT): nguyer (Mon, 08 Nov 2021 13:35:12 GMT): KingAlawaka (Mon, 08 Nov 2021 13:54:50 GMT): KingAlawaka (Mon, 08 Nov 2021 13:56:03 GMT): nguyer (Mon, 08 Nov 2021 14:11:50 GMT): KingAlawaka (Mon, 08 Nov 2021 14:21:23 GMT): nguyer (Mon, 08 Nov 2021 14:22:13 GMT): nguyer (Mon, 08 Nov 2021 14:22:52 GMT): KingAlawaka (Mon, 08 Nov 2021 14:24:16 GMT): nguyer (Mon, 08 Nov 2021 14:24:24 GMT): nguyer (Mon, 08 Nov 2021 14:24:44 GMT): KingAlawaka (Mon, 08 Nov 2021 14:24:54 GMT): nguyer (Mon, 08 Nov 2021 14:27:40 GMT): nguyer (Mon, 08 Nov 2021 14:53:32 GMT): KingAlawaka (Mon, 08 Nov 2021 15:01:43 GMT): KingAlawaka (Mon, 08 Nov 2021 15:01:43 GMT): nguyer (Tue, 09 Nov 2021 20:38:57 GMT): nguyer (Wed, 10 Nov 2021 13:53:42 GMT): Andrew.Richardson (Wed, 17 Nov 2021 14:39:18 GMT): Andrew.Richardson (Wed, 17 Nov 2021 14:40:24 GMT): nguyer (Mon, 22 Nov 2021 20:38:47 GMT): nguyer (Mon, 22 Nov 2021 22:13:48 GMT): KingAlawaka (Wed, 24 Nov 2021 01:29:29 GMT): Kmm 4 (Wed, 24 Nov 2021 13:49:42 GMT): Kmm 4 (Wed, 24 Nov 2021 13:49:43 GMT): nguyer (Wed, 24 Nov 2021 13:50:08 GMT): Kmm 4 (Wed, 24 Nov 2021 13:50:51 GMT): Kmm 4 (Wed, 24 Nov 2021 13:52:44 GMT): nguyer (Wed, 24 Nov 2021 13:55:05 GMT): nguyer (Wed, 24 Nov 2021 13:55:29 GMT): Kmm 4 (Wed, 24 Nov 2021 14:01:10 GMT): nguyer (Wed, 24 Nov 2021 14:02:19 GMT): nguyer (Wed, 24 Nov 2021 14:03:40 GMT): Kmm 4 (Wed, 24 Nov 2021 14:07:27 GMT): Kmm 4 (Wed, 24 Nov 2021 14:12:50 GMT): Kmm 4 (Wed, 24 Nov 2021 14:13:43 GMT): Kmm 4 (Wed, 24 Nov 2021 14:42:25 GMT): Kmm 4 (Wed, 24 Nov 2021 14:43:14 GMT): nguyer (Wed, 24 Nov 2021 14:52:19 GMT): Kmm 4 (Wed, 24 Nov 2021 14:58:13 GMT): nguyer (Wed, 24 Nov 2021 15:03:43 GMT): nguyer (Wed, 24 Nov 2021 15:04:33 GMT): Kmm 4 (Wed, 24 Nov 2021 15:07:32 GMT): nguyer (Wed, 24 Nov 2021 15:31:56 GMT): Kmm 4 (Wed, 24 Nov 2021 15:38:07 GMT): nguyer (Wed, 24 Nov 2021 15:38:36 GMT): Kmm 4 (Wed, 24 Nov 2021 15:40:22 GMT): Kmm 4 (Wed, 24 Nov 2021 15:40:32 GMT): Kmm 4 (Wed, 24 Nov 2021 16:24:07 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:40:36 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:41:36 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:43:26 GMT): Kmm 4 (Wed, 24 Nov 2021 16:44:03 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:53:08 GMT): nguyer (Wed, 24 Nov 2021 16:53:14 GMT): nguyer (Wed, 24 Nov 2021 16:53:24 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:53:25 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:53:48 GMT): Kmm 4 (Wed, 24 Nov 2021 16:53:51 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:54:22 GMT): nguyer (Wed, 24 Nov 2021 16:54:33 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:54:47 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:54:55 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:55:27 GMT): nguyer (Wed, 24 Nov 2021 16:55:28 GMT): Kmm 4 (Wed, 24 Nov 2021 16:56:28 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:56:37 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:56:56 GMT): Kmm 4 (Wed, 24 Nov 2021 16:57:00 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:57:32 GMT): Kmm 4 (Wed, 24 Nov 2021 16:57:58 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:58:32 GMT): Andrew.Richardson (Wed, 24 Nov 2021 16:58:52 GMT): Kmm 4 (Wed, 24 Nov 2021 17:02:43 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:04:10 GMT): Kmm 4 (Wed, 24 Nov 2021 17:05:04 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:05:38 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:06:05 GMT): Kmm 4 (Wed, 24 Nov 2021 17:06:17 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:07:33 GMT): Kmm 4 (Wed, 24 Nov 2021 17:09:52 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:10:16 GMT): nguyer (Wed, 24 Nov 2021 17:10:57 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:11:04 GMT): Kmm 4 (Wed, 24 Nov 2021 17:11:20 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:12:31 GMT): Kmm 4 (Wed, 24 Nov 2021 17:21:56 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:22:57 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:25:21 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:27:19 GMT): Kmm 4 (Wed, 24 Nov 2021 17:29:02 GMT): Andrew.Richardson (Wed, 24 Nov 2021 17:53:19 GMT): Andrew.Richardson (Wed, 24 Nov 2021 18:04:09 GMT): Kmm 4 (Wed, 24 Nov 2021 19:01:13 GMT): Kmm 4 (Wed, 24 Nov 2021 19:01:17 GMT): Andrew.Richardson (Wed, 24 Nov 2021 19:04:12 GMT): Andrew.Richardson (Wed, 24 Nov 2021 19:06:53 GMT): Andrew.Richardson (Wed, 24 Nov 2021 19:07:13 GMT): Kmm 4 (Wed, 24 Nov 2021 19:26:34 GMT): Andrew.Richardson (Wed, 24 Nov 2021 20:11:42 GMT): Kmm 4 (Wed, 24 Nov 2021 20:18:12 GMT): Kmm 4 (Wed, 24 Nov 2021 20:19:58 GMT): Andrew.Richardson (Wed, 24 Nov 2021 20:32:24 GMT): Andrew.Richardson (Wed, 24 Nov 2021 20:32:42 GMT): Andrew.Richardson (Wed, 01 Dec 2021 18:13:03 GMT): nguyer (Tue, 07 Dec 2021 19:38:50 GMT): Andrew.Richardson (Tue, 14 Dec 2021 19:11:09 GMT): SeanBohan (Fri, 17 Dec 2021 20:02:23 GMT): nguyer (Wed, 22 Dec 2021 15:58:02 GMT): nguyer (Mon, 03 Jan 2022 14:23:45 GMT): nguyer (Tue, 04 Jan 2022 16:09:01 GMT): rjones (Tue, 04 Jan 2022 18:16:56 GMT): nguyer (Tue, 04 Jan 2022 18:28:14 GMT): nguyer (Tue, 04 Jan 2022 18:30:25 GMT): rjones (Tue, 04 Jan 2022 19:09:45 GMT): nguyer (Tue, 04 Jan 2022 19:10:18 GMT): rjones (Tue, 04 Jan 2022 19:10:35 GMT): jas191 (Thu, 06 Jan 2022 14:12:53 GMT): jas191 (Thu, 06 Jan 2022 14:12:54 GMT): jas191 (Thu, 06 Jan 2022 14:16:37 GMT): nguyer (Thu, 06 Jan 2022 14:17:41 GMT): nguyer (Thu, 06 Jan 2022 14:18:31 GMT): jas191 (Thu, 06 Jan 2022 14:59:15 GMT): jas191 (Thu, 06 Jan 2022 14:59:40 GMT): nguyer (Thu, 06 Jan 2022 14:59:45 GMT): nguyer (Thu, 06 Jan 2022 15:00:06 GMT): jas191 (Thu, 06 Jan 2022 15:00:13 GMT): jas191 (Thu, 06 Jan 2022 15:00:17 GMT): nguyer (Thu, 06 Jan 2022 15:00:56 GMT): jas191 (Thu, 06 Jan 2022 15:52:53 GMT): nguyer (Thu, 06 Jan 2022 16:16:32 GMT): jas191 (Thu, 06 Jan 2022 16:49:54 GMT): jas191 (Thu, 06 Jan 2022 16:58:53 GMT): jas191 (Thu, 06 Jan 2022 16:59:47 GMT): nguyer (Thu, 06 Jan 2022 17:01:01 GMT): jas191 (Thu, 06 Jan 2022 17:03:56 GMT): jas191 (Thu, 06 Jan 2022 17:04:00 GMT): nguyer (Thu, 06 Jan 2022 17:04:10 GMT): nguyer (Mon, 10 Jan 2022 19:28:43 GMT): Gavimat (Wed, 12 Jan 2022 20:07:48 GMT): newbusybee (Tue, 18 Jan 2022 01:03:01 GMT): nguyer (Wed, 19 Jan 2022 13:07:14 GMT): jas191 (Wed, 19 Jan 2022 15:58:47 GMT): nguyer (Thu, 20 Jan 2022 16:26:53 GMT): sbohanlf (Tue, 25 Jan 2022 15:20:38 GMT): nguyer (Tue, 25 Jan 2022 15:34:53 GMT): sbohanlf (Wed, 26 Jan 2022 18:35:16 GMT): nandrews283 (Sun, 30 Jan 2022 02:05:30 GMT): nandrews283 (Sun, 30 Jan 2022 02:05:31 GMT): Andrew.Richardson (Mon, 31 Jan 2022 14:27:23 GMT): Andrew.Richardson (Mon, 31 Jan 2022 14:41:23 GMT): Andrew.Richardson (Tue, 01 Feb 2022 22:04:45 GMT): Andrew.Richardson (Tue, 01 Feb 2022 22:04:45 GMT): nandrews283 (Wed, 02 Feb 2022 00:17:12 GMT): nandrews283 (Wed, 02 Feb 2022 00:17:39 GMT): Andrew.Richardson (Wed, 02 Feb 2022 18:53:46 GMT): Andrew.Richardson (Wed, 02 Feb 2022 23:37:05 GMT): jas191 (Fri, 04 Feb 2022 04:33:43 GMT): jas191 (Fri, 04 Feb 2022 05:05:29 GMT): jas191 (Fri, 04 Feb 2022 10:10:00 GMT): Andrew.Richardson (Fri, 04 Feb 2022 17:08:22 GMT): Andrew.Richardson (Fri, 04 Feb 2022 17:10:07 GMT): Andrew.Richardson (Fri, 04 Feb 2022 17:20:50 GMT): jas191 (Fri, 04 Feb 2022 18:17:41 GMT): sukrutsathaye (Thu, 10 Feb 2022 08:55:56 GMT): jas191 (Thu, 10 Feb 2022 09:41:44 GMT): jas191 (Thu, 10 Feb 2022 09:42:11 GMT): jas191 (Thu, 10 Feb 2022 09:47:09 GMT): jas191 (Thu, 10 Feb 2022 09:47:17 GMT): jas191 (Thu, 10 Feb 2022 09:47:33 GMT): jas191 (Thu, 10 Feb 2022 10:53:48 GMT): Andrew.Richardson (Thu, 10 Feb 2022 16:07:12 GMT): Andrew.Richardson (Thu, 10 Feb 2022 16:08:03 GMT): Andrew.Richardson (Thu, 10 Feb 2022 16:29:16 GMT): sukrutsathaye (Thu, 10 Feb 2022 16:29:45 GMT): rjones (Fri, 11 Feb 2022 22:01:39 GMT): rjones (Sun, 13 Feb 2022 01:34:33 GMT): F.Florian (Wed, 16 Feb 2022 13:03:20 GMT): dangeross (Fri, 11 Mar 2022 08:55:47 GMT): rjones (Wed, 23 Mar 2022 17:25:18 GMT): rjones (Wed, 23 Mar 2022 17:25:18 GMT): rjones (Wed, 23 Mar 2022 17:25:18 GMT):
Ah okay, I forgot about the part where the config file was generated after doing `ff start
The config file should be generated with `ff init`
But the CLI will tell you the command to run as part of `ff start`
So I should run ff init within the terminal for the repo right? I did it outside of my vscode terminal
You can run `ff init/start` in any working directory
Awesome, it works! Going to update the steps I wrote
Great!
Hi all, please, any comments on https://github.com/softwaremill/fablo ? They are presenting themselves with Hyperledger too and it looks similar to Firefly! Grrrrr...lets hack them! :woo:
I hadn't seen Fablo before. I just took a quick look at it. It looks like a tool to help speed up fabric network creation. That's very different than what FireFly has been designed to do. I'm assuming your call to "hack them" is a joke (which is hard to convey over chat), but let's try to keep the conversation positive. Even if they are trying to do the same thing, there is room in the world for more than one open source project. And more projects mean more opportunities for collaboration.
Has joined the channel.
Hi Team
I am trying to setup firefly to interact with my fabric network
somehow i managed to run fabconnect
but not sure how to take it forward
how do I inititate a transaction
or how to connect fabconnect to my my fabric network which is running
Is there any video available which tells setup by step how to integrate firefly with fabirc?
Hi @upmagupta! :wave:
Fabric support has not quite been merged into the main branch yet but it should be fairly soon
thanks nguyer for your response
actually I am doing a POC on it is it possible that with the existing code we have we can integrate fabric and try basic transactions?
I'll start a thread for this one... So it sounds like you already have a POC on FireFly? And you'd like to switch FireFly to use Fabric now?
yaa i did my POC on ethereum but my company wants to explore fabric too as we are trying to build a solution using fabric
so I was trying to do a POC on the same
I see. It _is_ possible to try it today on your own machine, but you'll need to checkout some specific feature branches and build the docker images for those locally.
if i can try what all will be possible with firefly when it comes to fabric then i will be able to look for options if we can use the same for our use case
yaa i can do all of what is required but the problem is i dont know how to do it
Okay. I can try to walk you through it
so do we have anything which i can use to setup and integrate my firefly with fabric
that will be awesome
thanks a lot
so how do we do it ?
Do you already have the FireFly CLI set up, and have you been able to create an environment yet?
yes i have firefly setup
Great.
and my fabric network indiviadually is also running . i have setup fabconnect also but not sure if i have done coreectly
Clone this fork/branch: https://github.com/kaleido-io/firefly/tree/fabric-plugin
In that directory run `docker build -t ghcr.io/hyperledger/firefly .`
okay this is the first step to start from
?
Yes
okay sure ihave set it up in my ec2 machine
(note, you must be on the `fabric-plugin` branch when you run `docker build`
okay
So that will give you a version of FireFly that has a plugin to work with fabric. The next thing you need is the version of the CLI that can set up the fabric network. To do that, checkout the `fabric` branch of the CLI: https://github.com/hyperledger/firefly-cli/tree/fabric
From that directory run `make install` to build and install that version of the CLI
Then you should be able to run `ff init --blockchain-provider fabric` to create the config for the new FireFly stack
Finally, start up the stack with `ff start
hi nguyer
i just got an error stating
Error: geth is currently the only supported blockchain provider - support for other providers is coming soon
Usage:
after i ran f init --blockchain-provider fabric
That means you're not running the correct build of the CLI
ff init command
ohh
Did you build and install from source on the `fabric` branch of the CLI?
i am inside the ff cli folder
What branch are you on?
home/ec2-user/go/bin/firefly-cli
this is the path
and inside firefly-cli i ran make build and then ff init
my firefly cli has all these folsers
HANGELOG.md cmd CODE_OF_CONDUCT.md CODEOWNERS CONTRIBUTING.md docs ff go.mod go.sum internal LICENSE MAINTAINERS.md Makefile pkg README.md SECURITY.md
Can you please run `git status` in that directory and check what branch you are on?
HANGELOG.md cmd CODE_OF_CONDUCT.md CODEOWNERS CONTRIBUTING.md docs ff go.mod go.sum internal LICENSE MAINTAINERS.md Makefile pkg README.md SECURITY.md
n branch main
Your branch is up to date with 'origin/main'.
main branch
That's hwy
That's why
ohh okay
You need to be on the `fabric` branch
`git checkout fabric`
which branch i need to be on
okay
Please also make sure that you were on the `fabric-plugin` branch when you built the docker image for firefly (the first step I listed above)
ohh
i didnt take care of the branch thing
i just repeat the above steps
Yes, that's why I pointed out at the beginning that none of this has been merged into the main branch yet
ohh sorry i missed that
It's okay
100% agree, challenge to be better! ;)
hi nguyer
it worked thanks
now i have firefly for ethereum running on 3000 ports
and this will be fabric
and 5000 is already accupied
occupied
so i should be running
ff ff init --blockchain-provider fabric 4000 -s 4100
?
ff init --blockchain-provider fabric -p 4000 -s 4100
You can't currently run more than one FireFly stack on your local machine at the same time
ohh so i need to delete the ethereum one first ?
You should run `ff stop
ohh okay thanks
You don't have to remove it completely. You just need to stop it
okay thanks
Besides port conflicts, it's a lot of system resources to run that many containers
Error: an error occurred - rolling back changes... Error: docker-compose up -d
Failed [1] Creating network "firefly_fabric_default" with the default driver
Error: docker-compose up -d
Failed [1] Creating network "firefly_fabric_default" with the default driver
Creating volume "firefly_fabric_fabconnect_events_0" with default driver
Creating volume "firefly_fabric_fabconnect_events_1" with default driver
Creating volume "firefly_fabric_fabconnect_receipts_0" with default driver
Creating volume "firefly_fabric_fabconnect_receipts_1" with default driver
Creating volume "firefly_fabric_fabric_ca" with default driver
Creating volume "firefly_fabric_fabric_orderer" with default driver
Creating volume "firefly_fabric_fabric_peer" with default driver
Creating volume "firefly_fabric_ipfs_data_0" with default driver
Creating volume "firefly_fabric_ipfs_data_1" with default driver
Creating volume "firefly_fabric_ipfs_staging_0" with default driver
Creating volume "firefly_fabric_ipfs_staging_1" with default driver
Pulling fabconnect_1 (ghcr.io/hyperledger-labs/firefly-fabconnect:latest)...
Head "https://ghcr.io/v2/hyperledger-labs/firefly-fabconnect/manifests/latest": denied
- all changes rolled back
That's strange. I haven't seen that particular error before. Are docker and docker compose set up on your system?
yes
my fabric nrtwork is running
independently
on the same ec2 machine
That may or may not be a problem, but with the FireFly CLI, the expectation is that the CLI will set up everything, including the blockchain network
not sure
is it a permission error
Head "https://ghcr.io/v2/hyperledger-labs/firefly-fabconnect/manifests/latest": denied
- all changes rolled back
Oh... sorry I forgot a step...
okay
So you'll need to pull https://github.com/hyperledger/firefly-fabconnect and run `docker build -t ghcr.io/hyperledger/firefly-fabconnect .` in that directory
This one should use the `main` branch so you don't need to switch branches
Sorry I forgot that step
no issues
no changes to make right
hi
again getting the same error
ulling fabconnect_1 (ghcr.io/hyperledger-labs/firefly-fabconnect:latest)...
Head "https://ghcr.io/v2/hyperledger-labs/firefly-fabconnect/manifests/latest": denied
- all changes rolled back
Usage:
ff start
Ah okay. Many of these repos moved in the last couple of days so some of these branches may need to be updated. I think you can work around this issue by running `docker build -t ghcr.io/hyperledger-labs/firefly-fabconnect .` in the fabconnect directory
you mean switch to fabconnect branch n then run docker build ?
No branch switching should be neccesary
But in the firefly-fabconnect directory, you need to tag the docker build with a different name
ohh git it used labs
okay
Right
FireFly moved out of Labs last Thursday :)
All of the main branches have been updated but some of these feature branches are still in progress
sure thanks a lot helping me like this
:)
one more thing i dont have create my network and then connect fabconnect to it
it will bring up the fabric network too right ?
also i am getting the error
Failed [1] Error: No such container:path: firefly_fabric_firefly_core_0_1:/firefly/contracts/firefly_fabric.tar.gz
i have firefly_fabric.tar.gz in my cli
should i copy that there ?
I suspect that means you aren't running the correct branch of `firefly` which has the fabric chaincode in it
What branch are you on in the `firefly` repo when you built that docker image?
fabric-plugin
Hmm okay. If that's true I'm not sure what else would cause that
oh
should i paste tar file under my contract n try ?
You can certainly try. I'm not sure what tar file you actually have there or where it would have come from
its lokking for firefly_fabric.tar.gz
which is not there in my contract folder
but its under my cli folder
Right. The CLI is trying to extract a packaged chaincode from the FireFly docker container
And it can't find it. Which usually means the image that is running is not the correct version
ohh
so should i remove the firefly folder n create it again n build image in pkugin repo
?
plugin*
Possibly. If you want to try it again, you can run `ff remove
ok thanks let me try that
whats the difference between firefly folder
and .firefly folder?
`~.firefly` is a directory where the FireFly CLI stores data. I'm guessing the other directory is probably where you cloned the `firefly` repo with git
`~/.firefly` is a directory where the FireFly CLI stores data. I'm guessing the other directory is probably where you cloned the `firefly` repo with git
yes
i am still getting the same error
after doing all the steps again
but i am trying to cpoty the tar file in contract folder from cli and will try that
Okay. Sorry I can't help anymore at this point. My dev machine is in the middle of working on another branch right now. The change I'm working on is a prerequisite to be able to merge the fabric branches
sure no problem i will try to resolve this error
and check with you thanks
later
Sounds good. As soon as I get these changes done, I'll be working on incorporating them to the fabric branches, so if there's something not working there today, I'll have it working very soon
great
this path only has some issues
Error: docker cp firefly_fabric2_firefly_core_0_1:/firefly/contracts/firefly_fabric.tar.gz /home/ec2-user/.firefly/stacks/firefly_fabric2/contracts/firefly_fabric.tar.gz
anyways will try again tomorrow
thanks for all the help
:)
HL_FireflyRelease.png
Hello everyone! That's right, it's official! FireFly has moved out of Labs and is now an official Hyperledger Project.
This will mean a few logistical things will change with mailing lists and stuff like that. We'll talk through some details on tomorrow's call. Here are the details for tomorrow's call:
Wednesday, September 29, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- What's changing now that FireFly is an official project?
- Open discussion
- Architecture: update on Identity in FireFly
As always, thank you all for your participation in these calls! We hope to see you there!
Also, if you haven't seen it, here's the official blog post with the announcement. Please feel free to share! https://www.hyperledger.org/blog/2021/09/28/introducing-hyperledger-firefly-a-multi-party-system-for-enterprise-data-flows
Will the session be recorded?
Yes it will! All the calls are public and recorded
The recordings are posted to the wiki afterward. Although the link to this page will be moving as a part of the transition out of Labs
I'll like the new page after it moves
I'll link the new page after it moves
Awesome, thanks!
Hi Nicko,
I have the MVP almost ready, but I need some more help to add a node. I was trying to create another stack, modify some data from .firefly/stacks/project/configs/firefly_core_0.yml and then start the stack for the first time but I´m giving a timeout error. What I have are two computers, the main one with the Firefly ports open and the other one with the stack config modified. Can you confirm for me if the URL selected is the good one? Do you have any examples? Thanks again!
2021-09-29_06h05_51.png
I mean, if the URL selected is the one I need to change.
I'm looking for this element in the Docker Dashboard and redirecting the node from the second computer to the real port in my main computer.
Has joined the channel.
Hi @chakshujain :wave: welcome!
Hi Oscar, that config file was generated for running FireFly inside a docker compose network that has all of the other microservices that FireFly depends on also running inside the same docker compose network. If you want to run FireFly on separate machines, outside of docker compose, it's definitely possible, but you will need to configure each application to know about the real IP address/port that it should be connecting to. It is possible, but there would be a lot of things to change.
Today's community call recording and slides are up here: https://wiki.hyperledger.org/display/FIR/2021-09-29+FireFly+Community+Call
So, this config file has the right structure to deploy on production? Do you have any documentation about production deploy process? Where should be the config file on prod? Thanks again.
What tokens and dataexchanges URLs mean?
The config files generated by the CLI are not intended to be deployed to production as-is. They're designed for setting up a minimum viable local development environment
Those are the URLs for the token connector and the data exchange - two of the microservices used by FireFly
Ok, so where I can set those URLs in production environment?
They are set in the FireFLy core config yaml file (just like the one you posted the screenshot of, above)
The URL should point to the IP/port of wherever you are running those services
The URLs should point to the IP/port of wherever you are running those services
Thanks
So, there is a command to run the firefly node or just like a regular GO project?
In the firefly project directory, you can run `make install`. Then you just need to run `firefly` to run it as a normal process on your machine
If you run `firefly --help` it will print out the other command line flags that you can pass to it, such as the path to the config file
Ok, thank you
Hi Nicko, it was really helpful your guidance. I'm getting this error now "FF10105: Failed to initialize TLS configuration: crypto/x509: system root pool is not available on Windows", any ideas?
For anyone that doesn't follow every single FF issue, wanted to point out that we do have an overall tracking issue for tokens now: https://github.com/hyperledger/firefly/issues/218
Hopefully this gives better visibility on where it's at and a place to jump in as the conversation evolves. Basic mint/burn/transfer are nearly ready for use!
If you go here: https://insights.lfx.linuxfoundation.org/projects/hyperledger-f/dashboard;quicktime=time_filter_3Y and click on "subprojects", you'll see firefly is there, with logo
Has joined the channel.
Has joined the channel.
Welcome @guri @RakshitaKaulgud :wave:!
Welcome @guri @RakshitaKaulgud :wave:
hi @nguyer
have you merged the code to main branch ?
hi team
i am getting error while starting my firefly for fabric
ocker cp abf_fabric_firefly_firefly_core_0_1:/firefly/contracts/firefly_fabric.tar.gz /home/ec2-user/.firefly/stacks/abf_fabric_firefly/contracts/firefly_fabric.tar.gz
is firefly_fabric.tar.gz contract tar file to be deployed?
is it the chaincode?
can we put oue own custom chaincode here and oput it
@upmagupta I haven't run with Fabric, but I believe that file should be present in the FireFly Docker image (it's a provided chaincode file for FireFly, and you do not need to provide your own)
but the volume is not created
AFAIK all the Fabric work is still on branches, so you likely need to build your own FireFly Docker from the appropriate Fabric branch (I don't know if there is one published). @nguyer would know more.
okay thanks Andrew will wait for nguyer
hi @nguyer good morning
we need your help
are you there ?
Hi @upmagupta. Andrew is correct. Fabric feature branches have not been merged yet. There is another large pull request that changes how identities are handled that needs to be merged first. Then the fabric feature branches need to be updated with these changes merged back into them.
Hey, sorry just got back from travelling, so catching back up on messages. Are you using WSL on Windows?
actually we are working on a POC related to firefly integration with fabric if the code is somehow complete is it possible to get it to demoable stage ?
Yes, we're working on getting the branches merged
actually we dont have much time to close on our demo
so can you guide me now on how to take it to demo stage
?
I don't think it's possible to run FireFly with Fabric at this exact moment because of all the changes we are in the middle of right now.
ohh okay any timeline you have ?
also did you guys remove the support for fabconnect and introduced smart-client ?
As soon as possible :) We are working getting both fabric and tokens branches updated with the identity changes. Fabconnect is still the way to use Fabric with FireFly.
any tentative time like in few weeks or months ?
also why do we have fabric-smart-client with a link not pointing to the reop and also the fabcoonect links are removed
I would expect days, rather than weeks or months.
Where are you seeing those links?
CLI / Developer experience - https://github.com/hyperledger/firefly-cli
UI Explorer - https://github.com/hyperledger/firefly-ui
Sample applications - https://github.com/hyperledger/firefly-samples
Core (this repo) - https://github.com/hyperledger/firefly
HTTP Data Exchange - https://github.com/hyperledger/firefly-dataexchange-https
Ethereum (Hyperledger Besu / Quorum) connector: https://github.com/hyperledger/firefly-ethconnect
Corda connector: https://github.com/hyperledger/firefly-cordaconnect - contributed from Kaleido generation 1 - porting to generation 2
Hyperledger Fabric connector - in design phase, including collaboration with https://github.com/hyperledger/fabric-smart-client
this if from hyperledger main repo
readme
Hyperledger Fabric connector - in design phase, including collaboration with https://github.com/hyperledger/fabric-smart-client
Ah I think that line in the readme is very old. Probably written before fabconnect existed. We will get that updated
ok thanks
but initially in labs repo it was actually fabconnect
but guess an updation required
no issues we will wait for your fabric support :)
git blame says it was written 4 months ago: https://github.com/hyperledger/firefly/pull/41/files
hey Fabric fans, given the amount of questions we've got around the progress of the Fabric support in FireFly, I just added a project board in the `firefly-fabconnect` repo that reflects what's been done, what's in progress and what are still on the docket. This should give you a sense of the planned scope for the first release we are working towards (let's call it `0.1`).
here are the ways you can contribute:
- feedback on what you'd like to have that's not on the list
- feedback on re-prioritizing the existing items
- even better, feel free to pick items off the TODO list, assign to yourself and move them to In Progress! we'd love to work with you and help you contribute. a number of them have been marked as "Good First Issue"
in the meanwhile, the PR for the Fabric plugin inside FireFly core is under review: https://github.com/hyperledger/firefly/pull/184. @nguyer has already added support for Fabric in the CLI repo, and is helping with adding the Fabric flow to the FireFly's end-to-end test
hey Fabric fans, given the amount of questions we've got around the progress of the Fabric support in FireFly, I just added a project board in the `firefly-fabconnect` repo that reflects what's been done, what's in progress and what are still on the docket. This should give you a sense of the planned scope for the first release we are working towards (let's call it `0.1`).
https://github.com/hyperledger/firefly-fabconnect/projects/1
here are the ways you can contribute:
- feedback on what you'd like to have that's not on the list
- feedback on re-prioritizing the existing items
- even better, feel free to pick items off the TODO list, assign to yourself and move them to In Progress! we'd love to work with you and help you contribute. a number of them have been marked as "Good First Issue"
in the meanwhile, the PR for the Fabric plugin inside FireFly core is under review: https://github.com/hyperledger/firefly/pull/184. @nguyer has already added support for Fabric in the CLI repo, and is helping with adding the Fabric flow to the FireFly's end-to-end test
Hi All, does anyone have an example payload for a create data type request?
@mona15 Actaully we do have a docs page on this :) Have you seen this page? https://hyperledger.github.io/firefly/gettingstarted/define_datatype.html
Ah I hadn't seen this. I was just going off the api specs, thanks nicko!
Sure thing!
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/FIR/2021-10-13+FireFly+Community+Call
Wednesday, October 13, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Preview of new FireFly UI designs
- Quick status update on major features in progress
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
Hi there, I have an upcoming project that stopped the MVP for a while but I will be trying to deploy the system again. So, it is a bit confusing to me but I will need to wake up an external Data Exchange, isn't it? is that all? I mean for a minimum system.
We should maybe start a new thread for this one :) it took me a minute to find this one all the way back up here. Can you elaborate on what type of deployment you're trying to do? How many members, etc? I'm assuming this is not a development environment anymore, and is a production or pre-production environment?
If you're using Kubernetes there is a helm chart in the FireFly repo now that may also be helpful to you: https://github.com/hyperledger/firefly/tree/main/deploy/charts/firefly
Yes, is a pre production environment. We want to check how easy is the onboarding process.
Thanks for the link, I'll check it
We have started posting issues for enhancements to FireFly Explorer, the first being the new module to support tokens. If you're interested in contributing in any way, please see https://github.com/hyperledger/firefly-ui/issues/65
Hi all... I did a small experiment with jmeter to post requests through firefly API. I'm using multiple threads and do multiple post requests... In my explorer, it says 455 messages but 13 transactions... I thought every message is a transaction... Is there any batch processing or any aggregation happening behind the scene?
Merged: https://hyperledger.github.io/hyperledger-hip/HIPs/firefly.html
There is batch processing going on, briefly mentioned here: https://hyperledger.github.io/firefly/architecture/multiparty_event_sequencing.html#transaction-submission. @nguyer, did we have a community call on batching? Or help me find the right place in the docs :)
Hi @shorsher.... Thanks a lot for the information... I will check this... this really helps me... thanks again... :D
No problem :)
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/FIR/2021-10-27+FireFly+Community+Call
Wednesday, October 27, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Demo of network map and tokens UI
- Discussion about repo versioning, builds, and releases
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
First draft of the documentation for tokens is up in PR: https://github.com/hyperledger/firefly/pull/306
Some of the routes are still being shuffled around, but anyone interested can follow along here and give feedback.
firefly.mp4
Good question. This looks like a limitation of the UI, probably based on the API request that it's making to get the count. I think there's an upper bound on the type of request it's currently doing, so it probably gets capped at 10,000 (9,993 is suspiciously close to 10,000).
@shorsher is this something you could take a look at if you have a chance?
Also, @KingAlawaka I would love to know more about your test configuration and what you're looking to prove. Thanks for pointing this out too!
Hi @nguyer...
Thanks for the reply. I am planning to use firefly in my research to support multi-party communication. Since there is a fabric and Ethereum as options for a distributed ledger, I am trying to stress the stack and see what is the best ledger to use in my research.
The test is simple API broadcast messages for all participants ( 3 member stack). I am increasing the number of API calls and analyzing error rate, throughput, time is taken to complete, etc. I am using JMeter to automate these API calls and get the performance indexes. Currently, I am facing another strange behavior. Even after JMeter finishes its test cases, firefly nodes are heavily working. When I check the docker container performance firefly_core_0 is continuously running with high CPU usage. Since Jmeter finishes its test cases I believe firefly nodes should not continue to run like this. I send all the requests from one node (port 5000) so that the firefly node is still heavily using the resources in the containers.
I am sorry if I didn't make any sense with my experiment or my explanation. I am very new to the field, and I like to explore. Please let me know your thoughts on my experiment or anything related to the firefly node performance after completing the tests.
Annotation 2021-11-08 134708.jpg
Very interesting. I wouldn't expect to see much CPU usage after the test has finished either so that is concerning. Would you mind sharing your JMeter configuration at some point when it's ready? I'd be interested in reproducing this behavior to investigate it as well
Sure I'll share my JMeter configuration. However I cant upload it here.. zip files or .jmx files are not supported... how can I share it?
is .tar.gz supported?
or maybe just change the .zip file extension to something else?
https://drive.google.com/file/d/12e71De_ME_4GI6OrUpigb-z4v9_9YW8J/view?usp=sharing
That works :)
Thank you!
Thanks, @nguyer... I really appreciate your time...
Sure! For transparency, the maintainers (including myself) are currently heads down trying to finish the last few major features for v1.0. But "production readiness", including this type of testing is the next major priority in getting ready for v1.0, so there will a lot of attention on it here soon.
If it's something you're interested in for research, we would love to include you in the discussions about this testing when we have those soon
I am not an expert but I am more than happy to get involved. Please let me know about future discussions... ```
On a side note, I think my virtual machine configuration is also helpful...
```
I am not an expert but I am more than happy to get involved. Please let me know about future discussions...
On a side note, I think my virtual machine configuration is also helpful...
Intel® Xeon(R) CPU @ 2.20GHz × 2 , 8GB ram, Ubuntu 18.04LTS
Hello everyone!
Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/FIR/2021-11-10+FireFly+Community+Call
Wednesday, November 10, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Update and proposed design for Custom On-Chain Logic
- FireFly Improvement Request process
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
Also, a late addition to today's agenda, but we will also get to see a demo of a recently merged contribution that adds Hyperledger Besu support to the FireFly CLI!
Wanted to circle back on this and note that performance testing is officially underway now: https://github.com/hyperledger/firefly/issues/316
@shorsher it would be good to know if any of your early results also align with what's reported above.
Hi all! FireFly v0.11.0 has been released! :tada: For more details, please see the release page (https://github.com/hyperledger/firefly/releases/tag/v0.11.0 ), or the note on the FireFly mailing list. Thanks to everyone who contributed to this release!
With the Thanksgiving holiday this week in the US, the community call will likely be lightly attended, so we will skip this week. See you all in 2 weeks, and hope everyone has a great week!
great... I will have a look :D
Has joined the channel.
Hi all !
Hi @Kmm 4 :wave: welcome!
Thank you :) I'm quite new with Firefly, but it look great !
I have setup my dev environment with fabric blockchain, and played a bit with the APIs.. I was wondering where i can find some additionnal tutorials, specificly on how to handle security for the users ?
Great! There are some tutorials here: https://hyperledger.github.io/firefly/gettingstarted/gettingstarted.html as well as a couple very small sample apps here: https://github.com/hyperledger/firefly-samples Though more robust samples are definitely something we need.
For your question about security, are you wondering how to secure the FireFly API itself?
Yes I've already test the firefly-sample and was stuck a bit as the token part is still empty in the docs.. Yes exactly, for now i can access the api on http access without tls nor identification nor api keys..
Right. There is actually a very user-friendly walkthrough of the new tokens APIs that will be merged very shortly in this PR: https://github.com/hyperledger/firefly/pull/306
In terms of securing the API, normally in a production environment there would be some other service or load balancer in front of FireFly such as nginx or HAProxy which would authenticate requests
Ok thx looking forward to it !
So for security, my main app need to handle users connection, then securely connect to a node as a admin member, then send the command to the blockchain to write something on the behalf of the user who did the request ?
or do i need to create a member for each users ?
and one last question, is the concept of namespaces in firefly the same as channels in fabric ?
sorry for such beginnners questions :sweat_smile:
No that's a great question! They are not actually the same and have some different use cases. Namespaces are a way to group definitions, data, messages, etc related to a specific app. It provides a way to look at a related subsection of the database/blockchain. However, namespaces in FireFly are not currently an access control. Use cases for different namespaces might be: 1) Running test transactions on a separate namespace to not pollute the default namespace 2) Running multiple apps on a single FireFly network
Ok thank you. So if i need the concept of channels in Firefly, I need to forget about fabric and use instead a logic of datas&Events ? Originaly i was thinking creating a dedicated channel for each projects of a user. I can still a different namespaces, or it is advise to not use too many namespaces ?
API support for using many Fabric channels in FireFly is coming, but it's not ready yet
I think it will be possible to use multiple Fabric channels within one FireFly namespace
Ok great looking forward to it ! If there is subproject about this, i'll be happy to try to help :)
Thanks! Will definitely include you when that work kicks off. There will be some core FireFly architecture work required as part of this as well.
Yes I'm still quite new (less than 24 hours) but diving a bit in.. It seems through the fabconnector i can get more control about what's happening specificaly in the fabric network.. its seems to use by default a "default-channel"
Yes, using Fabconnect's API you can use whatever channel you wish
Yes it seems to be the correct way to use the MSPs to solve my security problem..but still not sure if i should focus on wallet on firefly instead ?
*also
I did check to new doc, but was a bit struggling with the notion of plugin connector, where are they defined ? thx
"connectors" in FireFly are external microservices that perform a particular task (we have connectors for blockchain, data exchange, tokens, etc). They run separately, and your FireFly YAML config will point to the addresses of your various connectors.
If you use the CLI to start an Ethereum stack, by default it will include an instance of the firefly-tokens-erc1155 connector for each node - your generated docker-compose file will contain entries to spin up these services, and your generated FireFly config will point to them
Now in the case of Fabric, currently the CLI does not have support to generate any type of tokens. You definitely could do a mixed network where your messaging is backed by Fabric, but you use the firefly-tokens-erc1155 connector and issue tokens with Ethereum. This is completely supported by FireFly, but the CLI doesn't (yet) have support to automatically generate the config for this type of combination.
ok thx, I used the cli to start a Fabric stack, and tried to use the API to create a token pool and got this message : {"error":"FF10272: Unknown tokens plugin 'tokens-erc1155'"}
yea, you would need to configure a tokens plugin by adding an entry like this to the end of your firefly config.yaml (found under the ~/.firefly folder for your stack):
```
tokens:
- plugin: fftokens
name: erc1155
url: http://tokens_0:3000
```
I think the correct API path is `erc1155`
rather than `tokens-erc1155`
but then you would also need a tokens microservice running on that port
@nguyer the name corresponds to whatever your config entry specifies
great ! I will test it asap :)
@Kmm 4 adding the config will make FireFly accept the request, but actually bringing up a working tokens microservice to process the request is more involved
Yep, @Andrew.Richardson is correct. I think the default that the FireFly CLI creates is just called `erc1155` though.
you have to bring up tokens, and tokens depends on ethconnect, and ethconnect depends on geth
and they all have to be configured to talk to each other
this is why it's nice that the CLI does it automatically on Ethereum. I could try to give pointers on doing it manually, but it's rather involved.
It's also worth pointing out that the FireFly CLI does not have an "out-of-the-box" configuration which supports both Fabric/Fabconnect as the blockchain, but some other ethereum based token connector.
ok i understand.. the correct way to achieve this is to work on firefly cli to make it more fabric friendly.. :)
yes :)
if you did want to play with tokens, currently the easiest way to do that is by starting an Ethereum stack
is there any work started yet on this topic ?
No, but I opened https://github.com/hyperledger/firefly-cli/issues/120 a little while back
actually i designed my system on Fabric and was looking for a reliable way to put this in production..that's why i checked the FireFly project
@Kmm 4 are you using tokens (or planning to use tokens)?
Curious if you'd want to find some implementation of tokens on Fabric, or would want the combo of Fabric with Ethereum tokens as we're discussing here.
I'm currently working on a crowdfunding plateform and need to emit/manage some tokens (noNFT & NFT) for each project. So I'm using the blockchain just as distributed database where to store these tokens. I choose a while ago to follow and get familiar with Fabric instead on Ethereum just to avoid gaz fees..
Got it. For what it's worth, if you're hosting your own network (ie not on mainnet), you can choose to eliminate gas fees. You'd need to decide how the network would be built out though.
so my preference is to find/make an implementationn of tokens on Fabric...
Yea, definitely another route here is to create a brand new tokens connector that is backed by tokens on Fabric
I'm not aware of a well-adopted standard for Fabric tokens, so it hasn't been on our immediate radar.
Yes you can i guess eliminate gas fees but you will somehow need to struggle with them when hosting your solution no ?
:) yea, hosting is a whole other set of problems
I found some elegant solutions for fabric on aws, the have a private cloud almost ready to use
if you're at all interested in exploring what a Fabric tokens connector would look like, it would likely mean copying https://github.com/hyperledger/firefly-tokens-erc1155 and changing the backend to point at some fabric thing instead of Ethereum
It would also need a token chaincode as well
correct
Yes I was currently checking it
There are only a few APIs required for a token connector, so it's a matter of figuring out how those map to something like FabToken
ok I should look in the solidity folder for changing backend pointer ?
Token docs were actually just merged, so they are live here: https://hyperledger.github.io/firefly/gettingstarted/mint_tokens.html
Yes, there are two components to the connector implementation. The actual smart contract is in that Solidity folder:
https://github.com/hyperledger/firefly-tokens-erc1155/blob/main/solidity/contracts/ERC1155MixedFungible.sol
And the mapping code which maps HTTP requests to those smart contract methods is in the token service:
https://github.com/hyperledger/firefly-tokens-erc1155/blob/main/src/tokens/tokens.service.ts
For the Solidity portion, we used the reference ERC1155 contract from OpenZeppelin and extended it with mint and burn methods. Would need to decide a similar standard on Fabric and determine if it also needs any extensions.
thank you that's a great help ! I will to replic a mint and burn for fabric
sounds great - keep us posted on what you find and I'm happy to help figure out the implementation details. it would definitely be a great addition to the project.
It also occurred to me that the token connector README was missing some important notes about how to deploy and run it manually. Perhaps @nguyer can give me an approval on these: https://github.com/hyperledger/firefly-tokens-erc1155/pull/46
Of course ! For the solidity contract part instead of OpenZeppelin cani use https://github.com/hyperledger/fabric-samples/tree/main/token-erc-1155
?
Yes, that looks like a very reasonable thing to try. Didn't know anybody had tried porting ERC1155 to Fabric.
The one thing I see - it looks like this chaincode mainly deals with fungible tokens. If you wanted to work with non-fungible tokens, it may require some tweaks (so that if you specify a particular token is non-fungible, you cannot mint more than 1 of that token).
But still, it's a very good starting point even to just get fungible tokens working on Fabric, and then go from there.
ok thx i will keep investigate and keep you posted. thx :)
A few background notes for how I implemented fungible/non-fungible pools on ERC1155:
- when you request to create a fungible pool, it allocates a single token ID - each time you call mint, it creates more of that token
- when you request to create a non-fungible pool, it allocates a range of token IDs (it masks off the high 128 bits as a "pool ID") - each time you call mint, it allocates a new token within that range by incrementing the lower 128 bits
There are some more notes in the Solidity contract, but that's essentially how I implemented the two types. Fungible is the easier one to implement, so again it's probably easiest to just start there.
ok i saw that in solidity.. so you distinguish a NFT from a non NFT just by looking a the last bit of the token ID
I was also having a look at https://github.com/hyperledger/fabric-samples/tree/main/token-erc-721 for NFT on fabric
yes, ERC1155 can support multiple types of tokens, so I used a split bit implementation to distinguish fungible tokens from non-fungible tokens
some other standards only support one type - like ERC721 is non fungible only
:mega: FireFly v0.11.1 has been released. This patch release includes important fixes and hardening for recent features.
https://github.com/hyperledger/firefly/releases/tag/v0.11.1
Hello everyone!
It's been a little bit, but we're excited for another Community Call tomorrow! Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/FIR/2021-12-08+FireFly+Community+Call
Wednesday, December 8, 2021 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's Agenda:
- Performance testing and tuning
- Status update on Custom On-Chain Logic
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
:mega: FireFly v0.11.2 has been released. This release includes a few important bug fixes and some new UI charts.
https://github.com/hyperledger/firefly/releases/tag/v0.11.2
Has joined the channel.
Hi all! Hopefully you saw that the calendar invite for today's Community Call was canceled, but if not, I just wanted to send a quick note to remind people that there is no Community Call today. I hope everyone has a great holiday season and is able to take some needed time off to spend with loved ones. See you in two weeks!
Hello, everyone. This is a notice that the Final Comment Period for FIR-2 Custom On-chain Logic has begun. It will close one week from today, on 2022-01-10. If you are interested in this functionality, this is the last opportunity to provide feedback on this proposed architecture and functionality change. https://github.com/hyperledger/firefly-fir/pull/2
Happy new year! :tada: We're back and looking forward to another FireFly Community Call tomorrow! Details for tomorrow's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/FIR/2022-01-05+FireFly+Community+Call
Wednesday, January 5, 2022 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Tomorrow's agenda is light, but here's what we have:
- Update on v1.0 progress
- New maintainer nomination
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
@nguyer I need someone from Firefly to look at https://hackerone.com/reports/1416432 - I've invited you all to h1
Sure, I'm taking a look
How should I be logging in? I registered just now as nguyer / nicko.guyer@kaleido.io
It's saying I don't have access to that report though
I sent another invite to your email address
Got it. Thanks
not sure why the first invite didn't work
Has joined the channel.
Hi guys
Good morning guys,
I been trying to troubleshoot this issue for days now and was woundering if anyone any tips for a solution.
trying to upload a image file via firefly
using:
curl --location --request POST 'http://35.175.18.83:5000/api/v1/namespaces/default/data' \
--form 'file=@"/C:/Users/mbarbuzzi/Downloads/sleeping-mask.png"'
and pull the image file and it's information so we display in our app.
however I can't figure how to do that using the Data Exchange API
I try using /data as a path or the blob hash but keeping no blob found.
Like:
http://35.17.184.83:5105/api/v1/blobs/aacd217811aae10798bb53357f2d4b914762819e3d6b767a337b5b15c079e6c6
Hey, good morning, and welcome!
Is there a reason you want to use the Data Exchange's API to retrieve the image, vs just using FireFly's API for both uploading and retrieving?
I would perfer to use FireFly for retrieving image
but I did'nt see any info clear details on the website how I would pull that data
Okay great. Have you had a look at this example on the docs site? https://hyperledger.github.io/firefly/gettingstarted/private_send.html#example-3-upload-a-blob-with-metadata-and-send-privately
Actually, that just shows how to upload it, which you already figured out
yep :)
not pull :(
GET
/namespaces/{ns}/data/{dataid}/blob should give you need I think
will try now
Let me know if that doesn't work for you
trying now
is any tips on how we can secure the firefly api
so only authorized people/app can run the quires?
Typically you would want it behind some sort of load balancer, reverse proxy, or other network appliance that is in charge of authenticating requests
yea I had a feeling. just wanetd to make sure :)
thanks for your help
Sure! happy to help
Hello all,
This is a notice that the Final Comment Period for FIR-4 Rest API Query Syntax Enhancements has begun, with a disposition to merge. It will close one week from today, on 2022-01-17. If you are interested in this functionality, this is the last opportunity to provide feedback on this proposed change.
This is a relatively small change and there is strong consensus among the maintainers. However it does introduce a breaking change, and thus is going through the FIR process. If your app uses query parameter filters on the FireFly API, you may be interested in giving it a look, if you haven't already.
Thanks!
https://github.com/hyperledger/firefly-fir/pull/4
Has joined the channel.
Has joined the channel.
Hi all!
Sorry for the late notice (usually I send this note out the day before) but we are having a community call today, and there are some interesting topics on the agenda for today. Details for today's FireFly Community Call can be found here: https://wiki.hyperledger.org/display/FIR/2022-01-19+FireFly+Community+Call
Wednesday, January 19, 2022 8:00 AM PT
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Today's agenda:
- Update on recent FIRs
- New maintainer vote
- New maintainer nomination
- Discussion and feedback on processes:
- FIR Process
- Process for adding maintainers
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
Good Morning everyone,
After you upload a blob and Broadcast the uploaded data using the firefly API. how do you pull the Transaction Hash that would be linked via blockchain?
Hi @jas191! Sorry I didn't see your message yesterday.
The gist of it is that you want to do is listen for a `message_confirmed` event for that broadcast and then you can look up more information about transaction at that point. There's a doc page here that should get you started on how listening for events works: https://hyperledger.github.io/firefly/gettingstarted/events.html
Has joined the channel.
Hi @sbohanlf! Welcome! :wave:
thanks @nguyer!
Has joined the channel.
I was wondering if someone could clarify how to upload a file into firefly on the IPFS. I understand that we can use the curl command as shown in the documentation, but I am struggling to implement this just using the API.
Hey @nandrews283! I assume you're looking at the docs here: https://hyperledger.github.io/firefly/gettingstarted/private_send.html#example-3-upload-a-blob-with-metadata-and-send-privately
You should also be able to upload a file using the Swagger UI (hosted at http://localhost:5000/api by default when running FireFly locally), or by using a tool like Postman. I can give more specific pointers on those, but is that the type of thing you're looking for?
The general flow in all cases is to set the request body format to "form-data", and then set "autometa=true" and set "file" to the actual file contents (similar to the curl command from the docs).
Hi all! We have a FireFly Community Call tomorrow, and it promises to be another full agenda. Details for the call can be found here: https://wiki.hyperledger.org/display/FIR/2022-02-02+FireFly+Community+Call
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Agenda:- ERC20 / ERC721 Token Connector
- FireFly v0.12.0 Updates
- FireFly UI Plans & Discussion
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
Hi all! We have a FireFly Community Call tomorrow, and it promises to be another full agenda. Details for the call can be found here: https://wiki.hyperledger.org/display/FIR/2022-02-02+FireFly+Community+Call
Join link: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
Agenda:
- ERC20 / ERC721 Token Connector
- FireFly v0.12.0 Updates
- FireFly UI Plans & Discussion
- Open discussion
As always, thank you all for your participation in these calls! We hope to see you there!
Yeah! And that is what i was looking at. Sorry I am kind of a beginner to this. So say I have a PDF save to my local directory.
I would assume that with the Swagger UI or Postman I would use Post to "/namespaces/{ns}/data"
What would the Request body look like?
OH!! multipart/form-data
I did not even see that there, I will try that and report back. Thank you so much
Great, hopefully that puts you on the right track. Definitely follow up if it doesn't!
:mega: FireFly v0.12.0 has been released! This is a large release as we come closer to the 1.0.0 milestone, and includes lots of exciting features such as ERC20 & ERC721 support, enhanced file support, richer query filters, and the groundwork for custom on-chain logic. There are some breaking API changes, so please read over the full release notes and make an effort to migrate projects if needed.
https://github.com/hyperledger/firefly/releases/tag/v0.12.0
Hi guys, this what trying to do with firefly-api however Im having some issues with the request and how to make it.
Trying to do that using firefly-api
upload a image file ie: boob and mint an token at same time so it's associated to the image-upload then have the token minted to send a specific wallet address
how would I do that in terms of query?
api endpoiont: api/v1/namespaces/default/tokens/mint
{
"amount": 1,
"to": "0x07eab7731db665caf02bc92c286f51dea81f923f",
"message": {
"header": {
"type": "transfer_private",
},
"group": {
"members": [{
"identity": "org_1"
}]
},
"data": [{
"value": "'file=@"/C:/Users/mbarbuzzi/Downloads/sleeping-mask.png"
}]
}
}
also when I checked my stack via firefly-tokens-erc1155 ff info does that get installed by default so you can use the tokens or no if not how do I add to my slack using the cli
also using tokens is there a way to transfer the tokens into mobile wallet have a mobile work with fire, our app then does it thing push datta to ipfs we also want a token transfer to happen which would go to some external wallet
@jas191 The token connectors for your stack can be configured with the `-t` option to the CLI, but the default is to create an instance of the ERC1155 connector for each member.
Regarding file upload, you must upload the file first before it can be used in a message or mint. You would follow the steps similar to what is described on this page for uploading a blob: https://hyperledger.github.io/firefly/gettingstarted/private_send.html#example-3-upload-a-blob-with-metadata-and-send-privately
Once you have uploaded the file and received an "id" for it, you can perform a mint as you have shown. You just include the data ID, such as `"data": [{ "id": "put-id-here" }]`
That will cause the data to be sent privately in a message, and also a new token will be minted (with the message ID and hash recorded on-chain in the mint operation). If you hit errors at any point, you can share them here.
As far as using mobile wallets with FireFly - that's a much longer answer and I know I won't be able to cover it myself. Possibly someone else here can. But more of the community has moved to the FireFly Discord now, so it might be a good topic to raise there if you're able: https://discord.com/invite/nnQw2aGhX6
thanks andrew, for sure I will join the discord
Hello everyone, I was trying out the api to register custom on chain smart contracts and to interact with them using firefly.
But, the documentation for that part isn't there. I was wondering whether there is any example readily available with one of the maintainers
How do I figure out what the operator is? "operator should not be empty" as tryng to mint a token and data along with it
as the docs aren't very clear on that
{
"amount": 1,
"to": "a99f6c148d4df7b0a8e16054d0e6734f347bb73d",
"message": {
"data": [{
"id": "27b2c9bc-f6c5-4817-956a-3b27a71a61f2"
}]
}
}
and response its giving back is: {
"statusCode": 400,
"message": [
"poolId should not be empty",
"operator should not be empty"
],
"error": "Bad Request"
}
for minting & data transfer
request trying to put-tog other: {
"poolId": "string",
"operator": "string",
"amount": 1,
"to": "a99f6c148d4df7b0a8e16054d0e6734f347bb73d"",
"message": {
"header": {
"type": "transfer_private",
},
"group": {
"members": [{
"identity": "org_1"
}]
},
"data": [{
"id": "27b2c9bc-f6c5-4817-956a-3b27a71a61f2"
}]
}
}
@sukrutsathaye yes, the custom on-chain logic work is still in flight and only considered a "preview" at this point since it's still undergoing some evolution. I know @nguyer is deep in that work right now - was just reviewing his latest PR. Not sure if he has any examples laying around?
@jas191 are you sending a request to FireFly or directly to the token connector? This looks like a response from the connector.
Just another reminder that we are officially moving from Rocket Chat to Discord, along with the rest of Hyperledger: https://discord.gg/hyperledger
Join us in the FireFly channel there!
just joined
:)
this chat has moved to https://discord.gg/hyperledger/
Has left the channel.
Has joined the channel.
Has joined the channel.