tkuhrt (Fri, 01 Nov 2019 16:29:49 GMT):
https://github.com/hyperledger-labs/blockchain-integration-framework

tkuhrt (Fri, 01 Nov 2019 16:29:49 GMT):
Discussion for the Blockchain Integration Framework lab

tkuhrt (Sat, 02 Nov 2019 15:45:23 GMT):
User User_1 added by tkuhrt.

peter_somogyvari (Sat, 02 Nov 2019 16:07:15 GMT):
Thank you Tracy!

faraggi (Tue, 12 Nov 2019 16:34:53 GMT):
Has joined the channel.

nicky01 (Thu, 21 Nov 2019 17:23:57 GMT):
Has joined the channel.

nicky01 (Thu, 21 Nov 2019 17:23:57 GMT):
Hi Tracy are you here?

adineshreddy1 (Wed, 27 Nov 2019 07:39:49 GMT):
Has joined the channel.

hartm (Tue, 03 Dec 2019 03:47:19 GMT):
Has joined the channel.

hartm (Tue, 03 Dec 2019 03:47:34 GMT):
Hi Everyone!

JHamilton (Tue, 03 Dec 2019 03:49:59 GMT):
thanks for joining @hartm!

knagware9 (Wed, 04 Dec 2019 17:29:10 GMT):
Has joined the channel.

glotov (Thu, 05 Dec 2019 16:39:56 GMT):
Has joined the channel.

glotov (Thu, 05 Dec 2019 16:39:56 GMT):
hi all!

peter_somogyvari (Thu, 05 Dec 2019 16:40:03 GMT):
Hi Denis

peter_somogyvari (Thu, 05 Dec 2019 16:40:05 GMT):
Mostly I would say #6 is about input validation. There isn't a single input validation / state validation line of code in there so for example if any of the input parameters are in an incorrect format, it will still try to do it's thing which is a bug at best some sever security vulnerability at worst (not saying it is, just that it's possible). I would write checks for #6 that enforce the contract between method and it's caller, verify that all method parameters are exactly what we expect them to be and if anything else comes in then just throw it right back.

glotov (Thu, 05 Dec 2019 16:41:20 GMT):
ok, will look what to do there then

VipinB (Thu, 05 Dec 2019 17:24:54 GMT):
Has joined the channel.

glotov (Thu, 05 Dec 2019 17:29:58 GMT):
BTW, this should also be a good new issue - to reduce the CI working time somehow. How it is about 16 minutes and still does not include Corda...

peter_somogyvari (Thu, 05 Dec 2019 20:28:21 GMT):
Agreed, I started working on this last week: https://github.com/hyperledger-labs/blockchain-integration-framework/pull/75 Work in progress still.

peter_somogyvari (Thu, 05 Dec 2019 20:34:03 GMT):
Also this, to reduce etcd logging which mostly about just reading the logs but also speed because logging is also CPU time https://github.com/etcd-io/etcd/issues/11407

HLFPOC (Fri, 06 Dec 2019 09:48:47 GMT):
Has joined the channel.

glotov (Fri, 06 Dec 2019 13:48:01 GMT):
ah, this `Unhandled rejection Error: invalid config key requested: error` again (https://travis-ci.org/denis-yu-glotov/blockchain-integration-framework/jobs/621601200#L811). Can be fixed by updating all `package-lock.json` files, but do you know a better way?

peter_somogyvari (Fri, 06 Dec 2019 16:16:30 GMT):
Should be fixed once we can update to NodeJS 10x, but I'm still working on that (when I do upgrade, CI script fails, so have to investigate it why). This is the branch (WIP): https://github.com/petermetz/blockchain-integration-framework/tree/feat/support-nodejs-10x

JHamilton (Fri, 06 Dec 2019 17:49:15 GMT):
We are on the calendar! Hope to see everyone at an upcoming session ^_^ https://lists.hyperledger.org/g/labs/calendar

rjagadee (Fri, 06 Dec 2019 18:06:20 GMT):
Has joined the channel.

peter_somogyvari (Fri, 06 Dec 2019 18:18:39 GMT):
Just in case others find this useful: You can connect the HL calendars (both main and labs) to MS Outlook via the ical feed URLs that you can find on the calendar page linked above. Spent some time digging into this because I had no clue initially how to do it or if it was even possible.

glotov (Mon, 09 Dec 2019 18:11:25 GMT):
ah, it is 6am my time, will you have it recorded?

JHamilton (Mon, 09 Dec 2019 20:52:48 GMT):
Yes, there will always be one time zone each session that it does not work well for. will try to record (my first time w/ zoom) and share!

JHamilton (Mon, 09 Dec 2019 20:56:11 GMT):
need to figure out how to do this for future sessions anyways!!

peter_somogyvari (Tue, 10 Dec 2019 04:22:37 GMT):
https://github.com/petermetz/blockchain-integration-framework/blob/docs/peter.somogyvari/whitepaper/docs/whitepaper/whitepaper.md

hartm (Tue, 10 Dec 2019 04:37:03 GMT):
Example of a proposal: https://docs.google.com/document/d/1JtFT5L-82egj6shgGXzTsNAg6_UHuMheKfsst6NS_Xo/edit?usp=sharing

JHamilton (Tue, 10 Dec 2019 05:02:21 GMT):
Key outcomes I captured for the Dec 9th; please advise if anything I missed: [1] Jonathan will email IBM contact re ability to contribute [2] Hart will begin preparing proposal, with end goal of approval before the Global Summit and being able to gain contribution momentum there [3] Peter shared design level details 👆 and request everyone to provide feedback & suggest alternatives; goal to start working on refactoring to new plugin arch in the new year [4] Fujitsu team will start enhancing documentation of contributed code; JH request to use Github issues and tags (please reach out if questions!) https://github.com/hyperledger-labs/blockchain-integration-framework/issues [5] Fujimoto-san will share list of Github IDs for contributors & maintainers

JHamilton (Tue, 10 Dec 2019 05:02:21 GMT):
Key outcomes I captured for the Dec 9th; please advise if anything I missed: [1] Jonathan will email IBM contact re ability to contribute and if so timing for Asia+Americas instance as they appear to be Australia based [2] Hart will begin preparing proposal, with end goal of approval before the Global Summit and being able to gain contribution momentum there [3] Peter shared design level details 👆 and request everyone to provide feedback & suggest alternatives; goal to start working on refactoring to new plugin arch in the new year [4] Fujitsu team will start enhancing documentation of contributed code; JH request to use Github issues and tags (please reach out if questions!) https://github.com/hyperledger-labs/blockchain-integration-framework/issues [5] Fujimoto-san will share list of Github IDs for contributors & maintainers

JHamilton (Tue, 10 Dec 2019 05:03:21 GMT):
@sfuji822 👆

peter_somogyvari (Wed, 11 Dec 2019 19:23:21 GMT):
@glotov Could you please rebase https://github.com/denis-yu-glotov/blockchain-integration-framework/tree/denis/multisig onto the master branch? I tried to do it myself before merging but your fork is read-only so didn't have the permission. (You could also just grant permission to edit the fork then I'm happy to do the chore)

peter_somogyvari (Wed, 11 Dec 2019 19:34:53 GMT):
Oops, nvm, I see you already merged it.

peter_somogyvari (Wed, 11 Dec 2019 21:28:09 GMT):
Some press coverage we just received: https://www.ledgerinsights.com/accenture-open-sources-enterprise-blockchain-interoperability-solution-with-hyperledger/ :woo:

glotov (Thu, 12 Dec 2019 08:16:17 GMT):
Yes, I rebased. Sorry for permissions

glotov (Thu, 12 Dec 2019 18:02:03 GMT):
@peter_somogyvari, do you have experience with running Corda and installing JDK for it? Here are my thoughts https://github.com/hyperledger-labs/blockchain-integration-framework/pull/84#issuecomment-565117066, please have a look.

peter_somogyvari (Thu, 12 Dec 2019 18:07:45 GMT):
I'll reply on the GitHub issue

glotov (Fri, 13 Dec 2019 15:00:31 GMT):
JDK arror is fixed, thanks all involved :)

glotov (Fri, 13 Dec 2019 15:00:31 GMT):
JDK error is fixed, thanks all involved :)

glotov (Fri, 13 Dec 2019 15:05:00 GMT):
Now I see `commitlint` bot coming and complainig about ```✖ message may not be empty ✖ type may not be empty```. Have you seen this? @peter_somogyvari https://github.com/hyperledger-labs/blockchain-integration-framework/pull/84#issuecomment-565427517

glotov (Fri, 13 Dec 2019 15:05:00 GMT):
Now I see `commitlint` bot coming and complainig about ```✖ message may not be empty ✖ type may not be empty```in my every commit. Have you seen this? @peter_somogyvari https://github.com/hyperledger-labs/blockchain-integration-framework/pull/84#issuecomment-565427517

JHamilton (Fri, 13 Dec 2019 15:30:57 GMT):
i added commitlint bot for #53 but i ran out of steam before it got authorized (looks like Tracy or someone did overnight). is it a configuration issue?

MicBowman (Fri, 13 Dec 2019 16:20:24 GMT):
Has joined the channel.

JHamilton (Fri, 13 Dec 2019 17:41:14 GMT):
Proposed agenda for Monday the 16th session; please respond in thread with changes • Introductions • Visit the design principles and discuss any feedback IBM team has • Q&A about the IBM whitepaper • Discuss any next steps on collaboration • Others?

peter_somogyvari (Fri, 13 Dec 2019 18:20:32 GMT):
I don't have permission to it either because the repo settings don't even show up on the main repo where I could see the configuration of the bot. Idea: Maybe we can use the new GitHub actions feature to install/use the bot instead of the old GitHub Apps way? It's the same bot but made accessible through the actions feature and I'm hoping this to improve the situation because I *can* see the 'actions' button on the main repo which makes me assume that we wouldn't have to depend on Tracy for small time configuration changes on the bot. https://github.com/marketplace/actions/commit-linter

peter_somogyvari (Fri, 13 Dec 2019 19:58:22 GMT):
I know earlier we put down the identities design principle as aspirational, but thinking through the use-cases that I had in mind I came to think that there's a lot of the real-world scenarios where permissions/access control has a crucial role (which is why we also see a lot of permission-ed DLTs being developed for enterprise use-cases) and permissions/ACLs are useful when we deal with identities as well. So, IMO dealing with identities should also be at the core of what we intend to do instead of being on the wish list. Note: I don't mean for us to be a standalone identity framework or identity provider of some sort, just that we focus a little more on the ability of being able to correlate identities cross-chain, supporting especially the framework(s) that are being developed by the identity WG here at Hyperledger. Thoughts?

glotov (Fri, 13 Dec 2019 20:38:36 GMT):
ah, about `lgtm`, this changelist is not ready for review, Travis VM cannot handle all 3 repos and fail in different places.

glotov (Fri, 13 Dec 2019 20:38:59 GMT):
@peter_somogyvari , how do you mark a PR as work-in-progress?

hartm (Fri, 13 Dec 2019 21:05:40 GMT):
What did you have in mind? I'm hoping we can make this as pluggable as possible in that we define some common interfaces around identity so that we can use different identity management interfaces. As you (in my opinion, correctly) point out, we don't want to have to implement an identity framework ourselves.

hartm (Fri, 13 Dec 2019 21:05:40 GMT):
What did you have in mind? I'm hoping we can make this as pluggable as possible in that we define some common interfaces around identity so that we can use different identity management solutions. As you (in my opinion, correctly) point out, we don't want to have to implement an identity framework ourselves.

peter_somogyvari (Fri, 13 Dec 2019 21:56:03 GMT):
> ah, about lgtm, this changelist is not ready for review, Travis VM cannot handle all 3 repos and fail in different places. peter_somogyvari , how do you mark a PR as work-in-progress? I agree mate, that's what I meant as well: it looks good to me, but first the CI and commitlint issue has to be green :-) You can set the PR to be a "draft" : https://github.blog/2019-02-14-introducing-draft-pull-requests/ The link shows how to do it when opening a new PR but I believe you can also modify the status of an existing PR to make a draft instead of a "ready for review" PR

peter_somogyvari (Fri, 13 Dec 2019 22:14:17 GMT):
Still reading other's papers to get a better grasp of the implementation details (and what I *exactly* want to do). BUT the vision is that whatever the identity WG comes up with from that big consolidation process of theirs should be something that we are aligned with. Two reasons for the latter idea: 1) It would be nice if different Hyperledger projects fit/worked together like legos (so long as they don't constrain each other of course). Don't know if this has ever been an explicit goal or not but I just made it up myself that I think it should be. 2) From what I understood based on the recent meeting minutes of the identity WG is that they are trying to come up with something uniting DID, DIF, Sovrin/Indy and that's basically the heavy lifting done (if they succeed) for us in terms of how we should approach identity. I know it's vague, but even just talking about it helps me seeing the bigger picture (at least it feels like it)

hartm (Fri, 13 Dec 2019 22:54:19 GMT):
What the identity WG is doing is really cool, but I suspect we will want a workable solution before they are done.

hartm (Fri, 13 Dec 2019 22:54:57 GMT):
Yes, it would be awesome if LH projects fit/worked together like legos. This form of modular design has been a goal since the beginning of Hyperledger. Unfortunately, it has not been widely realized.

peter_somogyvari (Fri, 13 Dec 2019 22:55:20 GMT):
Oh. I guess I was making the assumption that they are close to being done. Back to the drawing board then. :-)

hartm (Fri, 13 Dec 2019 22:55:30 GMT):
And yes, the identity interface is something we need to figure out.

hartm (Fri, 13 Dec 2019 22:55:40 GMT):
I would love to see what you had in mind, or what you needed.

hartm (Fri, 13 Dec 2019 22:56:01 GMT):
The best thing to do is to probably start with a list of things we want an identity service provider to do and then go from there.

peter_somogyvari (Sun, 15 Dec 2019 00:10:58 GMT):
Agreed, 100%. I'm working on an IdentityProvider interface definition file, but it's a very iterative process (I throw away ideas a lot because I realize I wasn't getting the bigger picture). Just realized that I should also be looking at Aries as well. What I know for sure I'd need from the StorageProvider plugin implementations so far: 1) Ability to prove that a wallet is associated with a given identity (cross-chain). 2) Provide access control lists of any kind of on-chain or even off-chain entities (wallets, smart contracts, identities, etc).

kh.nguyen (Sun, 15 Dec 2019 19:13:24 GMT):
Has joined the channel.

kh.nguyen (Sun, 15 Dec 2019 19:21:34 GMT):
Hi. Is there a link to join the discussion online?

hartm (Sun, 15 Dec 2019 19:30:27 GMT):
We should post a link to the meeting online and send it out.

hartm (Sun, 15 Dec 2019 19:30:32 GMT):
Probably to the TSC list.

JHamilton (Sun, 15 Dec 2019 21:00:26 GMT):
yes i should have included the meeting invite in the original message, but they are all published out on the Hyperledger public calendars https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings

JHamilton (Sun, 15 Dec 2019 21:02:05 GMT):
https://lists.hyperledger.org/calendar

JHamilton (Sun, 15 Dec 2019 21:02:52 GMT):
Yes, they are all published out to the public calendars / email lists. i incorrectly assumed everyone was familiar

kh.nguyen (Mon, 16 Dec 2019 02:41:13 GMT):
Sounds great! Talk to you guys in a few hours!

glotov (Mon, 16 Dec 2019 08:45:37 GMT):
Do you have a recording of this meeting? I heard strong echo, but after the call it appeared it was my local mic echoing to my local phones which I thought was from your side :)

easeev (Mon, 16 Dec 2019 12:18:43 GMT):
Has joined the channel.

peter_somogyvari (Mon, 16 Dec 2019 18:19:17 GMT):
Ohh, sorry to hear that :-) I do have a recording, but still working on the uploading of the files (it's not clear where exactly are we supposed to upload them). But I'll send the link out here as soon as possible.

hartm (Mon, 16 Dec 2019 19:23:37 GMT):
The difficulty with all of this is that there is unlikely to be one identity provider we can use for all of this, since different chains will use different identity providers and we probably do not want to implement our own provider. Hence why I think we should focus on a functionality and then try to shim over existing providers to our functionality interface.

hartm (Mon, 16 Dec 2019 19:23:40 GMT):
Is this making sense?

peter_somogyvari (Mon, 16 Dec 2019 21:26:18 GMT):
Makes perfect sense, definitely helps my thought process, thank you!

peter_somogyvari (Mon, 16 Dec 2019 22:40:01 GMT):
The recording of this morning's BIF call is up on the Wiki: https://wiki.hyperledger.org/display/labs/Blockchain+Integration+Framework+-+16+December+2019

hartm (Mon, 16 Dec 2019 22:48:01 GMT):
I'd be happy to go over stuff if you'd like to run anything by me about this.

sanket1211 (Tue, 17 Dec 2019 05:37:42 GMT):
Has joined the channel.

nikolas (Tue, 17 Dec 2019 11:20:52 GMT):
Has joined the channel.

glotov (Tue, 17 Dec 2019 19:37:34 GMT):
Hi @peter_somogyvari, I tried to run our Corda under Circle-CI, here are my (unsuccessful) results so far https://github.com/hyperledger-labs/blockchain-integration-framework/issues/90. Maybe you have some ideas about that?

peter_somogyvari (Tue, 17 Dec 2019 19:41:17 GMT):
Hi Denis, I would look at the corda documentation/source code and try to figure out where all that memory goes (e.g. why do they need so much of it) and then try to tweak configuration parameters in a way so that maybe it gets reduced. Maybe it's not even possible because potentially the authors of Corda already optimized it so much that the current RAM usage is the absolute minimum but I doubt it because it would be strange for any piece of software to be needing several gigabytes of RAM just to basically run idle unless there's something funky going on. I'll take a deeper look today just trying to finish up some documentation first

glotov (Tue, 17 Dec 2019 19:42:58 GMT):
why do you think it if because of memory?

glotov (Tue, 17 Dec 2019 19:43:31 GMT):
on my vm, our Corda mostly works

peter_somogyvari (Tue, 17 Dec 2019 22:14:33 GMT):
I saw it use up 7-8 GB RAM on my VM so I figured the RAM gets filled up and then it starts swapping hard which slows everything to a halt. Could be wrong and instead could be just CPU bound of course, I don't yet have evidence either way.

sfuji822 (Wed, 18 Dec 2019 01:29:28 GMT):
Has joined the channel.

sfuji822 (Wed, 18 Dec 2019 01:29:29 GMT):
Hello guys. I think meetings scheduled on 24th and 31st will be canceled. Can you modified those ?

JHamilton (Wed, 18 Dec 2019 02:30:27 GMT):
yes, agreed @sfuji822 will take care of that. will look forward to resuming in the new year!

glotov (Thu, 19 Dec 2019 14:38:41 GMT):
'There is insufficient memory for the Java Runtime Environment to continue'

glotov (Thu, 19 Dec 2019 14:39:00 GMT):
https://44-219771363-gh.circle-artifacts.com/0/home/circleci/project/packages/core/examples/simple-asset-transfer/corda/logs/web-partyD.log

glotov (Thu, 19 Dec 2019 14:41:12 GMT):
@peter_somogyvari was right, this happens when I start Fabric in addition to running Corda,

nmarco (Thu, 19 Dec 2019 19:17:17 GMT):
Has joined the channel.

nmarco (Thu, 19 Dec 2019 19:17:18 GMT):
Saw some notes about Fabric to Bitocin in the draft whitepaper. Is there a bitcoin connector in development?

peter_somogyvari (Fri, 20 Dec 2019 03:10:55 GMT):
It's in the design phase, no code has been written yet. :-)

nmarco (Fri, 20 Dec 2019 14:09:01 GMT):
Any design docs I can check out ?

nmarco (Fri, 20 Dec 2019 14:09:10 GMT):
or conversations I can follow?

JHamilton (Fri, 20 Dec 2019 22:44:19 GMT):
thanks for your interest @nmarco we have only just completed the design principles which are published and will be keeping things in the open as we go forward. we would welcome your collaboration in the weekly contributors session although we are taking a little holiday break until 2020

JHamilton (Fri, 20 Dec 2019 22:44:45 GMT):
here's the design principles, technically we are still in request for comment :)

JHamilton (Fri, 20 Dec 2019 22:44:47 GMT):
https://docs.google.com/document/d/1oCF7q_or7EWlVEmCMYuGU3ksKrNjHf07pSTrviRfktk/edit?pli=1

nmarco (Fri, 20 Dec 2019 22:45:12 GMT):
awesome, for sure. To stay in the loop is this channel the best place to follow?

JHamilton (Fri, 20 Dec 2019 22:45:22 GMT):
and the contributors sessions can be found on the Hyperledger calendar https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings

JHamilton (Fri, 20 Dec 2019 22:45:29 GMT):
yup yup!

nmarco (Fri, 20 Dec 2019 22:45:51 GMT):
Thanks and enjoy the holidays!

JHamilton (Fri, 20 Dec 2019 22:46:02 GMT):
thanks, you too!

sfuji822 (Fri, 27 Dec 2019 02:25:56 GMT):
User User_2 added by sfuji822.

peter_somogyvari (Fri, 27 Dec 2019 08:01:31 GMT):
Hi Hart, sorry for the slow response, I wanted to come back with something concrete. I would love some feedback on a few ideas related to identity/authentication. Much more details on the link (chapter 5 of the document), but here are the key points: * For browser based apps that cannot safely store private keys: We need a server side keychain. * We need our own authentication service so that said web app users users can interact with the server side keychain if need be * All this enables both client and server-side signing of transactions that a user wants to submit to a ledger through BIF. * Make it possible for end users to associate their BIF identity to wallets on other ledgers that they own * Registry of identities, credentials and other metadata so that a search/discovery feature can be implemented that maps a name of a person or organization to their digital identity, wallets, etc. (only what they choose to make public/discoverable) https://github.com/petermetz/blockchain-integration-framework/blob/docs/peter.somogyvari/whitepaper/docs/whitepaper/whitepaper.md#5-identities-authentication-authorization

glotov (Mon, 30 Dec 2019 19:58:36 GMT):
Hi @peter_somogyvari, please review https://github.com/hyperledger-labs/blockchain-integration-framework/pull/84 when you have time.

adityasingh177 (Sat, 04 Jan 2020 05:46:04 GMT):
Has joined the channel.

Abhishek2700 (Mon, 06 Jan 2020 07:18:02 GMT):

Clipboard - January 6, 2020 12:46 PM

Abhishek2700 (Mon, 06 Jan 2020 07:18:07 GMT):
Has joined the channel.

Abhishek2700 (Mon, 06 Jan 2020 07:18:09 GMT):
Hi Everyone , i was trying to run the sample example for simple asset transfer for blockchain integration framework. I did start the fabric and corda blockchain but i am getting error while starting the validators for corda and fabric.

Abhishek2700 (Mon, 06 Jan 2020 07:20:05 GMT):

Clipboard - January 6, 2020 12:48 PM

glotov (Mon, 06 Jan 2020 08:58:50 GMT):
Did you run `npm run share -noquorum`? You may follow `packages/core/tools/ci.sh` for reference.

glotov (Mon, 06 Jan 2020 08:58:50 GMT):
Did you run `npm run share noquorum`? You may follow `packages/core/tools/ci.sh` for reference.

Abhishek2700 (Mon, 06 Jan 2020 09:42:25 GMT):
@glotov , but there are no scripts like share -noquorum at examples/simple-asset-transfer

Abhishek2700 (Mon, 06 Jan 2020 09:42:25 GMT):
Hi @glotov , but there are no scripts like share -noquorum at examples/simple-asset-transfer

glotov (Mon, 06 Jan 2020 09:45:05 GMT):
I meant this: https://github.com/hyperledger-labs/blockchain-integration-framework/blob/master/packages/core/tools/ci.sh#L102. But for your case (Corda+Fabric) you need to specify `noquorum` as a parameter instead

Abhishek2700 (Mon, 06 Jan 2020 09:46:42 GMT):
So do i need to run script like this ? ./ci.sh --noquorum

glotov (Mon, 06 Jan 2020 09:48:59 GMT):
if you want to run complete path from sturting all blockchains to running all scenarios - yes, `ci.sh` will do

glotov (Mon, 06 Jan 2020 09:48:59 GMT):
if you want to run complete path from starting all blockchains to running all scenarios - yes, `ci.sh` will do

glotov (Mon, 06 Jan 2020 09:49:44 GMT):
provided you have a machine strong enough (6+ cpu, 8+ Gb ram)

Abhishek2700 (Mon, 06 Jan 2020 09:51:45 GMT):
i just need to see how does assets get transferred from one dlt to another. So i wanted to run the simple-asset-transfer between 2 dlt's corda and fabric. I have initialized the fabric and corda using https://github.com/hyperledger-labs/blockchain-integration-framework/blob/master/docs/tutorials/simple-asset-transfer.md document. I am able to run the blockchains but not able to run the validators.

glotov (Mon, 06 Jan 2020 09:52:45 GMT):
ah, you may reference the source of `ci.sh` to see how to start them:

glotov (Mon, 06 Jan 2020 09:54:51 GMT):
here you can see how to start validators: https://github.com/denis-yu-glotov/blockchain-integration-framework/blob/denis/scenarios-corda/packages/core/tools/ci.sh#L81

glotov (Mon, 06 Jan 2020 09:55:35 GMT):
and here for Corda: https://github.com/denis-yu-glotov/blockchain-integration-framework/blob/denis/scenarios-corda/packages/core/tools/ci.sh#L104

glotov (Mon, 06 Jan 2020 09:57:07 GMT):
(this is from `denis/scenarios-corda` branch because it is pending review, new year holidays)

Abhishek2700 (Mon, 06 Jan 2020 10:07:34 GMT):
ok thanks @glotov , i will try and do it this way

adityasingh177 (Mon, 06 Jan 2020 16:09:29 GMT):
Hi all , Hi @JHamilton where can i find the docs to setup the integration framework and docs related to apis?

peter_somogyvari (Mon, 06 Jan 2020 19:04:09 GMT):
I'm on it

peter_somogyvari (Mon, 06 Jan 2020 23:22:23 GMT):
Hi @adityasingh177 no finalized docs just yet, there's a few of us working on the design/architecture on separate documents (all of which will get eventually merged into one single document with cohesion in mind). Personally, my plan is to have a unified REST API with websocket support and a client side SDK that works in browsers and NodeJS as well. The API documentation will be done most likely with a tool, something with automation in mind such as Swagger (but we are not there yet). Also, you could take a look at the ConnectionChain REST API documentation but keep in mind that these will change as we mature and reach the first stable release (1.0). Also take a look at this if you are interested in higher level documentation and won't mind reading an early draft: https://github.com/petermetz/blockchain-integration-framework/blob/docs/peter.somogyvari/whitepaper/docs/whitepaper/whitepaper.md

JHamilton (Tue, 07 Jan 2020 00:19:04 GMT):
@adityasingh177 sorry for my delayed response, really hectic first day back after 2 week holiday 😅 As Peter mentions we don't have much in terms of a setup; your best bet frankly at the moment is the CI script where you can piece together the deps for an Ubuntu install (Docker, NPM, JDK, etc). https://github.com/hyperledger-labs/blockchain-integration-framework/blob/master/packages/core/tools/ci.sh getting this documented is important and we will definitely welcome PRs, but as Peter also mentions our small team is right now focused on getting to the to-be arch (which then will likely require new setup docs)

JHamilton (Tue, 07 Jan 2020 00:20:45 GMT):
sorry don't want to be discouraging on contributing, there are many good first issues tagged that would not require the full setup.

JHamilton (Tue, 07 Jan 2020 00:21:21 GMT):
even just submitting an issue on what you would want to see in setup is appreciated. thanks again for your time!

adityasingh177 (Tue, 07 Jan 2020 06:39:35 GMT):
Thanks @peter_somogyvari @JHamilton

adityasingh177 (Tue, 07 Jan 2020 06:42:19 GMT):
That will be a good start for me

Abhishek2700 (Tue, 07 Jan 2020 07:24:56 GMT):

Clipboard - January 7, 2020 12:50 PM

peter_somogyvari (Tue, 07 Jan 2020 07:41:12 GMT):
Can you try running the CI script (if not already)? That's the current gold standard for verifying issues. `./packages/core/tools/ci.sh` If that script fails then something is very likely to be causing it specific to your machine. If it succeeds, then please double check the steps for running the scenarios just by reading the commands in the ci.sh script.

Abhishek2700 (Tue, 07 Jan 2020 07:46:22 GMT):
Isn't it to setup fabric and quorum blockchain?? I wanted to try asset-tranfer between corda and fabric. I am following the doc at https://github.com/hyperledger-labs/blockchain-integration-framework/blob/master/docs/tutorials/simple-asset-transfer.md

Abhishek2700 (Tue, 07 Jan 2020 07:47:17 GMT):
The commands here in this doc seem to be the same as in the ci.sh script.

Abhishek2700 (Tue, 07 Jan 2020 10:24:54 GMT):
@glotov , could you please help me with this ?

glotov (Tue, 07 Jan 2020 10:28:14 GMT):
hi, you need to run all commands from `ci.sh` except those that mention Quorum. And also change `nocorda` to `noquorum`.

peter_somogyvari (Tue, 07 Jan 2020 18:30:37 GMT):
@Abhishek2700 The CI script does basically the same thing as the simple asset

peter_somogyvari (Tue, 07 Jan 2020 18:30:37 GMT):
@Abhishek2700 The CI script does basically the same thing as the simple asset transfer example, but also includes corda, which you can exlude as Denis was saying, but you don't have to unless you are RAM bound (you need 16GB RAM freely available on your system to run the full CI with Corda)

JHamilton (Tue, 07 Jan 2020 21:21:30 GMT):
FYI we have moved to a new standing time for weekly contributors forum. looking forward to seeing you there! https://lists.hyperledger.org/g/labs/viewevent?repeatid=21921&eventid=680316&calstart=2020-01-13 https://lists.hyperledger.org/g/labs/calendar?calstart=2020-01-13

Abhishek2700 (Wed, 08 Jan 2020 06:05:20 GMT):
Thanks @glotov and @peter_somogyvari for your help. I will try runniing ci.sh with better hardware

Abhishek2700 (Wed, 08 Jan 2020 06:15:14 GMT):

Clipboard - January 8, 2020 11:41 AM

Abhishek2700 (Wed, 08 Jan 2020 10:41:01 GMT):
@peter_somogyvari , @glotov , any thoughts on this ??

peter_somogyvari (Wed, 08 Jan 2020 17:27:55 GMT):
@Abhishek2700 It's part of the ChainCode written for the example: https://github.com/hyperledger-labs/blockchain-integration-framework/blob/eaa5a3796e6cfd59fd24fe55454491b7cea2a6b6/packages/core/examples/simple-asset-transfer/fabric/contracts/src/mycc/mycc.go#L161

glotov (Wed, 08 Jan 2020 19:54:40 GMT):
`verifyAndCreate` is here: https://github.com/hyperledger-labs/blockchain-integration-framework/blob/master/packages/core/examples/simple-asset-transfer/fabric/contracts/src/mycc/mycc.go#L161

Abhishek2700 (Fri, 10 Jan 2020 08:16:17 GMT):
thanks @peter_somogyvari and @glotov , got it

Abhishek2700 (Fri, 10 Jan 2020 08:16:37 GMT):
@peter_somogyvari , @glotov

Abhishek2700 (Fri, 10 Jan 2020 08:21:40 GMT):
@glotov , @peter_somogyvari . I also wanted to ask about the working of the validators. 1.) Are they the same as the peer nodes or are they different nodes specifically made for validating requests for cross blockchain requests or are their functionality defined by the chaincode . 2.) How many peer nodes do we need? The simple-asset-transfer example here shows 4 peers and 4 validators. Do we always have to have the same number of validators as the peer nodes? What is the minimum number of recommended validators required for a cross blockchain asset transfer?

Abhishek2700 (Fri, 10 Jan 2020 11:21:20 GMT):

Clipboard - January 10, 2020 4:47 PM

JHamilton (Fri, 10 Jan 2020 22:00:21 GMT):
hey folks, happy Friday & hope your week is wrapping up. just a heads up that the contributors forum the week of the 13th has shifted out a few days. https://lists.hyperledger.org/g/labs/viewevent?repeatid=21921&eventid=680316&calstart=2020-01-15

JHamilton (Fri, 10 Jan 2020 22:19:45 GMT):
Proposed agenda; please respond if other topics of interest! 1) confirm standing time going forward across time zones 2) discuss closing the design principles "request for comment" period and publishing them from the google drive to Github https://docs.google.com/document/d/1oCF7q_or7EWlVEmCMYuGU3ksKrNjHf07pSTrviRfktk/edit?pli=1 3) identify next steps in detailing design

Abhishek2700 (Mon, 13 Jan 2020 06:08:51 GMT):

Clipboard - January 13, 2020 11:34 AM

Abhishek2700 (Mon, 13 Jan 2020 06:09:59 GMT):
@glotov , @peter_somogyvari , please advice on this. Any method that is using these urls and sending requests to them are handled by the chaincodes/smart contract right ?

Abhishek2700 (Mon, 13 Jan 2020 06:25:40 GMT):
It seems everything is done my chaincode/smart contract right. It is the chaincode code that creates , gets , and coppy assets , verify multisigs and get the signatures right ??

Abhishek2700 (Mon, 13 Jan 2020 12:05:32 GMT):
Could you all also please tell me if we need a validator for each peer node in any DLT when we try simple-asset-transfer ??

Abhishek2700 (Tue, 14 Jan 2020 10:06:24 GMT):

Clipboard - January 14, 2020 3:26 PM

Abhishek2700 (Tue, 14 Jan 2020 11:28:28 GMT):

Clipboard - January 14, 2020 4:57 PM

Abhishek2700 (Tue, 14 Jan 2020 11:31:51 GMT):
I figured out that the code for verifying signatures by fabric connector is mentioned in the chaincode. But what about asking for signatures by corda in this example ?? Its code just shows that we send a request to the validator node of the corda to ask for signatures. Could someone tell me where is the code written for the validators and how do they process these requests for signatures. Is it mentioned in some chaincode as well ?

Abhishek2700 (Wed, 15 Jan 2020 04:38:21 GMT):
@peter_somogyvari , @JHamilton , anyone ?? could you please help me in knowing how the validators are working while simple-asset-transfer ?? For example in transferring assets from corda to fabric , when corda assets have been created and locked , then it asks for signatures from cordaValidators who verify that the assets have been locked. How does it do that exactly ? Where is the code for the validation written ?? What i found in the code is only us sending requests to one of the validators and we get the signature back.

Abhishek2700 (Wed, 15 Jan 2020 04:38:21 GMT):
@peter_somogyvari , @JHamilton , anyone ?? could you please help me in knowing how the validators are working while simple-asset-transfer ?? For example in transferring assets from corda to fabric , when corda assets have been created and locked , then it asks for signatures from cordaValidators who verify that the assets have been locked and then provide their signatures as a proof . How does it do that exactly ? Where is the code for the validation written ?? What i found in the code is only us sending requests to one of the validators and we get the signature back.

Abhishek2700 (Wed, 15 Jan 2020 09:53:53 GMT):
@peter_somogyvari , please reply when you get the time. I need to clear few doubts regarding validators, thanks

peter_somogyvari (Wed, 15 Jan 2020 15:36:07 GMT):
@Abhishek2700 1 They are specifically made for validating, so they are different from peer nodes. 2 As many as you need for HA (assuming that you do). The number of peer nodes are up to the network operator and depends on the chain you are deploying and has no real relation to the number of validator nodes. Minimum recommended validator node count for now: 3.

peter_somogyvari (Wed, 15 Jan 2020 15:39:47 GMT):
@Abhishek2700 The client communicates with only one validator but that validator will make sure that the rest of the validators have signed off internally before giving the go-ahead.

peter_somogyvari (Wed, 15 Jan 2020 15:45:56 GMT):
@Abhishek2700 That's because the design isn't finalized yet so methods may be moved around to core or out of core. > All these methods are using the chaincode to create and get the assets right ? Since we can interact with the blockchain only using chaincodes right ? Yes, correct.

peter_somogyvari (Thu, 16 Jan 2020 01:40:59 GMT):
@Abhishek2700 Yes, that's correct.

peter_somogyvari (Thu, 16 Jan 2020 01:43:23 GMT):
@Abhishek2700 No, the two numbers don't constrain each other.

peter_somogyvari (Thu, 16 Jan 2020 01:44:51 GMT):
@Abhishek2700 They should be in the logs of the DLT node running the chain code container, maybe double check the log levels? We reduced them recently to increase performance by default

JHamilton (Thu, 16 Jan 2020 03:04:19 GMT):
hello! we are on the bridge and about to get started

JHamilton (Thu, 16 Jan 2020 04:12:21 GMT):
Key outcomes I captured, please respond if additions / corrections: 1) Aligned on standing time fortnightly from Mon 27th US 9pm CT US / Tues 8:30 am India, noon Japan, 2pm Australia 2) Goal to close design principles "RFC" by Mon 20th; please use Rocket chat on any discussion points; afterwards design principles will be posted to Github. While these will guide us in the next phase of work, we should be prepared to receive and digest further feedback, including changes 3) We will collaboratively work on design using Github, including organizing tasks in GH project and design content on GH wiki / markdown. Peter had started on a copy https://github.com/petermetz/blockchain-integration-framework/blob/docs/peter.somogyvari/whitepaper/docs/whitepaper/whitepaper.md and Fujitsu will share their updates post refinement. We want to get these merged into one working version available online to all where we can iteratively refine 4) IBM paper https://arxiv.org/abs/1911.01064 which IBM will present in future session

Abhishek2700 (Thu, 16 Jan 2020 05:40:35 GMT):
@peter_somogyvari , thanks for the help, really appreciate it.

Abhishek2700 (Thu, 16 Jan 2020 06:07:52 GMT):
I just need to confirm a few more things if you don't mind. I was checking docker logs for the vaidators to see how they are working. Correct me if i am wrong, according to me here is how it works. For this transfer suppose corda is sending assets to fabric. 1.) Corda creates and locks asset. 2.) Then it asks corda valdators for the confirmations for this locking of assets by passing in assetId and destination ledger for this asset. 3.) There are 4 validators which are always competing in an election. At one time among validators , there is one leader and 3 followers. Whenever the first validator gets the signing request , it notifies the leader which uses the getAsset method and the assetId passed in to the validator to check that the transsaction is valid and that the given asset is locked. Then it gives its approval by signing the message which contains the asset details. 4.) Then the leader asks the follower validator nodes to check that the asset is locked and further sign the message. Then each follower node individually checks that the asset is locked by using the getAsset method and sign the message and gives it to the leader node for acknowledgement. 5.) Then the leader node gets all the signatures as a mark of approval and when we get these signatures, we give it to the fabric connector which verifies these signatures by using the verify method in the chaincode. RIGHT ?? What i want to know is this (i) IN step 3 above , when the leader node uses the getAsset chaincode method to see if the asset is locked. What if i need to call some other method for validating the request the validator gets? Where do i specify it ? Is it something that we set while setting up the validator nodes ?? I just need to know how do i change how the request given to the validator node is processed by the validator node because you said that the validator nodes are specifically made for validation. Where do i need to specify the new validation process if i need to change the given default behaviour it has.? (ii) What happens if in step 4 , if a follower validator becomes corrupt and is not able to sign the request? Does the asset transfer still go through if the majority of the validator nodes validates the request? (iii) What happens if in scenario (ii) above , majority of the validator node gets corrupt and is unable to validate the transfer? Does the asset transfer process stop right there ? Won’t it be a problem , since now the asset has been created and locked in the sender chain but not recreated in the receiving chain .

Abhishek2700 (Thu, 16 Jan 2020 06:07:52 GMT):
@peter_somogyvari ,I just need to confirm a few more things if you don't mind. I was checking docker logs for the vaidators to see how they are working. Correct me if i am wrong, according to me here is how it works. For this transfer suppose corda is sending assets to fabric. 1.) Corda creates and locks asset. 2.) Then it asks corda valdators for the confirmations for this locking of assets by passing in assetId and destination ledger for this asset. 3.) There are 4 validators which are always competing in an election. At one time among validators , there is one leader and 3 followers. Whenever the first validator gets the signing request , it notifies the leader which uses the getAsset method and the assetId passed in to the validator to check that the transsaction is valid and that the given asset is locked. Then it gives its approval by signing the message which contains the asset details. 4.) Then the leader asks the follower validator nodes to check that the asset is locked and further sign the message. Then each follower node individually checks that the asset is locked by using the getAsset method and sign the message and gives it to the leader node for acknowledgement. 5.) Then the leader node gets all the signatures as a mark of approval and when we get these signatures, we give it to the fabric connector which verifies these signatures by using the verify method in the chaincode. RIGHT ?? What i want to know is this (i) IN step 3 above , when the leader node uses the getAsset chaincode method to see if the asset is locked. What if i need to call some other method for validating the request the validator gets? Where do i specify it ? Is it something that we set while setting up the validator nodes ?? I just need to know how do i change how the request given to the validator node is processed by the validator node because you said that the validator nodes are specifically made for validation. Where do i need to specify the new validation process if i need to change the given default behaviour it has.? (ii) What happens if in step 4 , if a follower validator becomes corrupt and is not able to sign the request? Does the asset transfer still go through if the majority of the validator nodes validates the request? (iii) What happens if in scenario (ii) above , majority of the validator node gets corrupt and is unable to validate the transfer? Does the asset transfer process stop right there ? Won’t it be a problem , since now the asset has been created and locked in the sender chain but not recreated in the receiving chain .

Abhishek2700 (Thu, 16 Jan 2020 06:07:52 GMT):
@peter_somogyvari ,I just need to confirm a few more things if you don't mind. I was checking docker logs for the vaidators to see how they are working. Correct me if i am wrong, according to me here is how it works. For this transfer suppose corda is sending assets to fabric. 1.) Corda creates and locks asset. 2.) Then it asks corda valdators for the confirmations for this locking of assets by passing in assetId and destination ledger for this asset. 3.) There are 4 validators which are always competing in an election. At one time among validators , there is one leader and 3 followers. Whenever the first validator gets the signing request , it notifies the leader which uses the getAsset method and the assetId passed in to the validator to check that the transsaction is valid and that the given asset is locked. Then it gives its approval by signing the message which contains the asset details. 4.) Then the leader asks the follower validator nodes to check that the asset is locked and further sign the message. Then each follower node individually checks that the asset is locked by using the getAsset method and sign the message and gives it to the leader node for acknowledgement. 5.) Then the leader node gets all the signatures as a mark of approval and when we get these signatures, we give it to the fabric connector which verifies these signatures by using the verify method in the chaincode. RIGHT ?? What i want to know is this (i) IN step 3 above , when the leader node uses the getAsset chaincode method to see if the asset is locked. What if i need to call some other method for validating the request the validator gets? Where do i specify it ? Is it something that we set while setting up the validator nodes ?? I just need to know how do i change how the request given to the validator node is processed by the validator node because you said that the validator nodes are specifically made for validation. Where do i need to specify the new validation process if i need to change the given default behaviour it has.? Because , right now , it just uses a docker imagee to run the validators. (ii) What happens if in step 4 , if a follower validator becomes corrupt and is not able to sign the request? Does the asset transfer still go through if the majority of the validator nodes validates the request? (iii) What happens if in scenario (ii) above , majority of the validator node gets corrupt and is unable to validate the transfer? Does the asset transfer process stop right there ? Won’t it be a problem , since now the asset has been created and locked in the sender chain but not recreated in the receiving chain .

vramaiitkgp (Thu, 16 Jan 2020 13:49:10 GMT):
Has joined the channel.

peter_somogyvari (Fri, 17 Jan 2020 00:56:00 GMT):
@Abhishek2700 1-5: Sounds correct, yes. (i) Right now we are still in the design phase with the plugin architecture so the only way at the moment would be sub-class (or write from scratch) your own connector implementation for the given ledger. I'm literally working on the plugin architecture right now for making this easier to customize as we speak so would love to hear what is the exact use case you are evaluating BIF for! (or as much as you can share). (ii) Transfer should still go through as long as there is at least one trusted validator alive, but I believe the current code to be buggy when it comes to this: a validator node being dead incorrectly causes the verification to fail. Not tested this just based on what I read in the code it looks like it doesn't tolerate any validators being down. (iii) Per design the transfer should succeed as long as at least one validator is alive. We don't yet have a rollback safety mecnanism in case all of the validators went down so the transaction would stop there with current codebase, but the assets are also can be unlocked so eventual consistency can be guaranteed with some improvements (that are coming). Locking an asset in our current contracts is NOT irreversible the way sending coins to a dead address on one of the permissionless ledgers is (locking is reversible by the contract itself). The design idea here is to have a persistent transaction state storage for BIF that survives downtime. Going back to the plugin architecture again: said transaction storage backend should be pluggable so that if you deploy BIF you can pick what you prefer (maybe you want some p2p storage, or just pay a cloud provider to have an RDBMS do synchronous replication to different regions)

Abhishek2700 (Fri, 17 Jan 2020 11:47:07 GMT):
@peter_somogyvari , thanks a lot , really appreciate it . I got the file Validator.js at package/core/src where the getAsset method is being called to validate the transaction and then it is using the response from that method which is being signed. THis was the thing i was looking for , now if i wanted to change the criteria for validation , i would just have to make some changes here . Thanks

JHamilton (Fri, 17 Jan 2020 17:36:20 GMT):
dear community, regarding the new contributors sessions, i made the judgement call to start from Jan 20th US / Jan 21st eastern time zones. this is because i want us to stick to our goal of closing design principles by Mon 20th and also because Peter is drafting a spec for the plugin archihtecture (whats in core vs what is a plugin, as well as interface and perhaps some other goodness if he is inspired ;-) ). so want to promptly get your feedback! please also bring ideas about how we can parallelize the design, with different people owning different modules / capabilities. thanks and have a great weekend! https://lists.hyperledger.org/g/labs/viewevent?repeatid=21083&eventid=642131&calstart=2020-01-20

adityasingh177 (Fri, 17 Jan 2020 17:37:16 GMT):
Thanks @JHamilton

peter_somogyvari (Fri, 17 Jan 2020 23:17:10 GMT):
Glad I was able to help @Abhishek2700

Abhishek2700 (Mon, 20 Jan 2020 04:23:50 GMT):
Hi @peter_somogyvari , i have a few more doubts regarding the validators. 1.) The validators present in the example are running in dockers on the same server, will the code change if the validators are different nodes present on different servers in a real life example or do i have to just change the ips in the code for the validators to work. 2.) All the validators right now use etcd1,etcd2,etcd3 as services when they run in dockers. I looked into it and its a key value store. So are they being used for database for the that we are setting in the chaincode or are they just being used for the election purpose. 3.) If i have a few validator nodes that are set up on different servers, will the etcd services be running on each validator or will there be a central server where we will run the etcd sservices and it will be shared by all validator nodes/servers.

Abhishek2700 (Mon, 20 Jan 2020 04:23:50 GMT):
Hi @peter_somogyvari , i have a few more doubts regarding the validators. 1.) The validators present in the example are running in dockers on the same server, will the code change if the validators are different nodes present on different servers in a real life example or do i have to just change the IP's in the code for the validators to work. 2.) All the validators right now use etcd1,etcd2,etcd3 as services when they run in dockers. I looked into it and its a key value store. So are they being used for database for the that we are setting in the chaincode or are they just being used for the election purpose. 3.) If i have a few validator nodes that are set up on different servers, will the etcd services be running on each validator or will there be a central server where we will run the etcd sservices and it will be shared by all validator nodes/servers.

Abhishek2700 (Mon, 20 Jan 2020 04:23:50 GMT):
Hi @peter_somogyvari , i have a few more doubts regarding the validators. 1.) The validators present in the example are running in dockers on the same server, will the code change if the validators are different nodes present on different servers in a real life example or do i have to just change the IP's in the code for the validators to work. 2.) All the validators right now use etcd1,etcd2,etcd3 as services when they run in dockers. I looked into it and its a key value store. So are they being used for database for the states we are setting in the chaincode or are they just being used for the election purpose. 3.) If i have a few validator nodes that are set up on different servers, will the etcd services be running on each validator or will there be a central server where we will run the etcd sservices and it will be shared by all validator nodes/servers.

takeutak (Mon, 20 Jan 2020 11:11:49 GMT):
[design principles] Hi, everyone! I make a new proposal of design principles based on the current version. I would like to explain about it on tomorrow phone meeting. The proposal is as the attached slide. (c.f.) the current version of design principles: https://docs.google.com/document/d/1oCF7q_or7EWlVEmCMYuGU3ksKrNjHf07pSTrviRfktk

takeutak (Mon, 20 Jan 2020 11:12:27 GMT):

Fujitsu_proposal_merged_plan_to_HL-labs-BIF_2020-01-21.pdf

takeutak (Mon, 20 Jan 2020 11:33:07 GMT):

Fujitsu_proposal_design_principle_to_HL-labs-BIF_2020-01-21.pdf

JHamilton (Mon, 20 Jan 2020 11:35:39 GMT):
thanks for the proactivity Takeuchi-san; will look forward to discussing in +14 hours :)

adityasingh177 (Mon, 20 Jan 2020 16:15:11 GMT):
Thanks

peter_somogyvari (Tue, 21 Jan 2020 00:35:12 GMT):
@Abhishek2700 1.) As the operator of a cluster you are responsible for making sure that there is network connectivity between the nodes. Whether it's a software defined networking environment (like what Docker Compose gives us) or a physical network it doesn't matter: as long as there is connectivity to the addresses/hosts you supply in the config, it should work. There is a caveat with cross data center or cross region deployments that I noted down here for reference: https://github.com/hyperledger-labs/blockchain-integration-framework/issues/63 2.) They are strictly just for leader election at the moment. In the future (long term) we intend to re-design the system so that leader election for validators is either a) not needed at all or b) it is embedded in the validator codebase itself (e.g. a Typescript Raft algorithm implementation) 3.) It's up to the person who performs the installation. Etcd servers don't need to be on the same machine as the validators and their numbers don't need to match the number of validators either. Etcd works best when it has an odd number of nodes in a cluster.

peter_somogyvari (Tue, 21 Jan 2020 02:43:22 GMT):
@takeutak Thank you very much! I think the proposed new structure is great and I incorporated the thing in section 3 of the whitepaper document here, if you happen to have time please take a look at the pull request :-) https://github.com/hyperledger-labs/blockchain-integration-framework/pull/98

JHamilton (Tue, 21 Jan 2020 03:06:23 GMT):
hey @dileban @micbowman & any others that are interested to join. we are a few minutes past the meeting start and going to get started. would welcome your participation if you are able to join!

JHamilton (Tue, 21 Jan 2020 03:06:23 GMT):
hey @dileban @MicBowman & any others that are interested to join. we are a few minutes past the meeting start and going to get started. would welcome your participation if you are able to join!

JHamilton (Tue, 21 Jan 2020 04:00:04 GMT):
key outcomes i captured @hartm @peter_somogyvari @sfuji822 @takeutak; please respond with additions / updates: 1. aligned and agreed with the Fujitsu feedback on design principles & splitting. @takeutak will update the google docs 2. introduced draft whitepaper & seeking feedback via PR https://github.com/hyperledger-labs/blockchain-integration-framework/pull/98 agreed to provide feedback in the PR; things that can be agreed to async will be captured; for any open discussion points we will cover in next meeting in a fortnight. if anyone else would like to be added as reviewer please ping here.

peter_somogyvari (Tue, 21 Jan 2020 18:29:51 GMT):
FYI: Whitepaper PR had a minor update where I fixed a few syntax errors, added a couple roles to the terminology section (and made the use-cases consistent with it by changing `company` to `organization`. Commit: https://github.com/hyperledger-labs/blockchain-integration-framework/pull/98/commits/4465b03fe4f489e3fbdcb73d3640342739e49ac8

Abhishek2700 (Wed, 22 Jan 2020 06:27:29 GMT):
Thanks @peter_somogyvari , got it

Abhishek2700 (Wed, 22 Jan 2020 06:30:18 GMT):
What i want to do now is to remove the election functionality among validator nodes and make the validation process sequential. 1.) I Have tried removing the follower and leader properties from the yml file of the federattion. 2.) I have also tried stopping the election process by commenting out this.setupLeaderElections();

Abhishek2700 (Wed, 22 Jan 2020 06:32:07 GMT):
But when i rebuild the federation image and restart the fabric validators , i still see the election happening in the fabric validator node logs

Abhishek2700 (Wed, 22 Jan 2020 06:34:15 GMT):
I just want to turn off the election process and just want to request public keys and heartbeat , sequential . So if i want to ask for a public key of a validator , i just wantto create a socket connection with it and send a request and based on the request type , i want to send the response. Could you please help me with this

Abhishek2700 (Wed, 22 Jan 2020 07:49:48 GMT):
I just tried removing the etcd service and ow its not running and i also stopped the setupLeaderElections method to be invoked in the validator.js file. But the election is still going on. Each validator node is tryingto be the leader but since etcd service are not working , we are getting an error there. What i want to do is stop the parallel validation altogether.

Abhishek2700 (Wed, 22 Jan 2020 10:00:39 GMT):
I did try some more things to remove the etcd dependency of the validators but the logs still say that the validators require etcd . So my question is , Does the validator nodes right now require the etcd service internally or is it optional and we can remove it? If it is optional , can you please tell me what changes do i have to make to make it work without etcd? Also , whatever changes i am making in the Validator.js file. It is not being reflected in the logs for the validators. I also restarted the fabric peer nodes and remade the image for the validators. It is still not showing the additional console.log line i am putting in the file Validator.js at packages/core/src/Validator.js . I also tried stopping the election in the constructor but it is still not working. Is there anything i am missing?

MicBowman (Wed, 22 Jan 2020 17:11:22 GMT):
sorry @JHamilton i still had the meeting on my calendar for wednesdays... will adjust

JHamilton (Wed, 22 Jan 2020 17:17:34 GMT):
no worries and thank you for your continued interest!

JHamilton (Thu, 23 Jan 2020 04:10:17 GMT):
@Abhishek2700 to clarify, right now the leader election is mandatory, not optional. we do have a desire to make this optional in a future version so it will be helpful if you create a feature request to describe how you would like this to work and we can have this context in a ticket https://github.com/hyperledger-labs/blockchain-integration-framework/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=

JHamilton (Thu, 23 Jan 2020 04:12:06 GMT):
it also looks like you are trying to modify the code but the changes are not making it into the validator node container... perhaps an NPM or docker caching issue? can you explain a bit the commands you are using to update?

Abhishek2700 (Thu, 23 Jan 2020 04:21:04 GMT):
@JHamilton , i wanted to remove the election process and confirmed from here that etcd is being used for this. So tried to remove etcd from the yml file that is being used for starting the federation servers. This starts the dockers but the logs say that it needs the etcd functionality. SO i tried stopping the election in the Validation constructor that according to me is being used to initialise the validators. Then i restarted the validators but the logs still say that the election is still going on and the nodes are trying to be the leader but since the etcd service are removed from the yml file , it cannot find it and after 25 attempts to be the leader , its logs gives error that etcd hosts not found. I also tried rebuilding the image after i made the changes in the yml file . In fact i restarted the whole network and restarted the whole thing but the election is still going on. So what i wanted to confirm was if the elction process ca be stopped for now

JHamilton (Thu, 23 Jan 2020 04:30:35 GMT):
i'll let @peter_somogyvari chime in with more details, but my guidance is we take an approach to define how we want it election feature to work (e.g. configuration option) and the use that to drive a solution. i'm still learning the ropes of working in open community but would like to do that in the context of a GH ticket so it's there for posterity. so would appreciate your help in defining via feature request ticket. what do you think?

JHamilton (Thu, 23 Jan 2020 04:30:35 GMT):
i'll let @peter_somogyvari chime in with more details, but my guidance is we take an approach to define how we want leader election feature to work (e.g. configuration option) and the use that to drive a solution. i'm still learning the ropes of working in open community but would like to do that in the context of a GH ticket so it's there for posterity. so would appreciate your help in defining via feature request ticket. what do you think?

Abhishek2700 (Thu, 23 Jan 2020 07:19:27 GMT):
@JHamilton , i have raised a ticket and described the functionality i want. Thanks for the support

JHamilton (Thu, 23 Jan 2020 13:17:29 GMT):
looks great, thank you!

JHamilton (Thu, 23 Jan 2020 13:17:29 GMT):
looks great, thank you! will be in touch

sfuji822 (Fri, 24 Jan 2020 13:17:59 GMT):
whitepaper

sfuji822 (Fri, 24 Jan 2020 13:18:05 GMT):
whitepaper

sigma67 (Tue, 28 Jan 2020 10:29:13 GMT):
Has joined the channel.

takeutak (Fri, 31 Jan 2020 08:29:54 GMT):
Hi everyone, This is a feedback to the Whitepaper draft which is found at pull-request: https://github.com/hyperledger-labs/blockchain-integration-framework/pull/98 . I prepared my comments in the attached presentation, and I will add some explanations at next conference call. I'd like to hear other participants' opinions on the meeting. Best regards, Takuma

takeutak (Fri, 31 Jan 2020 08:30:16 GMT):

Takeuchi_Review_to_BIF_whitepaper_v2020-01-31.pdf

takeutak (Fri, 31 Jan 2020 08:32:28 GMT):

Takeuchi_Review_to_BIF_whitepaper_v2020-01-31.pdf

JHamilton (Fri, 31 Jan 2020 16:59:16 GMT):
Thanks Takuma! will review and look forward to discussion

peter_somogyvari (Fri, 31 Jan 2020 17:27:09 GMT):
@takeutak Thank you very much for taking the time! I'll go through this ASAP!

JHamilton (Fri, 31 Jan 2020 22:51:06 GMT):
dear #blockchain-integration-framework our next contributors session is coming up! https://lists.hyperledger.org/g/labs/viewevent?repeatid=21921&eventid=691706&calstart=2020-02-03 the main item for agenda is to discuss any feedback on the white paper and any possibility to "divide & conquer" on to-be arch. looking forward to discussing with you! are there other items of agenda you would like to cover?

takeutak (Mon, 03 Feb 2020 09:17:38 GMT):
Hi, everyone! I prepare a meeting record for BIF meeting on January 21, 2020 as the attached file. (c.f.) Meeting log on December 16, 2019: https://wiki.hyperledger.org/display/labs/Blockchain+Integration+Framework+-+16+December+2019 Would you mind if I share the meeting record on Hypeledger labs page like the above URL? I'd like to hear other paticipants' opinions on the tomorrow phone meeting. BR,

takeutak (Mon, 03 Feb 2020 09:17:46 GMT):

2020-01-21_BIF_meeting_record.txt

dushyantbehl (Mon, 03 Feb 2020 11:40:09 GMT):
Has joined the channel.

JHamilton (Mon, 03 Feb 2020 17:56:23 GMT):
Hey Takuma, that's a great idea to record to the wiki so that they are more easily organized and located. Maybe will be better if they are all rolled under one page ( i made an example like this with the Dec 16th instance), take a look and see if it works

dileban (Mon, 03 Feb 2020 23:30:17 GMT):
Has joined the channel.

JHamilton (Tue, 04 Feb 2020 04:18:05 GMT):
Key outcomes from I captured are as follows; please respond if anything key I missed. Will try to get in the habit of scribing these into the Wiki. Just very late local time when we finish! 1. No news on project proposal. Hart please respond if anything the group should be aware of 2. Discussed Fujitsu feedback that Peter will start applying. Requested that going forward Fujitsu team provide feedback directly on PR and that if any use case scope they could own (e.g. non-financial exchange). 3. Reviewed Hart's PR feedback and plan to address 4. Confirmed intention to setup a meal or drinks at the Hyperledger Global Forum (Shingo, Takuma, Hart, Mic, & Peter will be intention) 5. Given the contributors session on Mar 2 will be during contributors forum, will move that session up by a week (Feb 24 same time)

peter_somogyvari (Fri, 07 Feb 2020 06:27:16 GMT):
@takeutak I updated section 1 and 2 as per the proposal. Do you think you could give a shot to section 3? I'm also happy to work together on it more closely. Here are the relevant commits for me updating the first two sections as per the proposal: https://github.com/petermetz/blockchain-integration-framework/commit/e01c1f47159d8c5b05a392ebc1d51147a7b5666b https://github.com/petermetz/blockchain-integration-framework/commit/2d7e7f5c2651e7559bc829904ae7294dc9c0adf9

JHamilton (Mon, 10 Feb 2020 20:23:18 GMT):
dear BIF community, please note that our Mar 2 / 3 contributors session has been bumped up to same time on Feb 24 / 25 to accommodate the HGF week of Mar 2 https://lists.hyperledger.org/g/labs/viewevent?repeatid=21921&eventid=695068&calstart=2020-02-24

peter_somogyvari (Tue, 11 Feb 2020 21:46:22 GMT):
NodeJS 10 support just landed. 🎉🎉🎉

JHamilton (Wed, 12 Feb 2020 18:55:39 GMT):
@takeutak any feedback or update you can give before Monday session would be much appreciated! open feedback request for the rest of the community too :D thank you!

takeutak (Tue, 18 Feb 2020 01:30:04 GMT):
Hi everyone! This is a feedback to the Whitepaper draft which is found at pull-request: https://github.com/hyperledger-labs/blockchain-integration-framework/pull/98 . (especially, topics about use-cases and interworking patterns) I prepared my comments in the attached presentation, and I will add some explanations at next conference call. I'd like to hear other participants' opinions on the meeting. Best regards, Takuma

takeutak (Tue, 18 Feb 2020 01:30:26 GMT):

Takeuchi_Review_to_BIF_whitepaper_v2020-02-17.pdf

takeutak (Tue, 18 Feb 2020 01:31:39 GMT):
My pull request on WhitePaper is the following: https://github.com/petermetz/blockchain-integration-framework/pull/1/commits/621d60ca4117703a43c48bb792feb872fbc27f98

takeutak (Tue, 18 Feb 2020 01:31:39 GMT):
My pull request on WhitePaper is the following: https://github.com/petermetz/blockchain-integration-framework/pull/1 (diff): https://github.com/petermetz/blockchain-integration-framework/pull/1/commits/621d60ca4117703a43c48bb792feb872fbc27f98

sfuji822 (Tue, 18 Feb 2020 02:38:26 GMT):

CommentsOnWP20200218FUJITSU.pdf

JHamilton (Tue, 18 Feb 2020 04:09:40 GMT):
Key takeaways from today's session Feb 17 / 18th; please clarify anything I have missed / misstated: * Whitepaper feedback from @sfuji822 & @takeutak will be incorporated / merged * Then whitepaper will be published to master as "WIP" with open request for feedback * Request to divide & conquer as much as possible over next week * @hartm will start drafting project proposal, in order to start getting TSC / community feedback

hartm (Tue, 18 Feb 2020 17:11:24 GMT):
I'm starting the proposal. If you'd like, you can follow my progress here:

hartm (Tue, 18 Feb 2020 17:11:27 GMT):
https://docs.google.com/document/d/1kxylkfVKG_zdNfuzhrmhnYAM_eROwLsoLgIp3XjKNr0/edit?usp=sharing

hartm (Tue, 18 Feb 2020 17:11:46 GMT):
Note that this is obviously incomplete, but feel free to follow my progress and comment if you like.

ajayjadhav (Wed, 19 Feb 2020 08:17:39 GMT):
Has joined the channel.

tkuhrt (Wed, 19 Feb 2020 13:58:26 GMT):
Hart, you probably already know this, but there is a template on the wiki and a place for proposing new projects : https://wiki.hyperledger.org/pages/createpage-entervariables.action?templateId=3112984&spaceKey=HYP&newSpaceKey=HYP&fromPageId=2392298

hartm (Wed, 19 Feb 2020 14:46:47 GMT):
@tkuhrt Yep! My google doc is based on that. I figure it's easier for everyone to comment/edit in google docs for a while before we move to github.

peter_somogyvari (Wed, 19 Feb 2020 23:57:38 GMT):
Just created a new draft PR on the whitepaper: added a list of people with names and email addresses who helped making it this far. If anybody feels like they don't want to be on that list please let me know (or just change it directly). And of course if I forgot anyone, apologies and please let me know or just add yourselves (please keep the alphabetical ordering in place) I'll wait a few days to make sure that everyone gets a chance to look at it. https://github.com/hyperledger-labs/blockchain-integration-framework/pull/112 ``` docs(whitepaper): pdf toolchain, contributors Also fixes that were necessary to be cross-compatible between GitHub markdown, HTML and PDF. Pandoc is used to generate HTML from markdown WKHTMLtoPDF is used to generated PDF from the HTML that Pandoc produces. To generate html and pdf files (on an Ubuntu 18.04 system) run `make configure pdf` while being in the docs/whitepaper/ directory Also: fixed typo in TOC that had the old section title for one of the use-cases Signed-off-by: Peter Somogyvari ```

sfuji822 (Fri, 21 Feb 2020 23:06:13 GMT):
thanks Peter. We will keep contribute on this to foam group consensus.

sfuji822 (Fri, 21 Feb 2020 23:08:41 GMT):
[ ](https://chat.hyperledger.org/channel/blockchain-integration-framework?msg=n3wnGKWuKkwzmrygi)
MergedArch20200221.pdf

peter_somogyvari (Sat, 22 Feb 2020 04:32:47 GMT):
FYI: Opened a 'frequently asked questions' page on the github wiki of BIF, added a couple of entries => https://github.com/hyperledger-labs/blockchain-integration-framework/wiki/FAQ If you have ideas on what else should be added either add it or just throw me a message with the idea and I can hash it out there. Would be nice to have a bunch of answers there related to first time contributions, build system and other mechanical things that aren't design related but still help people consume the big picture faster.

takeutak (Tue, 25 Feb 2020 00:56:55 GMT):
Thanks Peter! I have a request. My correct name is "Takuma Takeuchi" ("Takuma" is my first name, "Takeuchi" is my family name). That is NOT "Takeuchi Takuma". Would you mind if you revise my name on the people list on the whitepaper draft?

peter_somogyvari (Tue, 25 Feb 2020 01:34:18 GMT):
Ooops, apologies! I'll correct the mistake. :-)

peter_somogyvari (Tue, 25 Feb 2020 01:50:34 GMT):
Fixed: https://github.com/hyperledger-labs/blockchain-integration-framework/pull/112/commits/d1718ca04ac08429792455cb982171f74a3840bc Apologies, once again!

takeutak (Tue, 25 Feb 2020 02:40:20 GMT):
Thanks!

peter_somogyvari (Tue, 25 Feb 2020 04:47:57 GMT):
Meeting minutes from our BIF contributors call on the 24th of February, 2020: -Everyone's excited about HGF - We'll have a technical collaboration session on Thursday at 9 AM or Friday at 9 AM - subject to room availability. Action item for Peter to book the room and notify the team of the outcome. - Hart will work on the project proposal, the plan is to be ready for HGF - We agreed that the latest whitepaper pull request is approved, action item for Peter to merge it in. - We'll start working on the code base integration after the architecture design is finished (currently some of the sections are still short on details or just outright 'TBD')

sfuji822 (Wed, 26 Feb 2020 11:14:45 GMT):
Question. Regarding HGF, should we reserve a table at BOF session ? or we can get another breakout room to draft white paper and proposal document ?

sfuji822 (Wed, 26 Feb 2020 11:14:45 GMT):
Hi Peter, thank you very much on hosting F2F meeting at Phoenix. I believe all of participants had great time with getting fruitful result. BTW, as par conversation on the meeting, can you request to give Takuma (takeutak) Maintainer privilege on BIF's github repository for starting actual coding ?

doomguy (Wed, 26 Feb 2020 13:05:21 GMT):
Has joined the channel.

doomguy (Wed, 26 Feb 2020 13:05:24 GMT):
Hello all. Could I use this framework to integrate HL Indy features into HL Fabric?

peter_somogyvari (Wed, 26 Feb 2020 17:38:52 GMT):
Hmm, what is the BOF session? I received confirmation that we can have the conference room in our hotel Thursday morning (right now it's open all day Thursday and Friday). Will send a map showing which one it is (Westin)

peter_somogyvari (Wed, 26 Feb 2020 17:40:03 GMT):

Screenshot (56).png

peter_somogyvari (Wed, 26 Feb 2020 17:48:29 GMT):
Hey @doomguy we are planning on adding support through plugins to as many ledgers as possible, but there isn't one for Indy as of right now. Also depends on your use-case so I'd love to hear what is it that you mean by integrating Indy features into Fabric because it could help influence our plugin design in a meaningful way.

peter_somogyvari (Wed, 26 Feb 2020 18:55:19 GMT):
Sorry, figured it out after my first coffee of the day kicked in. :-) You meant the BIF session of ours. I'm happy to stay at the convention center as well, but if we need it, I have the reservation for us in the Westin: ROOM 1: Cobalt Room, 12th floor: Large client meeting space for 30ppl. Boardroom-style set. Chairs, table, power, basic beverages (coffee, tea, water). Also asked them to provide a large screen monitor or projector so that we can collaborate without having to huddle over a single laptop.

doomguy (Thu, 27 Feb 2020 07:43:17 GMT):
Hi @peter_somogyvari ! I mean something like https://github.com/hyperledger-labs/cordentity OR https://github.com/Luxoft/cordentity These projects combine HL Indy ledger and decentralized identity features with Corda Platform. I'm looking for a similar thing but with Fabric instead of Corda.

peter_somogyvari (Thu, 27 Feb 2020 08:24:01 GMT):
Checked it out and the answer is a definite yes. Down the line, we want to be able to authenticate people with their identities on any indy ledger, sign attestations, etc. I do have to say that we are at the design phase, so it will take some time before it gets added, but my personal opinion is that it's a must have to support it in a very similar fashion (but through plugins of ours) as cordentity does.

peter_somogyvari (Thu, 27 Feb 2020 08:24:01 GMT):
@doomguy Checked it out and the answer is a definite yes. Down the line, we want to be able to authenticate people with their identities on any indy ledger, sign attestations, etc. I do have to say that we are at the design phase, so it will take some time before it gets added, but my personal opinion is that it's a must have to support it in a very similar fashion (but through plugins of ours) as cordentity does.

hartm (Sat, 29 Feb 2020 01:54:40 GMT):
I've put in some more work on a tentative project proposal document, and I think a first draft is ready. It's not perfect, but would probably suffice if we wanted to propose the BIF for project incubation status. Let me know what you think! https://docs.google.com/document/d/1kxylkfVKG_zdNfuzhrmhnYAM_eROwLsoLgIp3XjKNr0/edit?usp=sharing Thanks!

peter_somogyvari (Sun, 01 Mar 2020 07:00:48 GMT):
That dunking booth easter egg in the FAQ is awesome. :D

hartm (Sun, 01 Mar 2020 21:37:21 GMT):
It's a longstanding joke I put in pretty much all of my Hyperledger documents.

RahulDesai (Wed, 04 Mar 2020 11:25:12 GMT):
Has joined the channel.

RahulDesai (Wed, 04 Mar 2020 11:25:13 GMT):
Hi we are trying this article locally https://github.com/hyperledger-labs/blockchain-integration-framework/blob/master/docs/tutorials/simple-asset-transfer.md and facing an issue ERROR: pull access denied for federation/fabric-api, repository does not exist or may require 'docker login' can anyone please suggest.

peter_somogyvari (Wed, 04 Mar 2020 14:47:48 GMT):
@RahulDesai Which directory are you in and what command did you execute? Is it possible that you were not in the docs/whitepaper directory? I assume you were trying to build the pdf version of the whitepaper with the make task.

peter_somogyvari (Thu, 05 Mar 2020 06:31:10 GMT):
@RahulDesai Oh sorry, misread the question. You are in the examples folder. :-) Looked at it, we recently added an extra step to build the containers so you need to also run: npm run fabric:api:build Sorry I didn't catch that earlier. We merged in a PR on Sunday for containerizing the Fabric API and the documentation wasn't updated 100% yet

RahulDesai (Thu, 05 Mar 2020 06:54:00 GMT):
Thanks @peter_somogyvari

peter_somogyvari (Thu, 05 Mar 2020 16:27:50 GMT):
Hi, we are at the Westin hotel (two corners from the conference) for a contributor meeting if anyone wants to join.

peter_somogyvari (Thu, 05 Mar 2020 16:28:00 GMT):
12th floor, room Cobalt

sfuji822 (Sat, 07 Mar 2020 10:46:40 GMT):
Peter, thank you very much for hosting F2F meeting at phoenix. I believe all of participants had great time with fruitful discussions in person. As par conversation, can you request to give Takuma (takeutak) the Maintainer privilege on BIF's github repository for starting actual coding ?

peter_somogyvari (Sat, 07 Mar 2020 19:36:19 GMT):
Shingo-san, yes I talked to Tracy on Friday and she'll add Takuma-san as a maintainer to the lab! Thank you all for attending the meeting, it was very refreshing to meet in person instead of on the phone, I hope to do it again in the future if and when we get the chance to be in the same city for whatever reason. :-)

ajayjadhav (Sun, 08 Mar 2020 10:56:10 GMT):
Has left the channel.

ajayjadhav (Fri, 13 Mar 2020 09:34:17 GMT):
Has joined the channel.

kulkarnikk (Fri, 13 Mar 2020 12:00:24 GMT):
Has joined the channel.

takeutak (Mon, 16 Mar 2020 05:02:28 GMT):
Hi everyone! I created a pull-request in order to reflect the proposed architecture which was agreed at Phoenix meeting (March 5) in our whitepaper. Would you mind if you confirm the following one? pull-request(#120): https://github.com/hyperledger-labs/blockchain-integration-framework/pull/120

takeutak (Mon, 16 Mar 2020 05:02:28 GMT):
Hi everyone! I created a pull-request in order to reflect the proposed architecture which was agreed at Phoenix BIF meeting (March 5) in our whitepaper. Would you mind if you confirm the following one? pull-request(#120): https://github.com/hyperledger-labs/blockchain-integration-framework/pull/120

peter_somogyvari (Mon, 16 Mar 2020 18:40:46 GMT):
Looks awesome, just merged it in, thank you very much!

peter_somogyvari (Tue, 17 Mar 2020 03:21:32 GMT):
Thanks everyone for joining today's contributors call! *Contributor Meeting Minutes - 2020 March 16th* - Hart will initiate conversations about the proposal to test the waters before a potential TSC vote. We will decide next actions according to the initial feedback from this. - Shingo-san and Takeuchi-san will work include the project names in the proposal document - Shingo-san and Takeuchi-san will work on the forth section of the whitepaper hashing out design details - Peter will try to consolidate the code base and make the first time user experience more pleasant - Peter will add a use-case to the whitepaper related to migration (which was already contributed by Rafael in separate PR) - We will ask Mic to help out with the PDO specific parts of the design in the whitepaper. Peter will do a code level POC on us supporting the PDO.

peter_somogyvari (Mon, 23 Mar 2020 18:17:06 GMT):
The code consolidation now has an initial draft PR link below. Still very much work in progress so don't have high expectations, but regardless I wanted to put it out here so everyone can see what's happening: https://github.com/hyperledger-labs/blockchain-integration-framework/pull/123

hartm (Mon, 23 Mar 2020 20:37:43 GMT):
Thanks Peter!

takeutak (Mon, 30 Mar 2020 13:47:51 GMT):
Hi everyone! Shingo created a pull-request in order to enhance BIF whitepaper (especially, interworking architecture). Would you mind if you confirm the following one? https://github.com/hyperledger-labs/blockchain-integration-framework/pull/124

peter_somogyvari (Tue, 31 Mar 2020 03:09:15 GMT):
A good source for names of cactus species, I'll pick a few from there and add it to the proposal tomorrow: https://www.americansouthwest.net/plants/cacti/arizona.html

hartm (Wed, 01 Apr 2020 21:29:36 GMT):
I just sent the proposal document out to the TSC list. Hopefully we'll get positive feedback!

hartm (Wed, 01 Apr 2020 21:29:54 GMT):
In the meantime, please sign up for the TSC list if you haven't already so that you can follow the discussion. Thanks!

thhkmgl (Sat, 04 Apr 2020 11:26:30 GMT):
Has joined the channel.

takeutak (Fri, 10 Apr 2020 07:16:07 GMT):
Hi everyone! The next BIF meeting is scheduled on April 13. As my previous assumption, our proposal to TSC was scheduled on April 9, then we should have discussed about countermeasures about TSC meeting on the next BIF meeting. But our proposal to TSC has been rescheduled on TSC meeting at April 16. Then, I'm sure that we should reschedule the next BIF phone meeting from April 13 to April 20, which makes us more speedy to discuss about the countermeasures. Would you mind if you postpone BIF meeting 1 week later (April 20)? If you have any other idea, could you share with me?

takeutak (Fri, 10 Apr 2020 07:16:07 GMT):
Hi everyone! The next BIF meeting is scheduled on April 13 (on USA timezone). As my previous assumption, our proposal to TSC was scheduled on April 9, then we should have discussed about countermeasures about TSC meeting on the next BIF meeting. But our proposal to TSC has been rescheduled on TSC meeting at April 16. Then, I'm sure that we should reschedule the next BIF phone meeting from April 13 to April 20, which makes us more speedy to discuss about the countermeasures. Would you mind if you postpone BIF meeting 1 week later (April 20)? If you have any other idea, could you share with me?

hartm (Fri, 10 Apr 2020 15:40:36 GMT):
@takeutak I think it's fine to go ahead and have the meeting on April 13th. We should probably discuss our plans for presenting to the TSC in advance, and that meeting is a great time to do it. If we need to have a meeting to discuss revisions on the 20th, then we can schedule it after the TSC meeting on the 16th.

hartm (Fri, 10 Apr 2020 15:40:39 GMT):
Does this sound reasonable?

peter_somogyvari (Fri, 10 Apr 2020 16:15:42 GMT):
@takeutak @hartm I'm happy to attend on both the 13th and 20th. Nothing wrong with cranking up the meeting schedule a bit when we think it's appropriate IMO.

takeutak (Mon, 13 Apr 2020 11:02:44 GMT):
@hartm @peter_somogyvari Thank you for your reply! I agree with the meeting on the 13th and 20th.

takeutak (Mon, 13 Apr 2020 11:02:44 GMT):
@hartm @peter_somogyvari Thank you for your reply! I agree with the meeting on April 13th and 20th.

takeutak (Mon, 13 Apr 2020 11:02:44 GMT):
@hartm @peter_somogyvari Thank you for your reply! I agree with the meeting on both of April 13th and 20th.

takeutak (Mon, 13 Apr 2020 11:02:44 GMT):
@hartm @peter_somogyvari Thank you for your reply! I agree with the meeting on April 13th. If we need so, I also agree with the meeting on April 20th.

takeutak (Mon, 13 Apr 2020 11:02:44 GMT):
@hartm @peter_somogyvari Thank you for your replies! I agree with the meeting on April 13th. If we need so, I also agree with the meeting on April 20th.

hartm (Mon, 13 Apr 2020 15:44:38 GMT):
Great! Talk to you tomorrow (your time)!

JHamilton (Tue, 14 Apr 2020 14:49:33 GMT):
hey all, updating that we now have a time scheduled for April 20th Americas and April 21 rest of the world :) https://lists.hyperledger.org/g/labs/viewevent?eventid=783004&calstart=2020-04-20

JHamilton (Thu, 16 Apr 2020 01:24:35 GMT):
@hartm you get a dunk tank & you get a dunk tank! 🤣

cliveb (Thu, 16 Apr 2020 03:35:35 GMT):
Has joined the channel.

cliveb (Thu, 16 Apr 2020 05:39:00 GMT):
Re: [Hyperledger TSC] Blockchain Integration Framework--Project Incubation Proposal and Dan Miiddleton's question: How are rollbacks/forks in either network resolved? The answer "some kind of outside verification setup seems to be required. If anyone has more elegant ideas, then we would be more than open to suggestions." I've been reading Alberts for elegant ideas from microbiology. BIF seems to be mimicking genetic transcription. Made observation, but still reading Alberts. http://clive.tries.fed.wiki/view/two-phase-commit-vs-polymerase-function

cliveb (Thu, 16 Apr 2020 05:39:00 GMT):
Re: [Hyperledger TSC] Blockchain Integration Framework--Project Incubation Proposal and Dan Miiddleton's question: How are rollbacks/forks in either network resolved? Hart's answer "some kind of outside verification setup seems to be required. If anyone has more elegant ideas, then we would be more than open to suggestions." I've been reading Alberts for elegant ideas from microbiology. BIF seems to be mimicking genetic transcription. Made observation, but still reading Alberts. http://clive.tries.fed.wiki/view/two-phase-commit-vs-polymerase-function

cliveb (Thu, 16 Apr 2020 05:39:00 GMT):
Re: [Hyperledger TSC] Blockchain Integration Framework--Project Incubation Proposal and Dan Miiddleton's question: How are rollbacks/forks in either network resolved? @hartm Hart's answer "some kind of outside verification setup seems to be required. If anyone has more elegant ideas, then we would be more than open to suggestions." I've been reading Alberts for elegant ideas from microbiology. BIF seems to be mimicking genetic transcription. Made observation, but still reading Alberts. http://clive.tries.fed.wiki/view/two-phase-commit-vs-polymerase-function

cliveb (Thu, 16 Apr 2020 05:39:00 GMT):
Re: [Hyperledger TSC] Blockchain Integration Framework--Project Incubation Proposal and Dan Miiddleton's question: How are rollbacks/forks in either network resolved? @hartm Hart's answer "some kind of outside verification setup seems to be required. If anyone has more elegant ideas, then we would be more than open to suggestions." I've been reading Alberts for elegant ideas from microbiology. BIF seems to be mimicking genetic transcription. Made some observations, but still reading Alberts. http://clive.tries.fed.wiki/view/two-phase-commit-vs-polymerase-function

cliveb (Thu, 16 Apr 2020 05:39:00 GMT):
Re: [Hyperledger TSC] Blockchain Integration Framework--Project Incubation Proposal and Dan Miiddleton's question: How are rollbacks/forks in either network resolved? Hart's answer "some kind of outside verification setup seems to be required. If anyone has more elegant ideas, then we would be more than open to suggestions." I've been reading Alberts for elegant ideas from microbiology. BIF seems to be mimicking genetic transcription. Made some observations, but still reading Alberts. http://clive.tries.fed.wiki/view/two-phase-commit-vs-polymerase-function

kumar89 (Thu, 16 Apr 2020 14:57:27 GMT):
Has joined the channel.

JHamilton (Thu, 16 Apr 2020 15:01:01 GMT):
great work @sfuji822 @hartm @peter_somogyvari !!! 🚀

hartm (Thu, 16 Apr 2020 15:01:12 GMT):
Thanks! We're not done yet though.

JHamilton (Thu, 16 Apr 2020 15:02:48 GMT):
certainly not

JHamilton (Thu, 16 Apr 2020 15:02:54 GMT):
but a big step 💪

peter_somogyvari (Thu, 16 Apr 2020 15:03:05 GMT):
Thank you sir! :-)

cliveb (Thu, 16 Apr 2020 15:49:38 GMT):
Good presentation on rational for plugins design for BIF. Federated Wiki also uses plugins and node. To help make plugins trusted wiki uses Miller's Caja https://github.com/fedwiki. Deno version is just underway https://github.com/joshuabenuck/seran-wiki

cliveb (Thu, 16 Apr 2020 15:49:38 GMT):
Making blockchain integration easier could go a long way to helping HL projects gain adoption. 195,518 decentralized facilities have registered with FDA for Food Safely Modernization Act (FSMA). Next up is, the U.S. Drug Supply Chain Security Act (DSCSA) 2023 that pushes the pharmaceutical industry to quickly improve upon supply chain traceability in an interoperable manner to address supply chain logistics in at least 17 countries. https://diginomica.com/critical-role-it-assuring-food-safety-pandemic-times

dhuseby (Thu, 16 Apr 2020 16:40:27 GMT):
Has joined the channel.

peter_somogyvari (Thu, 16 Apr 2020 19:01:47 GMT):
Thanks Clive, we do our best. :-) This federated wiki project looks cool, especially the deno port. I have high hopes for Deno one day becoming the de-facto runtime the way NodeJS is today, especially on account of the security enhancements which will only become more important each year. In a perfect world I would also push for BIF to run on Deno, but resources must be prioritized. :)

richzhao (Fri, 17 Apr 2020 09:28:04 GMT):
Has joined the channel.

kumar89 (Fri, 17 Apr 2020 11:08:09 GMT):
Do we have any recording of the previous BIF meeting please?

hartm (Mon, 20 Apr 2020 23:49:04 GMT):
Since we don't have a Hyperledger calendar-approved meeting this week (it's our off week), I figured I'd go ahead and create a zoom meeting.

hartm (Mon, 20 Apr 2020 23:49:07 GMT):
Here's the link:

hartm (Mon, 20 Apr 2020 23:49:15 GMT):
Hart Montgomery is inviting you to a scheduled Zoom meeting. Topic: BIF Off-Weekly Meeting Time: Apr 20, 2020 07:00 PM Pacific Time (US and Canada) Join Zoom Meeting https://zoom.us/j/99326471994?pwd=aXpvT0l3Z1lHaDRuT3hhY2NxUThZQT09 Meeting ID: 993 2647 1994 Password: 966735 One tap mobile +16699006833,,99326471994# US (San Jose) +13462487799,,99326471994# US (Houston) Dial by your location +1 669 900 6833 US (San Jose) +1 346 248 7799 US (Houston) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) +1 253 215 8782 US +1 301 715 8592 US Meeting ID: 993 2647 1994 Find your local number: https://zoom.us/u/ad54wbkITF Join by SIP 99326471994@zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India Mumbai) 115.114.115.7 (India Hyderabad) 213.19.144.110 (EMEA) 103.122.166.55 (Australia) 209.9.211.110 (Hong Kong China) 64.211.144.160 (Brazil) 69.174.57.160 (Canada) 207.226.132.110 (Japan) Meeting ID: 993 2647 1994 Password: 966735

hartm (Mon, 20 Apr 2020 23:49:26 GMT):
Talk to everyone in a couple of hours! Thanks!

JHamilton (Tue, 21 Apr 2020 01:05:40 GMT):
@hartm there is an official one already created

JHamilton (Tue, 21 Apr 2020 01:05:44 GMT):
i sent it last week

JHamilton (Tue, 21 Apr 2020 01:06:14 GMT):
as it's on the public calendar suggest we stick to that one

JHamilton (Tue, 21 Apr 2020 01:06:17 GMT):

Clipboard - April 20, 2020 8:06 PM

sfuji822 (Tue, 21 Apr 2020 01:25:47 GMT):
Thank you Jonathan ! Let's move to the official meeting room, then.

hartm (Tue, 21 Apr 2020 01:36:07 GMT):
Sorry I forgot!

hartm (Tue, 21 Apr 2020 01:36:14 GMT):
Let's stick with the real one then.

JHamilton (Tue, 21 Apr 2020 01:45:35 GMT):
no worries, lots more important things going on and a week ago seems like an eternity anyways 😅

JHamilton (Tue, 21 Apr 2020 02:48:36 GMT):
Key outcomes from today's BIF Contributors; please respond if I missed / misstated anything 1. Hart & Peter have prepared answers to questions raised in Arpil 16th TSC, including those on Identity 2. Takuma has also prepared sequence diagrams to address question raised on use cases 3. Takuma will share deck and Peter will send this along with #1 by EoD US 21st

JHamilton (Tue, 21 Apr 2020 02:49:18 GMT):
outside of TSC on 23rd we will resume our regular scheduled meetings on Mon 27th NA / 28th rest of the world

faraggi (Tue, 21 Apr 2020 10:48:52 GMT):
Has left the channel.

takeutak (Wed, 22 Apr 2020 09:20:33 GMT):
Hi everyone! I created a pull-request in order to reflect the enhanced use case of asset transfer (section 2.1: Ethereum to Quorum Asset Transfer) in our whitepaper, which was agreed at BIF phone meeting (April 20). Would you mind if you confirm the following one? pull-request(#125): https://github.com/hyperledger-labs/blockchain-integration-framework/pull/125

peter_somogyvari (Wed, 22 Apr 2020 13:42:09 GMT):
Done, thank you very much!

JHamilton (Thu, 23 Apr 2020 15:01:41 GMT):
another step! is it worth making visible recurring maintainers call?

hartm (Thu, 23 Apr 2020 15:28:10 GMT):
We have our regular call this Monday. We've advertised it, but yes, it's probably useful to point it out.

hartm (Thu, 23 Apr 2020 15:28:39 GMT):
I'm going to start a google doc with answers for the questions that were brought up today. I'll send it out once I make some progress.

cliveb (Thu, 23 Apr 2020 17:24:17 GMT):
Making blockchain integration easier could go a long way to helping HL projects gain adoption. 195,518 decentralized facilities have registered with FDA for Food Safely Modernization Act (FSMA). Next up, the U.S. Drug Supply Chain Security Act (DSCSA) 2023 that pushes the pharmaceutical industry to quickly improve upon supply chain traceability in an interoperable manner to address supply chain logistics in at least 17 countries. https://diginomica.com/critical-role-it-assuring-food-safety-pandemic-times

cliveb (Thu, 23 Apr 2020 17:51:53 GMT):
Could a developer create a domain specific plugin for BIF to transport data to HL projects. e.g. for FDA traceability above?

hartm (Thu, 23 Apr 2020 19:05:42 GMT):
@cliveb If you look in the whitepaper, food traceability across multiple blockchains is a featured application. Presumably tracing drugs would be a very similar application.

HritikGupta (Fri, 24 Apr 2020 07:44:01 GMT):
Has joined the channel.

cliveb (Fri, 24 Apr 2020 19:45:27 GMT):
Re: "traceability (section 2.6) when “supplies” move across different... Could BIF be used as a transporter between disparate ERPs used by food/pharma manufactures and HL Fabric. i.e. any roadblock to developers (like me) creating BIF plugins that transport from SQL databases to HL blockchain?

hartm (Fri, 24 Apr 2020 20:03:15 GMT):
@cliveb That's a great observation. I presume it would work (I can't be 100% certain), although you would clearly need to write your own BIF plugin for your SQL database and your SQL database would need to have some kind of cryptographic identity.

hartm (Fri, 24 Apr 2020 20:04:09 GMT):
I'm going to add in @takeutak and @sfuji822 who have worked on this application (I haven't worked with this one specifically).

hartm (Fri, 24 Apr 2020 20:04:28 GMT):
It might be a while until you get a response from them, though, unfortunately, because next week is Golden Week (a big holiday in Japan).

hartm (Fri, 24 Apr 2020 20:05:24 GMT):
I guess it should work if your database can handle general blockchain logic, which should be the case.

sownak (Mon, 27 Apr 2020 15:31:28 GMT):
Has joined the channel.

hartm (Tue, 28 Apr 2020 02:02:32 GMT):
A TSC action item page for comments: https://wiki.hyperledger.org/display/TSC/Move+the+Blockchain+Integration+Framework+%28BIF%29+lab+to+a+Project?focusedCommentId=31199066#comment-31199066

hartm (Tue, 28 Apr 2020 03:36:53 GMT):
Thanks for the meeting today, everyone! I think I'm going to put off the email I discussed to the TSC list until tomorrow to see if anyone comments on the wiki page before then.

cliveb (Wed, 29 Apr 2020 01:26:49 GMT):
In support of BIF https://docs.google.com/document/d/14WPHFy-j7ajnH8d4KeyCvo25w7EVwd5hxyPIALVckqc/edit

cliveb (Wed, 29 Apr 2020 01:26:49 GMT):
Added comment. In support of BIF. https://docs.google.com/document/d/14WPHFy-j7ajnH8d4KeyCvo25w7EVwd5hxyPIALVckqc/edit

hartm (Wed, 29 Apr 2020 01:54:45 GMT):
@cliveb Thanks, and thanks for participating in the meeting yesterday! It was great to hear from you.

sfuji822 (Wed, 29 Apr 2020 07:20:51 GMT):

BIF-plan20200428.pdf

cliveb (Wed, 29 Apr 2020 08:19:57 GMT):
I like the verification after-the-fact (Alice check status changes Cherie). If check status fails, log the fail?

MicBowman (Thu, 30 Apr 2020 14:37:18 GMT):
congratulations!!!!!

hartm (Thu, 30 Apr 2020 14:38:12 GMT):
Thanks @MicBowman . We look forward to talking with you more about this (hopefully we'll see you in some meetings!).

peter_somogyvari (Thu, 30 Apr 2020 14:48:18 GMT):
Now we just need to get a name approved. :-)

cliveb (Thu, 30 Apr 2020 15:27:27 GMT):
Pity that Isis, the Greek goddess of integration now has the wrong association.

cliveb (Thu, 30 Apr 2020 15:27:27 GMT):
Pity that Isis, the Egyptian goddess of integration now has the wrong association.

knagware9 (Thu, 30 Apr 2020 15:34:17 GMT):
Congrats ..looking forward to contribute to BIF

JHamilton (Thu, 30 Apr 2020 15:48:04 GMT):
Apparently the trick was to just have me not join :stuck_out_tongue_closed_eyes:

rjones (Thu, 30 Apr 2020 15:54:24 GMT):
Has joined the channel.

rjones (Thu, 30 Apr 2020 15:55:26 GMT):
@hartm and I were discussing next steps. I can move the code easily, but creating the wiki before having a name is problematic. Mailing lists as well.

rjones (Thu, 30 Apr 2020 15:55:44 GMT):
I propose moving the code and punting on everything else until the name is decided

hartm (Thu, 30 Apr 2020 15:56:16 GMT):
@rjones That sounds good to me.

rjones (Thu, 30 Apr 2020 15:56:32 GMT):
OK. Next question: are you moving to Azure Pipelines for CI/CD? Please say yes.

hartm (Thu, 30 Apr 2020 15:56:33 GMT):
We need to go through marketing approval to get the name anyways, so that could take a bit.

rjones (Thu, 30 Apr 2020 15:56:55 GMT):
oh wait, I see you're on circle CI, we're good.

rjones (Thu, 30 Apr 2020 15:57:28 GMT):
I would prefer AZP but I'm not a developer :)

peter_somogyvari (Thu, 30 Apr 2020 16:13:08 GMT):
CI is sort of a moving target at the moment for us, will definitely look into AZP because CircleCI has this issue that it cannot trigger builds for PRs, only actual branch commits... :/ Off-topic: @rjones Is the code move just a one to one copy from the labs GH org to the main one or is there something else that you are changing along the way as well? (I know the name will have to be changed later)

rjones (Thu, 30 Apr 2020 16:13:47 GMT):
it's a direct move. GitHub also silently fixes up your remotes for a while

rjones (Thu, 30 Apr 2020 16:19:18 GMT):
I'd like to get this merged, in some form, before the move. https://github.com/hyperledger-labs/blockchain-integration-framework/pull/126

rjones (Thu, 30 Apr 2020 16:19:49 GMT):
I just took the list of everyone in the github group with write access

peter_somogyvari (Thu, 30 Apr 2020 17:00:32 GMT):
Working on a consensus regarding the maintainers list. Sorry for the wait. :-)

rjones (Thu, 30 Apr 2020 17:02:03 GMT):
Let me know when you make your decisions and I'll do the things. I don't want to move it at this instant because I need to create the ACLs when it lands

peter_somogyvari (Thu, 30 Apr 2020 17:04:48 GMT):
Understood. Will ping you here and LGTM the PR once we are ready. Cheers

peter_somogyvari (Thu, 30 Apr 2020 18:17:55 GMT):
Updated the PR with the freshly proposed list, now just waiting for everyone on it to chime in/approve and then we are good to go. I'll send another ping once that's also done. Want to make sure we have a unanimous agreement.

peter_somogyvari (Fri, 01 May 2020 02:40:10 GMT):
@sfuji822 @takeutak I think you already answered this question so apologies for asking again, but I could not figure it out. Where is the editable version of the file `docs/whitepaper/architecture-with-plugin-and-routing.png` that you added in the commit https://github.com/petermetz/blockchain-integration-framework/commit/c3b7d5e16f0a5883563384619413e43e0503694d I know we talked about this, I just cannot remember for the life of me, sorry. :-)

JHamilton (Fri, 01 May 2020 03:31:48 GMT):
Should we meet back up at our Monday NA / Tuesday (rest of the world) time to keep momentum up and organize actions / owners?

JHamilton (Fri, 01 May 2020 03:32:27 GMT):
otherwise our next meet is not until 11th / 12th

hartm (Fri, 01 May 2020 15:00:15 GMT):
@JHamilton Yes, it's probably a good idea to meet Monday.

hartm (Fri, 01 May 2020 15:00:27 GMT):
Not sure if the Japanese folks can make it, since it's a holiday for them though.

JHamilton (Fri, 01 May 2020 15:28:16 GMT):
thanks @hartm ! I had not realized about the holiday, there's a few there in a row!

JHamilton (Fri, 01 May 2020 15:29:19 GMT):
@sfuji822 @takeutak what would you prefer? if we meet later in the week will you be able to join? otherwise maybe we will take an earlier time in the day Americas

S.Fujimoto (Mon, 04 May 2020 00:25:01 GMT):
Has joined the channel.

S.Fujimoto (Mon, 04 May 2020 00:25:02 GMT):
I would like to have short version of the meeting to discuss about following up TSC meeting result.

S.Fujimoto (Mon, 04 May 2020 00:25:55 GMT):
I would like to have short version of the meeting to discuss about following up TSC meeting result.

JHamilton (Mon, 04 May 2020 10:57:29 GMT):
great, thank you! by short version of the meeting do you mean at our regular time "today" 4th Americas and 5th rest of the world?

JHamilton (Mon, 04 May 2020 20:27:12 GMT):
since this is last minute and unlikely to be picked up by someone from the broader community, perhaps we can connect at the regular time "today" on https://zoom.us/my/hyperledger.community.3

JHamilton (Mon, 04 May 2020 20:27:34 GMT):
or please let me know if other ideas :D

sfuji822 (Mon, 04 May 2020 22:47:24 GMT):
Yeah, I assumed that it will start at regular time. sorry for slow response.

JHamilton (Mon, 04 May 2020 23:14:00 GMT):
no worries, i appreciate that it is actually a holiday in Japan. talk to you in a few hours :)

hartm (Mon, 04 May 2020 23:38:37 GMT):
Talk to you all then!

hartm (Mon, 04 May 2020 23:38:46 GMT):
Think of your name preference, if possible!

JHamilton (Tue, 05 May 2020 02:02:22 GMT):
sorry i'm getting a zoom error

hartm (Tue, 05 May 2020 02:02:36 GMT):
No worries!

hartm (Tue, 05 May 2020 02:02:45 GMT):
And that's weird--it's usually reliable.

JHamilton (Tue, 05 May 2020 13:46:29 GMT):
NAMING 🚀 _Additional naming guidelines can be found here._ https://docs.google.com/document/d/1P__qAcWL-CYHZGozKpS8WCyQ3brTpBweFfUwYzEZD0w/edit the bad news: none of the names we have are completely "clean", some level of existing conflicts. the good news: none of the conflicts appears significant or within the Blockchain space

JHamilton (Tue, 05 May 2020 13:48:26 GMT):
can we go ahead and share the list w/ Jessica?

hartm (Tue, 05 May 2020 15:20:21 GMT):
Yes, will do.

MicBowman (Wed, 06 May 2020 17:47:00 GMT):
in the architecture working group meeting today we talked about how to provide an authoritative description of a distributed ledger that might include descriptions of consensus algorithms, transaction commit rates, etc... this information could be used to create (in theory) a more formal description of the characteristics of a multiple-chain transaction. @hartm @peter_somogyvari would you be available to come into the AWG meeting in two weeks to help us figure out what your requirements might be?

hartm (Wed, 06 May 2020 17:50:51 GMT):
I'd be happy to come and talk then, sure.

hartm (Wed, 06 May 2020 17:51:05 GMT):
What kind of preparation would we need to do?

hartm (Wed, 06 May 2020 17:51:17 GMT):
(I would have come today but had a VDF meeting I needed to attend).

peter_somogyvari (Wed, 06 May 2020 18:03:30 GMT):
I'm happy to show up as well (and apologies that I haven't so far, I'm still working on the schedule). The first thing that comes to my mind that we need 100% is some enum/boolean (I prefer enums even when there's only 2 possible values to begin with) property describing whether the ledger with the given consensus algorithm has transaction finality. A lot of modern ledgers have pluggable consensus so it's probably wiser to actually have the transaction finality property specified for consensus algorithms and the ledger instance should describe the algorithm it's running on so one could retrieve information about transaction finality with a reference chain like this: `ledger.consensusAlgorithm.transactionFinality == TransactionFinality.GUARANTEED` or `ledger.consensusAlgorithm.transactionFinality == TransactionFinality.NOT_GUARANTEED` And then for a BIF transaction proposal one could write code that examines the to-be participating ledgers transaction finality and take action if there's a mismatch. `Transaction commit rates`: Do you mean from a performance/throughput perspective or specific to the algorithm's configuration (like block size, number of transactions per mined block, etc?)

MicBowman (Wed, 06 May 2020 21:58:09 GMT):
@hartm no preparation, i think we want to talk about the general problem of how to build self-describing ledgers such that we could reason about applications built on those ledgers...

MicBowman (Wed, 06 May 2020 22:00:57 GMT):
@peter_somogyvari i understand the boolean on finality as a first step, but remember that even ledgers with finality "are not all the same"; they may have the same semantics but have very different trust (e.g. you might trust a ledger with multiple organizations participating in the ordering and validation of transactions more than you trust a ledger with an ordering service provided by a single organization)

MicBowman (Wed, 06 May 2020 22:01:42 GMT):
and... then we have the question about why we would believe a ledger that makes a claim about itself

MicBowman (Wed, 06 May 2020 22:02:43 GMT):
or... by what authority does a ledger claim that a transaction has been committed

MicBowman (Wed, 06 May 2020 22:03:44 GMT):
some of these questions are ones i've had for a while & are consistent, i think, with some of the concerns that angelo asked in the review

peter_somogyvari (Wed, 06 May 2020 22:07:29 GMT):
@MicBowman Yeah, I remember these coming up. Have you seen the response we provided regarding trust/authority on the TSC list? It's possible that it fell through the cracks because I haven't had time yet to include it in the whitepaper or anywhere else for that matter (hoping to add it soon though).

peter_somogyvari (Wed, 06 May 2020 22:08:46 GMT):
The answer on the TSC list was just an anecdotal one, there wasn't any formal specs included there, but I agree we should work towards that.

MicBowman (Wed, 06 May 2020 22:19:28 GMT):
yes, i saw the response. i think we need to keep separate what is "useful" and what is "provable"... "useful" works well with out of band information between a small set of parties; "provable" will be necessary in a world where there are "many" ledgers and out of band trust is not sufficient

hartm (Wed, 06 May 2020 22:27:11 GMT):
We'd be happy to discuss these things in two weeks.

hartm (Wed, 06 May 2020 22:27:17 GMT):
To answer some of your questions:

hartm (Wed, 06 May 2020 22:27:59 GMT):
If you don't believe a ledger making a claim on itself, then there's no reason to believe anything about the ledger period--so if this is the case, there's no value in doing a transaction on the ledger at all.

hartm (Wed, 06 May 2020 22:28:44 GMT):
You can have a ledger perform a consensus validation of a particular state to verify that a transaction has been committed. Alternatively, you could simplify this a lot using threshold signatures, but this is a lot to ask.

hartm (Wed, 06 May 2020 22:29:03 GMT):
We'd be happy to field questions like this. In fact, it'd be very useful for us.

hartm (Wed, 06 May 2020 22:29:07 GMT):
So let's plan on two weeks then.

MicBowman (Wed, 06 May 2020 23:57:29 GMT):
for a security guy you sure are trusting! :grin:

hartm (Wed, 06 May 2020 23:57:52 GMT):
Ouch!

MicBowman (Wed, 06 May 2020 23:58:20 GMT):
point is that a ledger is a collective and as a collective may be trusted, but individual validators may lie through their teeth

hartm (Wed, 06 May 2020 23:58:43 GMT):
Right--that's why you need some collective ledger validation.

hartm (Wed, 06 May 2020 23:59:02 GMT):
And why I said threshold signatures are an ideal primitive for this.

MicBowman (Wed, 06 May 2020 23:59:18 GMT):
so i think all of these issues... what can we say about a ledger become very interesting

MicBowman (Wed, 06 May 2020 23:59:42 GMT):
who has the right to sign? how do you know who the current set of validators is?

MicBowman (Thu, 07 May 2020 00:00:08 GMT):
again... very trusting. i'm disappointed in you hart! ;-)

MicBowman (Thu, 07 May 2020 00:01:37 GMT):
fwiw... i think we again need to think about useful and provable as two different things... where useful is "acceptable risk" and it is defined in terms of what my application is willing to accept as "truth"

MicBowman (Thu, 07 May 2020 00:03:24 GMT):
for BIF (or whatever its called now), in the short term i think "useful" dominates and we should be able to do something fairly straightforward, when the "trust" has to be automated, things get more interesting

hartm (Thu, 07 May 2020 00:09:49 GMT):
Yes, that's a great point. Right now we are "hardcoding" trust into use cases, so everything is pretty simple. If you want to do things dynamically, then it gets really complicated.

hartm (Thu, 07 May 2020 00:11:52 GMT):
This is a great topic for further discussion.

hartm (Thu, 07 May 2020 00:12:03 GMT):
We'd be happy to talk about at at the arch meeting or also at the BIF meeting.

rjones (Thu, 07 May 2020 00:34:47 GMT):
Is the name decided now?

rjones (Thu, 07 May 2020 00:35:09 GMT):
If so, I will start turning the crank for the wiki and the like post-TSC call

peter_somogyvari (Thu, 07 May 2020 00:47:31 GMT):
It's been narrowed down but haven't been finalized still from what I understood based on the emails.

hartm (Thu, 07 May 2020 00:48:22 GMT):
I'm hoping we can finalize this tonight, @rjones

hartm (Thu, 07 May 2020 01:01:56 GMT):
I just sent out an email on this.

JHamilton (Thu, 07 May 2020 14:02:03 GMT):
@sfuji822 @takeutak can you please weigh in on the proposed name of Cactus? if we have alignment from maintainers then we can bypass time to vote

JHamilton (Thu, 07 May 2020 14:02:22 GMT):
Peter and I are good with the name

JHamilton (Thu, 07 May 2020 14:02:49 GMT):
as is Brian Behlendorf 😎

hartm (Thu, 07 May 2020 14:03:06 GMT):
@JHamilton They did in a meeting last night, and they are good with it.

hartm (Thu, 07 May 2020 14:03:10 GMT):
I thought my email expressed that.

JHamilton (Thu, 07 May 2020 14:03:21 GMT):
apparently not, i will respond to Jessica

hartm (Thu, 07 May 2020 14:03:37 GMT):
@takeutak even suggested the name to begin with!

JHamilton (Thu, 07 May 2020 14:05:27 GMT):
👏

rjones (Thu, 07 May 2020 14:55:07 GMT):
should I rename this channel or start a new one?

JHamilton (Thu, 07 May 2020 14:56:22 GMT):
i vote rename so history retained

rjones (Thu, 07 May 2020 14:57:53 GMT):
@here when do you want me to rename and move the repo?

hartm (Thu, 07 May 2020 14:59:29 GMT):
Rename for sure.

hartm (Thu, 07 May 2020 14:59:56 GMT):
I guess we just need some kind of official approval?

rjones (Thu, 07 May 2020 15:23:27 GMT):
https://github.com/hyperledger/cactus

rjones (Thu, 07 May 2020 15:23:27 GMT):
Room name changed to: cactus-contributors by rjones

rjones (Thu, 07 May 2020 15:23:54 GMT):
OK.

MicBowman (Thu, 07 May 2020 16:09:58 GMT):
i don't think we need to change the focus of the BIF meetings, lets just meet with the AWG next time & see if we can define the problem more precisely

peter_somogyvari (Thu, 07 May 2020 17:01:16 GMT):
@rjones I just updated the maintainers PR with the finalized list and LGTM'd it and will merge in a minute.

peter_somogyvari (Thu, 07 May 2020 17:02:30 GMT):
Okay, need a reboot so more like 15 minutes. Back soon.

rjones (Thu, 07 May 2020 17:02:51 GMT):
I can merge it whenever. I incorporated your changes.

peter_somogyvari (Thu, 07 May 2020 17:18:27 GMT):
Feel free to do it anytime in that case. My dev VM is still booting... :-)

rjones (Thu, 07 May 2020 17:22:08 GMT):
https://github.com/hyperledger/cactus

peter_somogyvari (Thu, 07 May 2020 18:35:50 GMT):
Do we need to have a general and contributor specific channel at the same time?

peter_somogyvari (Thu, 07 May 2020 18:35:59 GMT):
(just curious)

rjones (Thu, 07 May 2020 18:37:14 GMT):
your call. I think you have the ability to rename this channel as you please - I'm not stuck on the name

peter_somogyvari (Thu, 07 May 2020 18:39:17 GMT):
I don't think we need two channels, not for now at least, but at the same time I'd first just call it 'cactus' so that nobody gets the feeling that they are not welcome on the channel unless they are a 'contributor'. So, I'll probably propose to rename it to just Cactus.

rjones (Thu, 07 May 2020 18:39:40 GMT):
Room name changed to: cactus by rjones

peter_somogyvari (Thu, 07 May 2020 18:39:57 GMT):
Thank you very much!

hartm (Fri, 08 May 2020 01:43:00 GMT):
Thanks @rjones !

rjones (Fri, 08 May 2020 01:55:20 GMT):
You're welcome @hartm !

JHamilton (Mon, 11 May 2020 19:51:05 GMT):
hey #cactus ! Proposed topics for contributors connection in ~6 hours. Please respond with any additions / modifications! 1. Critical path to Consensus announcements a. blog post(s) b. Name transition (anything remaining?) 2. PR 123 3. Routing Layer discussion

JHamilton (Tue, 12 May 2020 03:18:09 GMT):
The key outcomes I captured from tonight's discussion, please respond if any I missed or mistated: 1. Critical path to Consensus announcements a. Fujitsu will review the blog post and respond with any further adjustments b. Jonathan will check with Jessica on cactus logo and project URL e.g. https://www.hyperledger.org/projects/cactus 2. PR 123 https://github.com/hyperledger/cactus/pull/123 a. Large draft PR on the foundation of packaging; goal to merge in the next 1-2 weeks so seeking feedback now! b. Goal to make programatically configurable and establish packaging structure so that test driven development of plugins can begin and more paralell plug-in development can start 3. Routing Layer discussion a. Aligned in principle of using existing ecosystem components where possible. b. For each component we will work through the details in code / package 4. Other a. Team has lots to discuss still and will move to weekly meetings for the near future b. Going forward meetings will be recorded / posted

sownak (Wed, 13 May 2020 17:42:12 GMT):
Any change in the meeting times for a better GMT hour :)

rjones (Wed, 13 May 2020 18:18:47 GMT):
Who will moderate the email list to start? I need email addresses - feel free to send them to me directly in DM

rjones (Wed, 13 May 2020 18:20:25 GMT):
(I already volunteered @JHamilton ) :)

rjones (Wed, 13 May 2020 18:27:03 GMT):
https://wiki.hyperledger.org/display/cactus

JHamilton (Wed, 13 May 2020 20:19:34 GMT):
hey @rjones we would like to move our contributors session from fortnightly to weekly. can you help us or will one of us get calendar superpowers with project status? 🚀

rjones (Wed, 13 May 2020 20:25:22 GMT):
you should have that power - you can edit the calendar directly

rjones (Wed, 13 May 2020 20:26:54 GMT):
oh, I see what's hard about it. Could you create a replacement in the [new calendar](https://lists.hyperledger.org/g/cactus/calendar) and tell me which ones to deletew?

umtyzc (Wed, 13 May 2020 20:33:38 GMT):
Has joined the channel.

JHamilton (Wed, 13 May 2020 20:42:29 GMT):
#cactus we are now on for weekly contributors session. thanks @rjones for the help. letsgo!

rjones (Wed, 13 May 2020 20:45:25 GMT):
:cactus:

JHamilton (Wed, 13 May 2020 20:52:32 GMT):
Also our new calendar is here for future reference! https://lists.hyperledger.org/g/cactus/calendar?calstart=05%2f18%2f2020

baohua (Wed, 13 May 2020 21:25:22 GMT):
Has joined the channel.

rjones (Wed, 13 May 2020 22:17:55 GMT):
@JHamilton could I get a merge? https://github.com/hyperledger/cactus/pull/131 thanks

JHamilton (Wed, 13 May 2020 23:27:27 GMT):
Done! Thanks for the housekeeping

Taaanos (Thu, 14 May 2020 11:57:26 GMT):
Has joined the channel.

JHamilton (Thu, 14 May 2020 19:31:07 GMT):
glad to see the logo show up! thanks Ry! i was planning to take a pass thru the confluence setup later today

rjones (Thu, 14 May 2020 19:59:45 GMT):
It's a rough cut of the PDF - once I have the SVG, I'll replace it.

saanvijay (Fri, 15 May 2020 03:02:14 GMT):
Has joined the channel.

Rachit-gaur (Fri, 15 May 2020 05:57:05 GMT):
Has joined the channel.

Rachit-gaur (Fri, 15 May 2020 05:59:45 GMT):
Hi Guys, I read about hyperledger cactus today and really loved the idea. Would love to contribute. Cheers

Rachit-gaur (Fri, 15 May 2020 06:02:02 GMT):
I've automated the fabric network process and can spin up any configuration (raft,solo,kafka) within seconds for upto 1.4.4 version

Rachit-gaur (Fri, 15 May 2020 06:02:02 GMT):
I've automated the fabric network creation process and can spin up any configuration (raft,solo,kafka) within seconds for upto 1.4.4 version

Rachit-gaur (Fri, 15 May 2020 06:04:41 GMT):
Please let me know if I can be of any help. Thanks

AshutoshKumar7 (Sun, 17 May 2020 15:21:41 GMT):
Has joined the channel.

JHamilton (Sun, 17 May 2020 20:53:34 GMT):
Hello Rachit-gaur, great to hear your interest to contribute! we have our weekly contributors call on Monday Americas / Tues other time zones https://lists.hyperledger.org/g/cactus/calendar?calstart=05/18/2020

JHamilton (Sun, 17 May 2020 20:56:34 GMT):
understood that the time is not ideal for all time zones; we are considering how to cover more time zones so please let us know which one you are on if you plan to join regularly

JHamilton (Sun, 17 May 2020 20:58:02 GMT):
hey #cactus i started our first Jira agenda but am having some issue w/ Jira itself... can yall see / access? https://wiki.hyperledger.org/pages/resumedraft.action?draftId=31200292&draftShareId=b7b74e41-a891-414f-8aa9-4863f48c30d7&

JHamilton (Sun, 17 May 2020 20:59:15 GMT):
in case people can not access the draft here's the summary. feedback / edits welcome! Discussion * Any remaining Marketing, Media & Cactus cut-over loose ends * PR123 any discussion points prior to merge * Key enabler for collaboration; request to complete review in advance and document feedback on PR in advance of meeting * European contributors; moving to rolling schedule * Establishing criteria for 0.2 and roadmap for 0.3

JHamilton (Mon, 18 May 2020 16:13:52 GMT):
Ry helped fix editing issues, please go ahead and tailor proposed discussion agenda https://wiki.hyperledger.org/display/cactus/2020-05-18+Meeting+Agenda

jweate (Mon, 18 May 2020 17:20:10 GMT):
Has joined the channel.

peter_somogyvari (Mon, 18 May 2020 20:07:15 GMT):
@Rachit-gaur Sounds awesome! In addition to what Jonathan said: Do you have the code for this automation of Fabric network creation available somewhere public? I'd love to take a look and am also interested if it could be tailored for Fabric 2.0 as well.

peter_somogyvari (Mon, 18 May 2020 20:08:23 GMT):
Cheers, checked it just now, it works for me.

peter_somogyvari (Mon, 18 May 2020 20:09:41 GMT):
Did we lose the commit lint bot with the repo migration? Just wondering because it should've been complaining that the commit message wasn't in the required format (I know, I'm a stickler, but we need that for the automated change log generation)

JHamilton (Tue, 19 May 2020 01:25:19 GMT):
ack, yes looks like its gone. i could swear it was there post migration

JHamilton (Tue, 19 May 2020 01:36:26 GMT):
imagine it has to do with org permissions... i need to remember how it was activated in the first place, don't think it was painful just chore for someone to do... any volunteers? :D

JHamilton (Tue, 19 May 2020 02:00:09 GMT):

Clipboard - May 18, 2020 9:00 PM

JHamilton (Tue, 19 May 2020 02:00:17 GMT):
@rjones can you add @takeutak to Hyperledger GH Maintainers? looks like he was missed somehow 👆

takeutak (Tue, 19 May 2020 02:23:45 GMT):
@rjones @JHamilton Thank you Jonathan. My GitHub ID is takeutak (the same as rocketchat ID)

takeutak (Tue, 19 May 2020 02:49:34 GMT):
@rjones So would you mind if you add me (GitHub ID: takeutak) to Hyperledger GH Maintainers?

rjones (Tue, 19 May 2020 06:45:18 GMT):
@takeutak you have had an outstanding invitation since the move. You will need to accept the invitation.

rjones (Tue, 19 May 2020 06:46:14 GMT):
Please check your email; alternatively, you could visit https://github.com/hyperledger when you are logged in. You should see the invitation at the top of the page.

mzins_dev (Tue, 19 May 2020 15:44:27 GMT):
Has joined the channel.

takeutak (Wed, 20 May 2020 01:36:22 GMT):
@rjones Thank you for your guidance. I visited the URL https://github.com/hyperledger and checked your invitaion. But the message happened that "This invitation has expired." I guess that the expiration date of you invidation was over now. Would you mind if you give me the invitaion again?

takeutak (Wed, 20 May 2020 01:37:33 GMT):
@rjones Thank you for your guidance. I visited the URL https://github.com/hyperledger and checked your invitaion. But the message happened that "This invitation has expired." I guess that the expiration date of you invidation was over now. Would you mind if you give me the invitaion again?

takeutak (Wed, 20 May 2020 01:37:33 GMT):
@rjones Thank you for your guidance. I visited the URL https://github.com/hyperledger and checked your invitaion. But the message happened that "This invitation has expired." I guess that the expiration date of your invidation was over now. Would you mind if you give me the invitaion again?

amalcs23 (Wed, 20 May 2020 07:05:53 GMT):
Has joined the channel.

JHamilton (Wed, 20 May 2020 15:12:42 GMT):
#cactus hope all are keeping well. one of the things we ran out of time for in this weeks call (with 0.2 vs. 0.3 agenda item) was about hygiene of ensuring PRs are tied to issues. this helps the maintainers and the broader community have visibility on the work in-progress and the desired work. https://github.com/hyperledger/cactus/issues with our project status we have access to Jira but for now suggest we continue using GH issues, which has a nice template feature tied into contributing. https://github.com/hyperledger/cactus/blob/master/CONTRIBUTING.md we can use this as a way to structure our work remaining for 0.2 vs. objectives for 0.3 and better enable async collaboration. https://github.com/hyperledger/cactus/projects/1 any concerns about this approach or better ways to tackle?

JHamilton (Wed, 20 May 2020 15:12:42 GMT):
#cactus hope all are keeping well. one of the things we ran out of time for in this weeks call (with 0.2 vs. 0.3 agenda item) was about hygiene of ensuring PRs are tied to issues. this helps the maintainers and the broader community have visibility on the work in-progress and the desired work. https://github.com/hyperledger/cactus/issues with our project status we have access to Jira but for now suggest we continue using GH issues, which has a nice issue template feature tied into contributing. https://github.com/hyperledger/cactus/blob/master/CONTRIBUTING.md we can use this as a way to structure our work remaining for 0.2 vs. objectives for 0.3 and better enable async collaboration. https://github.com/hyperledger/cactus/projects/1 any concerns about this approach or better ways to tackle?

rjones (Wed, 20 May 2020 15:52:18 GMT):
sent again

rjones (Wed, 20 May 2020 22:19:35 GMT):
Hey folks, it looks like the [commit bot you're using is EOL](https://github.com/z0al/commitlint-bot). They suggest using [this bot instead](https://github.com/apps/semantic-pull-requests). Thoughts?

rjones (Wed, 20 May 2020 22:19:35 GMT):
Hey folks, it looks like the [commit bot you\'re using is EOL](https://github.com/z0al/commitlint-bot). They suggest using [this bot instead](https://github.com/apps/semantic-pull-requests). Thoughts?

peter_somogyvari (Wed, 20 May 2020 23:14:34 GMT):
Ah man, that's unlucky. I have to check if they allow to change the `at least one semantic commit message` constraint to `only semantic commit messages`. If yes, then I'm fine with it. Checking the commit messages is the only reason I wanted that particular bot.

peter_somogyvari (Wed, 20 May 2020 23:16:00 GMT):
Yepp, seems to work, according to their docs this is possible in the config: ``` # Always validate the PR title AND all the commits titleAndCommits: true ```

peter_somogyvari (Wed, 20 May 2020 23:17:16 GMT):
`A request to install Semantic Pull Requests has been submitted on the @hyperledger account.`

rolsonquadras (Thu, 21 May 2020 17:24:07 GMT):
Has joined the channel.

Unni_1994 (Fri, 22 May 2020 07:27:13 GMT):
Has joined the channel.

takeutak (Fri, 22 May 2020 10:31:10 GMT):
@rjones Thank you! I received your invitation.

takeutak (Fri, 22 May 2020 10:31:10 GMT):
@rjones Thank you! I received your invitation and accepted.

VipinB (Sun, 24 May 2020 16:11:21 GMT):
It would be great if one or more of you could present on cactus on the Identity Working Group- especially the digital identity usecase that you outlined, or how management of multiple identities (from the same holder) on different chains can help interoperability. It can be as early as this Wednesday 12 pm. EST. This could drive some identity experts to participate in Cactus. The cross-chain identity conundrum should be addressed.

amalcs23 (Mon, 25 May 2020 05:32:21 GMT):
Hai, Is there any detailed work flow explanation or use case demonstration available?

takeutak (Mon, 25 May 2020 06:59:06 GMT):
Hi @peter_somogyvari @JHamilton @sfuji822 and everyone! At the last Cactus meeting (May 18 USA time), I heard that the Cactus meeting on May 25 USA time would be canceled due to the holiday in USA. Is this correct? I found that the meeting on May 25 USA time still remains in Hyperledger public schecule. Would you mind if you cancel the meeting on Hyperledger calender? https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings BR, Takuma

rjones (Mon, 25 May 2020 16:31:52 GMT):
@takeutak done

takeutak (Tue, 26 May 2020 01:10:51 GMT):
@rjones Thank you for your replying. Do you mean that you already canceled today's Cactus meeting on Hyperledger calender? But I find that today's meeting still remains. I'm sorry for troubling you, but would you mind if you check it again? https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings

takeutak (Tue, 26 May 2020 01:10:51 GMT):
@rjones Thank you for your replying. Do you mean that you already canceled today's Cactus meeting on Hyperledger calender? But I find that today's meeting still remains in the calendar. I'm sorry for troubling you, but would you mind if you check it again? https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings

peter_somogyvari (Tue, 26 May 2020 01:15:37 GMT):
@takeutak Sorry for the late response. No issues from my side with cancelling it. I don't have permissions to modify the meetings, but I see @rjones took care of that already so we should be cancelled now. Cheers Ry!

peter_somogyvari (Tue, 26 May 2020 01:42:02 GMT):
@VipinB I'm working on a PR for our first identity related plugin that (when plugged in) basically gives you an Open ID Connect Identity Provider and authorization server so that what's in the whitepaper's `2.7` use case (direct link below) is slowly but surely becomes achievable. Use case from whitepaper: https://github.com/hyperledger/cactus/blob/master/whitepaper/whitepaper.md#27-end-user-wallet-authenticationauthorization My fork's branch for the OIDC plugin (frequently changes and gets force pushed so watch out!) => https://github.com/petermetz/blockchain-integration-framework/tree/feature/open-id-connect-web-service-plugin Regarding presenting this Wednesday: a little early because I myself still have a lot questions about how this or that would work *exactly* in the implementation so it might not be too stimulating for the audience just yet, BUT definitely sign me up for the following meeting (e.g. first one after the one this Wednesday). :-)

rjones (Tue, 26 May 2020 01:44:01 GMT):
@takeutak it can take 24 hours for the google calendar to catch up. if you look here you will see it is cancelled : https://lists.hyperledger.org/g/cactus/message/7

takeutak (Tue, 26 May 2020 01:50:59 GMT):
@rjones Thank you very much! All right.

peter_somogyvari (Tue, 26 May 2020 01:51:36 GMT):
Hi @amalcs23 Yes! We have explanations with detailed diagrams in the whitepaper use cases section here (link below) and actual code level demonstrations I can point you to some automated tests that we have but those only cover the most basic of things like deploying contracts on different supported ledgers via the plugins written for said ledgers. The tests are enforced by CI to always pass so in theory you can clone the project yourself and just run the `./tools/ci.sh` script on your machine and see the tests in action or even attach a debugger to them and just step through it to see it all. And please keep in mind: this is all work in progress. :-) Whitepaper, direct link to the use cases section: https://github.com/hyperledger/cactus/blob/master/whitepaper/whitepaper.md#2-example-use-cases Automated test verifying a contract deployment via the Cactus API: https://github.com/hyperledger/cactus/blob/master/packages/cactus-test-plugin-ledger-connector-quorum/src/test/typescript/integration/plugin-ledger-connector-quorum/deploy-contract/deploy-contract-via-web-service.ts

xxds (Tue, 26 May 2020 07:36:34 GMT):
Has joined the channel.

VipinB (Tue, 26 May 2020 13:22:40 GMT):
@peter_somogyvari this presentation does not have to be polished. It is in presenting the problems and getting feedback from the identity community that the value will be realized. I understand that this upcoming meeting is too soon. We can schedule for the next one which will be on June 10th.

peter_somogyvari (Tue, 26 May 2020 19:17:59 GMT):
@VipinB I agree 100%. June 10th is perfect, I marked it on my calendar, will bring a few slides and hopefully a working demo of whatever it is we have ready by then. Should be a stimulating conversation looking forward to it!

Rachit-gaur (Tue, 26 May 2020 22:50:42 GMT):
Hi guys I am in IST timezone, Will try my best to attend this meeting

Rachit-gaur (Tue, 26 May 2020 22:51:26 GMT):
@peter_somogyvari no sorry it isn't public, I am looking into 2.0 let's see what happens

Rachit-gaur (Tue, 26 May 2020 22:51:26 GMT):
@peter_somogyvari no sorry it isn't public, I work for a blockchain service provider company Votan Ventures, where I designed this singlehandedly, It also includes DevOps Tools to directly deploy on a pool of servers

Rachit-gaur (Tue, 26 May 2020 22:51:26 GMT):
@peter_somogyvari no sorry it isn't public, I am the co-founder of a blockchain service provider company Votan Ventures, where I designed this singlehandedly, It also includes DevOps Tools to directly deploy on a pool of servers

peter_somogyvari (Tue, 26 May 2020 23:59:12 GMT):
@Rachit-gaur No issues, didn't mean to pry of course. :-) If you can't make it, there's always this RocketChat or the mailing list (link below). We record the meetings as well so you can always just listen in after the fact and send thoughts/comments asynchronously, I'll definitely do my best to respond in substance. Here's the wiki for the recordings and the mailing list link as well: https://wiki.hyperledger.org/display/cactus https://lists.hyperledger.org/g/cactus/topics

hkiridera (Wed, 27 May 2020 03:57:05 GMT):
Has joined the channel.

amalcs23 (Wed, 27 May 2020 04:43:47 GMT):
Hi @peter_somogyvari

amalcs23 (Wed, 27 May 2020 04:48:06 GMT):
Hi @peter_somogyvari @JHamilton Correct me if I am wrong. In the white paper, 2.7 End User Wallet Authentication/Authorization use case diagram step 23 and 24, I think the ledgerOne is marked as wrong. LedgerTwo is the correct representation. Please send me the response. Thanks

peter_somogyvari (Wed, 27 May 2020 06:08:41 GMT):
@amalcs23 Ooops, that's right. The arrow is pointing to the wrong entity on the diagram, it should point to ledger 2 like the label says so. Thanks for catching that! I'll add github issue to have it fixed!

Rachit-gaur (Wed, 27 May 2020 18:13:16 GMT):
@peter_somogyvari no worries man, Thanks for the links.

rjones (Wed, 27 May 2020 19:03:09 GMT):
@JHamilton @peter_somogyvari I

rjones (Wed, 27 May 2020 19:03:09 GMT):
@JHamilton @peter_somogyvari I'm willing to delegate moderatorship of the mailing list as you like; this would let you edit the calendar directly

peter_somogyvari (Wed, 27 May 2020 19:05:46 GMT):
@rjones Works for me, thanks for the trust :-)

rjones (Wed, 27 May 2020 19:17:31 GMT):
You're now a mod, Peter, and you should be able to edit the calendar

peter_somogyvari (Wed, 27 May 2020 19:19:14 GMT):
Cheers Ry! Verified it: the 'edit event' button shows.

rjones (Wed, 27 May 2020 22:55:28 GMT):
Hi, I added your TSC update too early. It should be due on the correct date, with a reminder one week in advance.

peter_somogyvari (Wed, 27 May 2020 23:36:55 GMT):
Got it. The updated calendar invite says June 25th, that's the actual due date, not the "one week before" reminder, right?

rjones (Thu, 28 May 2020 00:54:12 GMT):
well... you should turn it in before it's due :)

rjones (Thu, 28 May 2020 00:54:20 GMT):
the TSC should review it on 25 June

peter_somogyvari (Thu, 28 May 2020 01:02:12 GMT):
:-) understood

amalcs23 (Thu, 28 May 2020 06:24:02 GMT):
Hi @peter_somogyvari What is mean by BIF? Is it Blockchain Integration Framework or Blockchain Interoperability Framework? How HL Catcus is defined?

peter_somogyvari (Thu, 28 May 2020 06:32:08 GMT):
@amalcs23 BIF is the old name of the project before it was approved to be in the greenhouse. It stood for `Blockchain Integration Framework`. Cactus came to be by way of being picked from a list of potential ones and got approved by the relevant Hyperledger teams (marketing and legal I believe). Is that what you mean by `How HL Catcus is defined?` ?

RafaelAPB (Thu, 28 May 2020 22:43:12 GMT):
Has joined the channel.

RafaelAPB (Thu, 28 May 2020 22:43:14 GMT):
Hey all! I've added a use case diagram (PR #156). In case of doubts feel free to ask!

JHamilton (Fri, 29 May 2020 03:17:28 GMT):
hey #cactus looks like i took a bad week to take off but glad to see so much going on :D I started an agenda draft on the confluence, would welcome other topics please edit directly with anything else you want to discuss. https://wiki.hyperledger.org/display/cactus/2020-06-01+Meeting+Agenda

dmproof (Sat, 30 May 2020 01:45:41 GMT):
Has joined the channel.

dmproof (Sat, 30 May 2020 01:52:41 GMT):
any suggestions on where to start for contributing as a dev? I really like the cactus concept and maybe I could lend a hand..

peter_somogyvari (Sat, 30 May 2020 02:22:25 GMT):
@dmproof Glad to hear that! Welcome to the community! There's a million things that needs doing, but you should work on something that you enjoy instead of consider menial. Do you prefer hands on code or design+diagrams? If you have a specific ledger that you are a fan of and would love to see it supported (and it isn't yet) then creating all-in-one docker images for that ledger is the way to start then you can write the connector plugin for it (and prove that it works with automated tests via the CI script) If that's your fancy there's always test coverage that needs increasing, but usually people are not stoked about working on that. :-) So just let me know if there's a particular topic that interests you and we can narrow it down from there.

rjones (Sat, 30 May 2020 05:01:52 GMT):
https://lf-landscape.netlify.app/category=hyperledger&format=card-mode&grouping=category&selected=hyperledger-cactus

dmproof (Sat, 30 May 2020 05:42:51 GMT):
hi peter, i prefer to code initially to learn more about how everything works. test coverage to get familiar with things never hurts either. is there any type of voting, request or in demand list for porting certain ledgers/block chains? and is there a list of currently supported blockchains/ledgers or ones being worked on? to me vechain or corda might be two interesting candidates. Are there any criteria for determining compatibility matrix of a ledger? Or just have to look at current example? . Id prefer to work on something code related that would benefit the project the most from a code perspective.

peter_somogyvari (Sat, 30 May 2020 06:05:57 GMT):
Sounds good. There is a process for getting changes approved, yes, there has to be at least two maintainers in approval of any given pull request. With that said, adding a new ledger to the list of supported ones is a very low-key change (thanks to the plugin architecture which we invested into heavily from early on) so adding support for new ledgers is not something I would expect to be opposed by any of the maintainers. With that said of course, you can always open a github issue with the feature request issue template and write it down there that you wish to add this contribution and before you invest any of your time and effort (which we very much value!) you would like to get preliminary confirmation that nobody has any problem with the idea/feature on a high level. This is just an optional step in case you want to be extra sure. I personally can tell your right now as one of the maintainers that I'd love to get new ledgers added. Corda is being worked on as we speak, but we can talk about vechain for sure, but here I also have to be honest and upfront about the fact that we are not yet production ready (we are a top level project within Hyperledger, but with a status of "incubation"). So at present when we add a supported ledger we only go as far as contract deployment through the plugin implementing the ledger so if you are looking to contribute a fully featured implementation and expect to use it to interop vechain with other ledgers right after the fact, that will have to wait a little longer (we'll definitely get there, but I'm trying not to over-promise or hype anything because we'd rather get the trust of people long term than get everyone excited and then disappear). Regarding the criteria for ledger compatibility: we want to support every ledger that at least has the capability to read and write block data and the ability to have smart contracts deployed on it. It's a pretty low bar that we set like that intentionally because the goal of the project is making as many ledgers as possible work together even if certain cross-ledger operations have to happen in some downgraded way because one ledger has a feature that the other does not (e.g. transaction privacy). The currently supported list of ledgers is evolving all the time (and note that by support I don't yet mean full support just that we've laid out some ground work and started working on it). Right now, the latest is this: we have besu and quorum ledger plugins set up with automated tests deploying contracts and making that functionality available through the API server as well through REST calls which are conveniently callable through the SDK which runs on NodeJS and browser as well. (I'm happy to show you around the relevant code components for all of this by the way, just let me know). What's in the works is corda and Fabric 1.4 (for both of those we start with an all-in-one docker image for enabling scalable test automation). So, circling back to code... if you want to get started with a vechain integration then my first question is, can you make an all-in-one style docker image that -upon the launching of the container- pulls up a testable (but not production ready by any means) ledger implementation? The requirements would be basically the same as for any other ledger, as an example you could take a look at what I wrote down for Jacob who is working on the exact same all-in-one image just for Corda: https://github.com/hyperledger/cactus/issues/143

peter_somogyvari (Sat, 30 May 2020 06:08:03 GMT):
Thanks for putting us out there! :-)

dmproof (Sat, 30 May 2020 07:14:35 GMT):
for the all in one docker image id have to see if I can do it, whatever ledger it would be. I am familiar with docker and most languages that nothing should be too far out of reach. I am not using any ledger currently outside some occasional fabric testing. corda and vechain were just two that I knew of and am somewhat more familiar with corda. Are there any popular or other interesting options you might have in mind to look at? or would vechain be a good place to start?

rjones (Sat, 30 May 2020 13:13:49 GMT):
you're doing the work!

peter_somogyvari (Sat, 30 May 2020 20:13:26 GMT):
If you ask me, for popular/interesting ones, personally, I would look at Burrow because that's the one I know of, but looking at Vechain (now that you brought it my attention) it does also look like a potential good candidate because they seem to have made good effort on containerization => https://github.com/vechain/thor#docker Not sure if that docker image of theirs meets all our requirements (no host binding of ports/volumes of any kind) but its definitely a good start when a ledger already has a single image that you can use to pull up a working/testable node of theirs. For some more interesting stuff (again just personal opinions) I would also want to explore how/what kind of integration could we do with DAML (which is a smart contract language not a ledger). I can imagine us being able to deploy smart contracts in both the ledger-native language and also in DAML (where the ledger is DAML-compatible). This could actually turn into a bigger piece of work because if it works then some or all of our existing ledger plugins could also be updated with DAML support. This one is sort of a wild card instead of just being about development one would have to also delve into the architecture/design first to make sure it all makes sense at the end of the day. Lastly, if you happen to know any ledgers that are out there and popular among developers, that's always a good candidate for us to have support for just based on the popularity. Anyway, bottom line is: If you look into adding vechain I think that's a great start.

dmproof (Sun, 31 May 2020 05:15:57 GMT):
thanks peter, ill look into it.

peter_somogyvari (Sun, 31 May 2020 18:25:37 GMT):
@dmproof Also let me know if there's any questions about the code itself, happy to demo+explain the test automation, the repo structure on a live call as well. We are in early days and I'm trying to find out what can we do to make it easier for people to on-board. Trying to avoid being a project with a big learning curve because it puts off a lot of people from getting started to begin with. So, if any questions, just ping me. ;-)

dmproof (Mon, 01 Jun 2020 06:24:33 GMT):
hi peter that would be great. i like all the ideas and potential and would like to explore daml possibilities as well. whenever you have the time to share let me know. im on a pst clock.

amalcs23 (Mon, 01 Jun 2020 08:06:10 GMT):
Hi @peter_somogyvari I am interested to go through HL Cactus Code. For that from where I start? Is there any proper file flow?

peter_somogyvari (Mon, 01 Jun 2020 15:15:18 GMT):
PST clock, same here :woo: If you drop me an email address in a direct message I can put something on the calendar.

peter_somogyvari (Mon, 01 Jun 2020 15:20:47 GMT):
@amalcs23 documentation is still being worked on but if you want to look at the code specifically, then I can recommend taking a look at one of the higher level test cases (can also run them). One like this for example: https://github.com/hyperledger/cactus/blob/master/packages/cactus-test-plugin-ledger-connector-quorum/src/test/typescript/integration/plugin-ledger-connector-quorum/deploy-contract/deploy-contract-via-web-service.ts

peter_somogyvari (Mon, 01 Jun 2020 15:21:40 GMT):
You can also run the CI script to set everything up as long as you are in an environment that can run shell scripts, on Windows it should work through WSL. CI script can be executed just by doing `./tools/ci.sh`

peter_somogyvari (Mon, 01 Jun 2020 15:51:45 GMT):
@amalcs23 Plus if you give me a few days, I'll have a PR ready with a somewhat updated documentation ;-)

xxds (Tue, 02 Jun 2020 05:25:34 GMT):
is there any demonstartion with example? simple asseset transfer is missing?

DOBEN (Tue, 02 Jun 2020 10:51:41 GMT):
Has joined the channel.

kumar89 (Tue, 02 Jun 2020 11:00:38 GMT):
Hi

DOBEN (Tue, 02 Jun 2020 13:25:06 GMT):
It might be a bit too early to discuss here how Cactus will implement escrow contracts for token/coin transfer, since Cactus seems to focus on non-fungible asset transfer between ledgers by locking the assets and then releasing a representation of it at another ledger at the moment. Nonetheless, I wanted to share some thoughts. My current understanding is that cactus wants to achieve an atomic inter-blockchain transfer of tokens/coins with escrow contracts in the future. That means that either the complete transfer is conducted or all participants are completely refunded and no partial transfer is done if an error occurs. I want to talk about this last step when an escrow contract is supposed to refund its locked up tokens to the original owner if the atomic inter-blockchain transfer failed for whatever reason. In case the escrow contract is written in solidity on the Ethereum blockchain and locks up Ether, I am not sure if this last transaction can always successfully refund the Ether (even after retrying to send the transaction several times). I am not referring to the problem that permissionless blockchains might fork and hence some transactions might not end up in the best chain. The problem that the Ether refund might fail forever is that the address where the Ether is sent to might be a smart contract on the Ethereum blockchain which has a malicious or accidentally malfunctioning receive() or fallback() function.

DOBEN (Tue, 02 Jun 2020 13:25:25 GMT):
In more detail, if the original address (the address used for locking up the Ether in the escrow contract) is an externally owned account (EOA), then it should be possible to always send Ether to that address. But if the original address is a contract account (CA), then there are several reasons why this external call could fail. If the receiving address is a contract, it could have a fallback()/receive() function implemented that simply throws an exception, once it gets called. Another reason for failure is running out of gas. https://fravoll.github.io/solidity-patterns/pull_over_push.html https://solidity.readthedocs.io/en/latest/common-patterns.html#withdrawal-from-contracts People recommend using the pull-over-push pattern to shift the risk associated with transferring Ether to the user or at least making sure that a failed Ether transfer does not block any code in the escrow contract after the failed Ether transaction has thrown an exception and every state change is reverted. This pattern is safer but it does not solve the problem that the escrow contract is unable to refund the Ether locked up. Since we cannot influence or check the code at the contract account (CA) before sending the Ether. We have to expect that some refund transactions will not be possible. That means that some Ether might end up being locked up forever in the escrow contract. It could be argued that it is the responsibility of the receiver to make sure that the address is able to receive the money back but there are also disadvantages on the escrow contract side and reasons why somebody might behave like this even though they loose money.

DOBEN (Tue, 02 Jun 2020 13:25:39 GMT):
1. We cannot guarantee that the inter-blockchain transfer is atomic which was the goal of cactus. 2. Somebody might just send very small amounts of Ether and does not care if the address is able to receive Ether back. The transaction still costs gas which might prevent such spamming in Ethereum but in other protocols with no gas cost this might be possible. It is a kind of spamming attack and the escrow contract ends up being a garbage collector. 2. There will be at least one person who accidentally locks up 100000 Ether and then cries and ask us for help. 3. People are curious to see how cactus or the other connected blockchains are behaving in such a scenario and playing around/ testing the limits of this feature. 4. It would be good to at least donate such money rather than locking it up. There might be some workaround to only allow EOA to lock up assets with “require(tx.origin == msg.sender)” but is it really that we want to disallow any CA to interact with the escrow contract. There are also very big warnings to use tx.origin in require expressions because of security issues. My second workaround that I though of was creating an escrow contract for every two parties that want to transfer the value among them and then use selfdestruct() (ether sent cannot be blocked in this function) to refund the ether but this also causes probably new issues. Additional comment: If the inter-blockchain transfer is successful and the escrow contract is supposed to pay out the locked ether to its new owner. The same problem occurs that some ether might be locked up forever. In Fabric: The escrow pay out might also have problems if the certification authority revoked the credentials of the user or if its certificate has been expired meanwhile or if the organisation of the user left the network. The user might be already removed from the user database when the refund transaction should take place.

cliveb (Wed, 03 Jun 2020 01:17:13 GMT):
@DOBEN My understanding, the initial goal of Cactus is not to guarantee that the inter-blockchain transfer is atomic. Rather, Cactus design principle is to prevent double spending where possible. Cactus is in charge of the inter-blockchain bridge not the blockchain databases on either of the blockchain integration framework. An analogy, Leonhard Euler proved there was no way to solve the Seven Bridges of Konigsberg, the mathematical rigor laying the foundation for graph theory underpinning networked systems today. Unlike other areas of blockchain, few are building resilient secure blockchain integration frameworks. Cloud databases use Web 2.0 technologies to interface databases, built with native software components and native APIs, typically requiring layer security in depth, because native code fails on storage reclamation and can expose private keys, making integrations easy to hack. Creating a far greater gap for inter-blockchain transfers to solve moving forward with Web 3.0 technologies. Making all the world of difference to resilient secure inter-blockchain reliability.

cliveb (Wed, 03 Jun 2020 01:17:13 GMT):
@DOBEN My understanding, the initial goal of Cactus is not to guarantee that the inter-blockchain transfer is atomic. Rather, Cactus design principle is to prevent double spending where possible. Cactus is in charge of the inter-blockchain bridge not the blockchain databases on either of the blockchain integration framework. An analogy, Leonhard Euler proved there was no way to solve the Seven Bridges of Konigsberg, the mathematical rigor laying the foundation for graph theory underpinning networked systems today. Unlike other areas of blockchain, few are building resilient secure blockchain integration frameworks. Cloud databases use Web 2.0 technologies to interface databases, built with native software components and native APIs, typically requiring layer security in depth, because native code fails on storage reclamation and can expose private keys, making integration easy to hack. Creating a far greater gap for inter-blockchain transfers to solve moving forward with Web 3.0 technologies. Making all the world of difference to resilient secure inter-blockchain reliability.

cliveb (Wed, 03 Jun 2020 01:17:13 GMT):
@DOBEN My understanding, the initial goal of Cactus is not to guarantee that the inter-blockchain transfer is atomic. Rather, Cactus design principle is to prevent double spending where possible. Cactus is in charge of the inter-blockchain bridge not the blockchain databases on at least one side of the blockchain integration framework. An analogy, Leonhard Euler proved there was no way to solve the Seven Bridges of Konigsberg, the mathematical rigor laying the foundation for graph theory underpinning networked systems today. Unlike other areas of blockchain, few are building resilient secure blockchain integration frameworks. Cloud databases use Web 2.0 technologies to interface databases, built with native software components and native APIs, typically requiring layer security in depth, because native code fails on storage reclamation and can expose private keys, making integration easy to hack. Creating a far greater gap for inter-blockchain transfers to solve moving forward with Web 3.0 technologies. Making all the world of difference to resilient secure inter-blockchain reliability.

cliveb (Wed, 03 Jun 2020 01:17:13 GMT):
@DOBEN My understanding, the initial goal of Cactus is not to guarantee that the inter-blockchain transfer is atomic. Rather, Cactus design principle is to prevent double spending where possible. Cactus is in charge of the inter-blockchain bridge not the blockchain databases on either side of the blockchain integration framework. An analogy, Leonhard Euler proved there was no way to solve the Seven Bridges of Konigsberg, the mathematical rigor laying the foundation for graph theory underpinning networked systems today. Unlike other areas of blockchain, few are building resilient secure blockchain integration frameworks. Cloud databases use Web 2.0 technologies to interface databases, built with native software components and native APIs, typically requiring layer security in depth, because native code fails on storage reclamation and can expose private keys, making integration easy to hack. Creating a far greater gap for inter-blockchain transfers to solve moving forward with Web 3.0 technologies. Making all the world of difference to resilient secure inter-blockchain reliability.

cliveb (Wed, 03 Jun 2020 01:17:13 GMT):
@DOBEN My understanding, the initial goal of Cactus is not to guarantee that the inter-blockchain transfer is atomic. Rather, Cactus design principle is to prevent double spending where possible. Cactus is in charge of the inter-blockchain bridge not the blockchain databases on either side of the blockchain integration framework. An analogy, Leonhard Euler proved there was no way to solve the Seven Bridges of Konigsberg, the mathematical rigor laying the foundation for graph theory underpinning networked systems today. Unlike other areas of blockchain, few are building resilient secure blockchain integration frameworks. Cloud databases use Web 2.0 technologies to interface databases, built with native software components and native APIs, typically requiring layer security in depth, because native code fails on storage reclamation and can expose private keys, making integration easy to hack. Creating a far greater gap for inter-blockchain transfers to solve moving forward with Web 3.0 technologies. Making all the world of difference to resilient secure inter-blockchain reliability. A coda. Log everything, transfers, plugins, latency, ops, across the Cactus blockchain integration framework.

cliveb (Wed, 03 Jun 2020 01:17:13 GMT):
@DOBEN My understanding, the initial goal of Cactus is not to guarantee that the inter-blockchain transfer is atomic. Rather, Cactus design principle is to prevent double spending where possible. Cactus is in charge of the inter-blockchain bridge not the blockchain databases on either side of the blockchain integration framework. An analogy, Leonhard Euler proved there was no way to solve the Seven Bridges of Konigsberg, the mathematical rigor laying the foundation for graph theory underpinning networked systems today. Unlike other areas of blockchain, few are building resilient secure blockchain integration frameworks. Cloud databases use Web 2.0 technologies to interface databases, built with native software components and native APIs, typically requiring layered security in depth, because native code fails on storage reclamation and can expose private keys, making integration easy to hack. Creating a far greater gap for inter-blockchain transfers to solve moving forward with Web 3.0 technologies. Making all the world of difference to resilient secure inter-blockchain reliability. A coda. Log everything, transfers, plugins, latency, ops, across the Cactus blockchain integration framework.

DOBEN (Wed, 03 Jun 2020 02:03:50 GMT):
Hello Cactus team, Thank you very much for all the hard work done so far and making the project open source. There are some more thoughts/questions that I want to share. I apologize if some of these issues have already been discussed. Thank you. If I can help in any of these tasks, please let me know. I was wondering if people would like to have an “emergency break feature” in cactus. In case the livelihood of one of the connected blockchains reduces below a specific threshold, the emergency break can be activated to prevent any further asset transfer out of this blockchain to keep all blockchains alive. The emergency break can be deactivated if enough assets have been returned to the affected blockchain. The emergency break could be either activated/deactivated by a trusted external party or could be hard coded and automatically activate in case a specific threshold is reached. How to define and measure the livelihood of a blockchain that I am not really sure about. If all tokens/assets of the total supply value are tradeable/spendable in the network, then the livelihood of the network is 100%. But we don’t know how many of the tokens are locked up/ burned in addresses that nobody has access anymore because e.g. the private keys got lost. Should the livelihood of a blockchain be defined with respect to how many transactions are done per second with that token?

DOBEN (Wed, 03 Jun 2020 02:04:08 GMT):
Another topic: Do people have other incentives to lock up things (in particular data) in an escrow contract without actually being interested in inter-blockchain transfers? I am not a lawyer, so please ask an expert on this topic. Under the General Data Protection Regulation (GDPR) in Europe, the “controller “ not the “processor” of sensitive data is liable for it and might be punished in court for any non-compliance with GDPR. Under the “Digital Millennium Copyright Act” in the USA, the possession of some data is illegal e.g. cases of illegal primes. There might be laws and regulations in some countries that if people lock up data in escrow contracts, they are not in control of this data anymore and hence, avoid legal punishment if they were in the possession of such sensitive/illegal data beforehand. Some people might therefore try to lock up such data in escrow contracts. This is a problem nobody can solve and applies to probably every distributed immuatable ledger, I assume.

DOBEN (Wed, 03 Jun 2020 02:04:33 GMT):
Another topic: There was this discussion about “burning of tokens” in one of the cactus papers. I agree that in general it is not advised to do so if connected to the cactus network since cactus does not want to jeopardize the “livelihood “of any of the connected chains (If all the tokens are burned of one chain and no new tokens are mined in that protocol of that chain then the chain is literally dead.). Nonetheless, if someone is still using this pattern to interact with cactus, what would be the recommended implementation to “burn tokens”? Should there be some recommendations in the white paper in the future? I saw at least two different implementations, so I was wondering what are the pros and cons and which is the recommended one when interacting with cactus? 1. Implementation: Tokens are sent to the address of the coinbase/generation transaction in the genesis block (the address of the miner that mined the genesis block, this is the address where the reward for mining the block is sent to). 1.1. Additional comments with respect to Bitcoin: Since most people in the bitcoin community assume that Satoshi does not know the private key of the address of the coinbase transaction in the genesis block, all coins collected in that address are burned since nobody has access to the private key to reclaim them. It is not proven if or if not Satoshi has the private key of that special address. 1.2 Additional comments with respect to Ethereum: I think it is proven that nobody knows the private key of the that coinbase address in the genesis block because it was set to the special address “00000.......000000”. 2. Implementation: Tokens are subtracted from the user account as well as from the total token supply value.

DOBEN (Wed, 03 Jun 2020 02:09:09 GMT):

Suggestions white paper.pdf

DOBEN (Wed, 03 Jun 2020 02:09:20 GMT):
There are some suggestions with respect to the white paper

DOBEN (Wed, 03 Jun 2020 02:09:25 GMT):
Thank you.

cliveb (Wed, 03 Jun 2020 17:48:34 GMT):
[web2 vs web3] ServiceNow page illustrates cloud database integration security operations built without trends in blockchain database crypto/security. https://docs.servicenow.com/bundle/orlando-security-management/page/product/security-operations/concept/understanding-secops.html#understanding-secops

cliveb (Wed, 03 Jun 2020 17:48:34 GMT):
[web2 vs web3] ServiceNow page illustrates cloud database integration security operations built without trust in blockchain database crypto/security. https://docs.servicenow.com/bundle/orlando-security-management/page/product/security-operations/concept/understanding-secops.html#understanding-secops

z3100 (Thu, 04 Jun 2020 03:29:25 GMT):
Has joined the channel.

stone-ch (Thu, 04 Jun 2020 07:57:00 GMT):
Has joined the channel.

JHamilton (Fri, 05 Jun 2020 21:35:20 GMT):
Hello @DOBEN thank you for all the insightful feedback. we are reviewing how to address. as these points are quite deep it would be useful to discuss live. if agreeable we could make time in an upcoming contributors session to cover if the timing is convenient for you? otherwise perhaps we can coordinate a special session that works across various timezones

JHamilton (Fri, 05 Jun 2020 21:36:08 GMT):
https://lists.hyperledger.org/g/cactus/calendar

VipinB (Sun, 07 Jun 2020 19:18:31 GMT):
I have announced this talk for the 10th at 12 noon EDT. @peter_somogyvari we will expect you on the call. I will forward meeting invite.

DOBEN (Mon, 08 Jun 2020 00:22:14 GMT):
Hello JHamilton, good idea. I will join next public meeting. See you there tomorrow.

DOBEN (Mon, 08 Jun 2020 00:26:57 GMT):
I joined the last two zoom meetings already but I used a different username in Zoom, so I updated my user name info in the chat here to avoid confusion.

DOBEN (Mon, 08 Jun 2020 00:42:17 GMT):
Hello cliveb, fair enough point and yes I agree that cactus is for now probably focusing on building the link/bridge between the blockchains by locking/unlocking assets to prevent double-spending (meaning preventing that a representation of the same asset exists in several blockchains and potentially been spent in several blockchains). It is already a quite difficult task and probably won’t get easier in the future as you mentioned. Let's see where it will develop to in the future because if token/value assets/fungible assets are include, things like escrow contracts might become important. I quite personally like the reference to the Seven Bridge of Koenigsberg problem so.

sfuji822 (Mon, 08 Jun 2020 01:06:13 GMT):
Hi doben,

sfuji822 (Mon, 08 Jun 2020 01:07:35 GMT):
Hi @DOBEN ,

sfuji822 (Mon, 08 Jun 2020 01:51:48 GMT):
Hi @DOBEN , first of all thanks for your feedback.I believe the issue raised in your comment is not easy to solved by generic solutions. As one of core contributor of Cactus, I want to keep a room for implement escrow transaction which was introduced in my paper DOI: 10.1109/IOTSMS48152.2019.8939267 or https://www.google.co.jp/url?q=https://www.fujitsu.com/global/documents/about/resources/publications/fstj/archives/vol55-5/paper11.pdf&sa=U&ved=2ahUKEwi2weTpivHpAhUQyYsBHUx_Bo8QFjAAegQIARAB&usg=AOvVaw1pEtaW-3bqrSdQXXenHMye . We design Cactus architecture to allow Business Logic Plugin to provide escrow trade service by interacting with Ledgers . Fujitsu'prototype system showed feasibility and acceptace from real market in some PoCs in Japan. Iwould like to continue such deep discussion in mailing list.

DOBEN (Mon, 08 Jun 2020 01:54:59 GMT):
Thanks for the paper link, I will read it until tomorrow to understand the implementation better. And I am happy to discuss further tomorroe

peter_somogyvari (Mon, 08 Jun 2020 23:10:27 GMT):
Slightly off-topic because it does not affect Cactus/NodeJS (I believe) but it's still worth mentioning as a good example/reminder why we need the `secure by default` design principle so much. :-) https://twitter.com/__agwa/status/1270054737317113857

cliveb (Tue, 09 Jun 2020 01:00:52 GMT):
Hello Peter, does secure by default design principle mean making the P in the Cactus CAP secure by default? Or more specifically, implementation making the Cactus/NodeJS plugins have no ambient authority; can interact only with the objects to which they have been granted access explicitly? (if so I might be tracking some useful contributions to point toward).

cliveb (Tue, 09 Jun 2020 01:00:52 GMT):
Hello Peter, does secure by default design principle mean making the P in the Cactus CAP secure by default? Or more specifically, making the Cactus/NodeJS plugins have no ambient authority; can interact only with the objects to which they have been granted access explicitly? (if so I might be tracking some useful contributions to point toward).

stone-ch (Tue, 09 Jun 2020 01:24:05 GMT):
Hi all, I am a member of TWGC(Technical Working Group China), now leading the translation of Fabric documents, I am interested in Cactus very much after reading the whitepaper, so I decided to translate the whitepaper into Chinese. After the whitepaper, I also want to translate other documents of Cactus, such as tutorial and so on, just like Fabric.Wish Cactus will be better and better.

JHamilton (Tue, 09 Jun 2020 01:31:57 GMT):
Thank you so much for your contribution(s) and clarifying the involvement! Perhaps we should find a way to flag which documents are in a good state for translation or good points in time for translation, as some are undergoing a lot of change still

stone-ch (Tue, 09 Jun 2020 01:38:04 GMT):
That's a good idea, I saw there still have some issues and PRs for whitepaper, but I will translate a first version of the whitepaper, and then update the translation when the whitepaper updated.

stone-ch (Tue, 09 Jun 2020 01:40:48 GMT):
After the whitepaper, I will translate the tutorial if I can run an example follow the documents.And

stone-ch (Tue, 09 Jun 2020 01:42:48 GMT):
After the whitepaper, I will translate the tutorial if I can run an example follow the documents.And the translation will be improved with the official version.

JHamilton (Tue, 09 Jun 2020 01:59:18 GMT):
sounds like a plan, thanks again for your contributions to make Cactus better and more visible!

peter_somogyvari (Tue, 09 Jun 2020 02:11:14 GMT):
@amalcs23 FYI: https://github.com/hyperledger/cactus/pull/168

cliveb (Tue, 09 Jun 2020 02:46:08 GMT):
@DOBEN another opportunity to discuss Cactus architecture futures, is biweekly ArchWG. Last weeks notes https://wiki.hyperledger.org/display/AWG/2020-06-03

cliveb (Tue, 09 Jun 2020 02:46:08 GMT):
@DOBEN another opportunity to discuss Cactus architecture futures, perhaps requirements for other HL projects. is biweekly ArchWG. Last weeks notes https://wiki.hyperledger.org/display/AWG/2020-06-03

cliveb (Tue, 09 Jun 2020 02:46:08 GMT):
@DOBEN another opportunity to discuss Cactus architecture futures, perhaps requirements for other HL projects, is biweekly ArchWG. Last weeks notes https://wiki.hyperledger.org/display/AWG/2020-06-03

JHamilton (Tue, 09 Jun 2020 03:17:30 GMT):
#cactus syndicating mailing list request for input on GMT friendly contributor call (additional to existing call with maintainers) _The current Cactus contributors call is Tuesdays 2-3am GMT, which works well for maintainers from America & Japan. However, we see lots of community interest and we are trying to judge how to best engage with those near GMT timezones. Please respond if you would regularly join a contributor call on GMT timezone friendly window and what timeframes would comfortably work for you (how early vs. how late). Thank you._

peter_somogyvari (Tue, 09 Jun 2020 03:33:38 GMT):
FYI: Just sent this PR with the git guidance I promised during our earlier call from last week. https://github.com/hyperledger/cactus/pull/169

rjones (Tue, 09 Jun 2020 17:25:36 GMT):
That is an awesome guide

DOBEN (Thu, 11 Jun 2020 07:35:41 GMT):
Great resource! Thank you for pointing it out.

DOBEN (Thu, 11 Jun 2020 07:47:28 GMT):
There is a Chainstack and LayerX webinar about "Interoperability on Corda and beyond". Not sure about the quality of the talk but if people are working on corda then it might be worth to check out. https://chainstack.com/webinar-interoperability-and-corda/

amalcs23 (Thu, 11 Jun 2020 10:27:22 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=5izRytwk4gjfW8Xq4) @peter_somogyvari Is there any updation for this?

amalcs23 (Thu, 11 Jun 2020 10:34:25 GMT):
Hi @peter_somogyvari I am try to run the simple-asset-transfer example. I have some doubts regarding the setup. Is there any OS( Ubuntu 18.04) dependency for running this example? From the documentation, "Note: Fabric SDK has stricter engine requirements (npm < 6.0 & node < 9.0)" Which Node and npm version is required for running Fabric SDK? Thank you

peter_somogyvari (Thu, 11 Jun 2020 17:06:42 GMT):
@amalcs23 Ooops, sorry, had to push that back yet again, but today is shaping up to be a great day to do it so if everything goes well there will be something by tomorrow morning.

peter_somogyvari (Thu, 11 Jun 2020 18:52:38 GMT):
Hi @amalcs23 That one should definitely work on Ubuntu 18.04 (we used to have CI coverage for it). On the other hand, things have moved on fast from the simple-asset-transfer example and now we are working on the merged architecture with a codebase that's new and improved compared to previous codebase. I'm working on the documentation right now, but to get things going I would ask you to first just try to pull the latest master branch contents and then run the CI script under `./tools/ci.sh` and if that fails with something then paste back the error here.

peter_somogyvari (Thu, 11 Jun 2020 20:32:00 GMT):
@amalcs23 Check this out: https://github.com/petermetz/blockchain-integration-framework/blob/docs/partial-issue-46-build-md/BUILD.md It allows you to get going with the setup and run the existing tests related to different ledgers. Note: in the new architecture the asset transfer example is not yet in existence but you can already see how contract deployment will work on a per ledger basis for example.

peter_somogyvari (Thu, 11 Jun 2020 20:51:49 GMT):
Thank you @DOBEN I've just signed up, looks like it's worth checking out! Also, I added your proposal on the meeting agenda right in the beginning, for Monday, apologies once again for hogging the line last time!

amalcs23 (Fri, 12 Jun 2020 09:13:49 GMT):
Hi @peter_somogyvari Thanks for your response. When I run the CI script ./tools/ci.sh, There is no error for me even I am using Debian OS.

rjones (Fri, 12 Jun 2020 16:32:39 GMT):
@peter_somogyvari Take a look at: https://tinyurl.com/yb3hyhlq

rjones (Fri, 12 Jun 2020 16:33:18 GMT):
Or this: https://tinyurl.com/yb6zd8go

peter_somogyvari (Fri, 12 Jun 2020 17:21:09 GMT):
@amalcs23 so just to clarify, does it get to the end where it prints `SUCCESS` and the amount of seconds it took to run?

peter_somogyvari (Fri, 12 Jun 2020 17:23:59 GMT):
Awesome! Bookmarking both of these right now. :-)

peter_somogyvari (Fri, 12 Jun 2020 17:25:20 GMT):
I should probably know this but what does `REI` stands for? It's the name of one of the charts

rjones (Fri, 12 Jun 2020 18:13:44 GMT):
If you scroll down, they explain it

peter_somogyvari (Fri, 12 Jun 2020 18:17:26 GMT):
(facepalm) thank you :-)

peter_somogyvari (Fri, 12 Jun 2020 18:20:33 GMT):
Is there any way for me to customize the way the LOC metrics are calculated? It says that I added ~80k LOC, but most of that will be generated package-lock.json files for NodeJS (which we must store under version control for stable builds despite them being generated).

rjones (Fri, 12 Jun 2020 18:26:39 GMT):
probably?

rjones (Fri, 12 Jun 2020 18:27:47 GMT):
I'm playing around with the filters to see what I can do

peter_somogyvari (Fri, 12 Jun 2020 18:29:03 GMT):
Cheers, I'm also tinkering with it now too (figured out that I can log in with LFID)

rjones (Fri, 12 Jun 2020 18:29:47 GMT):
are you able to edit your profile?

peter_somogyvari (Fri, 12 Jun 2020 18:30:22 GMT):
No, the only option I have when hovering over the user icon is 'Sign out' :D

amalcs23 (Mon, 15 Jun 2020 05:24:52 GMT):
@peter_somogyvari This is my output

amalcs23 (Mon, 15 Jun 2020 05:24:52 GMT):
@peter_somogyvari This is my output ++ date +%s + ENDED_AT=1590993338 + runtime=2028 ++ date +%FT%T%z + echo '2020-06-01T12:05:38+0530 [CI] SUCCESS - runtime=2028 seconds.' 2020-06-01T12:05:38+0530 [CI] SUCCESS - runtime=2028 seconds. + exit 0

peter_somogyvari (Mon, 15 Jun 2020 18:01:03 GMT):
@amalcs23 Great, that's the expected output, so you are good to go at this point to run all the individual tests or do development, etc. Good to know it also works on Debian not just Ubuntu (suspected it to begin with but did not have evidence until now)

JHamilton (Tue, 16 Jun 2020 02:07:45 GMT):
HERE!

nomorealias (Wed, 17 Jun 2020 22:46:05 GMT):
Has joined the channel.

RafaelAPB (Fri, 19 Jun 2020 19:32:14 GMT):
@peter_somogyvari I realized the test ledger needs some more flexibility. I should be able to take care of #191, if that's fine by you

peter_somogyvari (Fri, 19 Jun 2020 19:55:17 GMT):
@RafaelAPB Sounds good to me, I re-assigned the issue under your name (let me know if you need help of course)

RafaelAPB (Fri, 19 Jun 2020 20:50:32 GMT):
@peter_somogyvari I thought the way to pass arguments to docker run was through the startupOptions object passed to docker.run, but it gives me (HTTP code 400) unexpected - starting container with non-empty request body was deprecated since API v1.22 and removed in v1.24. Any thoughts on those?

peter_somogyvari (Fri, 19 Jun 2020 20:51:53 GMT):
@RafaelAPB To clarify, are you working with the `dockerode` library?

RafaelAPB (Fri, 19 Jun 2020 20:53:29 GMT):
Yes

peter_somogyvari (Fri, 19 Jun 2020 20:55:53 GMT):
Okay, good, can you paste in the code here that you are running when you get that error? Best with the triple single quote sintax in a new line

RafaelAPB (Fri, 19 Jun 2020 20:57:40 GMT):
https://gist.github.com/RafaelAPB/9b41fd24faf8eefbaa5cceef762d90b0

rjones (Fri, 19 Jun 2020 20:57:43 GMT):
Has left the channel.

RafaelAPB (Fri, 19 Jun 2020 20:58:07 GMT):
I just passed two new options to docker.run

peter_somogyvari (Fri, 19 Jun 2020 21:05:04 GMT):
Oh I see now. I think you want to use the cmd array (second parameter of the run method). That's how you can inject the args after that deprecation that the error message mentions as well. Off-topic: If you reply through the thread it will be much easier for others (or yourself) to follow the discussion later. Not mandatory of course, but it does make it easier in my personal opinion to scan the chat for information historically

hartm (Fri, 19 Jun 2020 23:27:28 GMT):
I've added a first draft of our quarterly report in the wiki. Please feel free to edit as you see fit. Thanks!

chipleinen (Sun, 21 Jun 2020 00:31:42 GMT):
Has joined the channel.

pouya (Sun, 21 Jun 2020 09:59:20 GMT):
Has joined the channel.

JHamilton (Mon, 22 Jun 2020 14:26:02 GMT):
Looks great Hart, thank you!

peter_somogyvari (Mon, 22 Jun 2020 20:24:43 GMT):
FYI: Created the draft meeting agenda for call tonight/today: https://wiki.hyperledger.org/display/cactus/2020-06-22+Cactus+Meeting+Agenda Please add anything additional that we should be discussing. I put the quarterly report right on top to make sure we cover that.

cliveb (Tue, 23 Jun 2020 00:47:48 GMT):
Added to wiki agenda - isolation for plugins and observable security: possible discuss improvements to docs whitepaper?

peter_somogyvari (Tue, 23 Jun 2020 03:13:02 GMT):
Is it just me or the Hyperledger Confluence is experiencing some technical issues right now? I can start drafting a new meeting agenda document but when trying to save it doesn't work: > The editor didn't load this time > The connection timed out. If it happens again, speak to your Confluence admin. You may be using a proxy server that prevents WebSocket connections.

JHamilton (Tue, 23 Jun 2020 03:20:57 GMT):
I had a similar issue where i had created a page where i wasn't logged in (let me create the page anonymous) but then after i signed in it wouldn't let me save the page i had created). had to start a new page post login and copy content in

JHamilton (Tue, 23 Jun 2020 03:21:31 GMT):
sometimes despite telling Confl to keep me logged in it logs me out, maybe something similar?

peter_somogyvari (Tue, 23 Jun 2020 03:23:14 GMT):
Reloaded the page but it still shows me as logged in. Will try explicit logout/login, thanks for the tip!

JHamilton (Tue, 23 Jun 2020 03:24:04 GMT):
i guess it's only as good as the "did you try rebooting" :P

JHamilton (Tue, 23 Jun 2020 03:24:24 GMT):
happy to create a page if it helps... see Hart created minutes ~20 min ago

peter_somogyvari (Tue, 23 Jun 2020 03:25:53 GMT):
:DD Yeah, I'm about at the point where I'll try rebooting because even after logging out and then logging back in it shows the same error. Yes please, if you could create it that would be great. I just wanted to make sure we have Clive's discussion item as the first one in the queue because we didn't get to it tonight.

JHamilton (Tue, 23 Jun 2020 03:26:13 GMT):
(y)

peter_somogyvari (Tue, 23 Jun 2020 03:26:22 GMT):
2020-06-30 Cactus Meeting Agenda 1. Discuss isolation for plugins and observable security: possible improvements to docs whitepaper? 2. ... 3. Pull request (has to be at the end because PR discussions are infinite)

JHamilton (Tue, 23 Jun 2020 03:29:05 GMT):
https://wiki.hyperledger.org/display/cactus/2020-06-29+Cactus+Meeting+Agenda

peter_somogyvari (Tue, 23 Jun 2020 03:29:47 GMT):
Oops, I had the wrong date, my bad. :-)

peter_somogyvari (Tue, 23 Jun 2020 03:29:53 GMT):
Thank you!

amalcs23 (Tue, 23 Jun 2020 09:44:03 GMT):
Hi @peter_somogyvari How can I start individual test or development? I am little bit confuse.

kulkarnikk (Tue, 23 Jun 2020 09:44:28 GMT):
Has left the channel.

peter_somogyvari (Tue, 23 Jun 2020 17:23:59 GMT):
@amalcs23 Depends on what would you like to do exactly. Feature or a bug fix? Adding some kind of plugin?

JHamilton (Thu, 25 Jun 2020 01:34:31 GMT):
hey Cactus community! making everyone aware that there are now weekly alternating Western & Eastern Hemisphere friendly contributor sessions! https://lists.hyperledger.org/g/cactus/calendar the weekly maintainers session is still open to all but we wanted to add these new contributor sessions to provide more overlap for interested participants that align better w/ ~GMT

amalcs23 (Thu, 25 Jun 2020 06:35:44 GMT):
Hi @peter_somogyvari Right now I want to test how two blockchain platform Fabric and Quorum communicate. for that I need your help. Thank You

peter_somogyvari (Thu, 25 Jun 2020 06:53:16 GMT):
@amalcs23 Yeah about that. The new version of the fabric connector is still under development unfortunately. We are waiting on this to be resolved and then it can be added: https://github.com/hyperledger/cactus/issues/132 (in case you want to track the progress/ get updates as we go, etc)

rjones (Thu, 25 Jun 2020 18:22:05 GMT):
Has joined the channel.

rjones (Thu, 25 Jun 2020 18:22:05 GMT):
@peter_somogyvari how can I help you publish to dockerhub?

rjones (Thu, 25 Jun 2020 18:23:18 GMT):
I added you here: https://hub.docker.com/orgs/hyperledger/teams/cactus

peter_somogyvari (Thu, 25 Jun 2020 18:23:39 GMT):
@rjones I just need to know if there's any specific image registry mandated by the org (HL) or can we go with DockerHub/Github Image Registry? If we are free to go with one of those, then I have all I need (I know how to do it just wanted to make sure whatever we do is compliant with guidelines)

peter_somogyvari (Thu, 25 Jun 2020 18:24:06 GMT):
> I added you here: https://hub.docker.com/orgs/hyperledger/teams/cactus

peter_somogyvari (Thu, 25 Jun 2020 18:24:16 GMT):
Awesome, thank you very much, I think that's all I need then :-)

rjones (Thu, 25 Jun 2020 18:24:33 GMT):
OK. I think I need to add you as an admin to the repo? not sure.

peter_somogyvari (Thu, 25 Jun 2020 18:25:17 GMT):
Could be, I'm not sure either TBH. If I hit a permission snag I can just ping you asking for the admin, not a problem.

rjones (Thu, 25 Jun 2020 18:25:36 GMT):
OK. I'm clicking around and stuff

rjones (Thu, 25 Jun 2020 18:26:22 GMT):
You're an admin here: https://hub.docker.com/repository/docker/hyperledger/cactus/ and I think it should work?

peter_somogyvari (Thu, 25 Jun 2020 18:26:31 GMT):
Checking now

rjones (Thu, 25 Jun 2020 18:27:04 GMT):
OK. If you need multiple images - I can do that. It's unclear to me if you need a bunch of images, or only one.

peter_somogyvari (Thu, 25 Jun 2020 18:27:53 GMT):
It will definitely be a bunch of images. Just one for cactus itself, but there are others that are for integration tests/demos/etc.

rjones (Thu, 25 Jun 2020 18:28:11 GMT):
OK. I think, just tell me what new ones you need?

rjones (Thu, 25 Jun 2020 18:28:42 GMT):
I think you can enable auto-builds, but I think everyone that did that moved away

peter_somogyvari (Thu, 25 Jun 2020 18:30:17 GMT):
Will do, now that we have established the "ground rules" I can actually move the Dockerfile(s) into the Cactus codebase and once that's done (PRs will have to be accepted first) then I'll ping you so we can set it up (assuming I can't do it myself, but with admin rights I can probably just do it all by myself, but let's see how it goes)

peter_somogyvari (Thu, 25 Jun 2020 18:30:33 GMT):
Thanks for the help!

peter_somogyvari (Fri, 26 Jun 2020 02:13:21 GMT):
> OK. I think, just tell me what new ones you need? @rjones Now I see what you meant and I definitely need 4 of them, sorry for not realizing this earlier! Here's the list of repos I need: cactus-fabric-all-in-one cactus-corda-all-in-one cactus-quorum-all-in-one cactus-besu-all-in-one I prefixed them all with `cactus` because that way it's not confusing anybody looking at the besu one for example (without the prefix one could think that the besu-all-in-one image is maintained by the besu team, but it is not)

rjones (Fri, 26 Jun 2020 05:02:21 GMT):
https://hub.docker.com/orgs/hyperledger/teams/cactus/permissions

peter_somogyvari (Fri, 26 Jun 2020 05:04:00 GMT):
Thank you very much!

amalcs23 (Fri, 26 Jun 2020 09:59:08 GMT):
Right now I am not able to run the simple-asset-transfer example?

peter_somogyvari (Fri, 26 Jun 2020 16:34:54 GMT):
You can probably still run the old one, if that's what you want to do, but the new one is coming soon so I'd recommend holding off with the effort until that happens. The reason I'm recommending this is because the foundations/principles will be pretty much the same in the new code but the mechanics and the implementation will be completely new. So if you invest your time into reading/understanding the old examples/code then you'll have to re-do some of that effort in a few weeks when the new example comes out doing the same thing. If you still want to go ahead with the old examples I'm happy to take a deeper look into what went wrong with your setup (or if somehow the example got broken since March when I last demoed it) . Just let me know

amalcs23 (Mon, 29 Jun 2020 06:43:30 GMT):
Thank you @peter_somogyvari

amalcs23 (Mon, 29 Jun 2020 08:49:59 GMT):
Hi @peter_somogyvari When I try to setup Quorum blockchain I got one error like this fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.11/main: temporary error (try again later) WARNING: Ignoring APKINDEX.70f61090.tar.gz: No such file or directory fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/x86_64/APKINDEX.tar.gz ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.11/community: temporary error (try again later) WARNING: Ignoring APKINDEX.ca2fea5b.tar.gz: No such file or directory

amalcs23 (Mon, 29 Jun 2020 08:49:59 GMT):
Hi @peter_somogyvari When I try to setup Quorum blockchain I got one error like this Command is: npm run quorum:api:build fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.11/main: temporary error (try again later) WARNING: Ignoring APKINDEX.70f61090.tar.gz: No such file or directory fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/x86_64/APKINDEX.tar.gz ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.11/community: temporary error (try again later) WARNING: Ignoring APKINDEX.ca2fea5b.tar.gz: No such file or directory

peter_somogyvari (Mon, 29 Jun 2020 16:51:30 GMT):
@amalcs23 That's a weird issue. Best guess is that the alpine linux CDN was down or that something strange is going on with your local docker installation because I literally just now ran that command and worked fine: ```sh $ npm run quorum:api:build > @hyperledger-labs/blockchain-integration-framework.examples.simple-asset-transfer@0.1.0 quorum:api:build /.../contribs/Accenture-BIF/core/examples/simple-asset-transfer > docker build --no-cache -t federation/qserver -f quorum/api/Dockerfile quorum Sending build context to Docker daemon 452.6kB Step 1/6 : FROM node:10-alpine 10-alpine: Pulling from library/node cbdbe7a5bc2a: Already exists 95feee427958: Pull complete 4123295e9f39: Pull complete a59140832df1: Pull complete Digest: sha256:177cdb2546eb321b7127aa1c45353c5b778959c9e30da29570ff85098786d776 Status: Downloaded newer image for node:10-alpine ---> 6bf4087f2679 Step 2/6 : RUN apk update && apk upgrade && apk add --update netcat-openbsd && rm -rf /var/cache/apk/* ---> Running in e072ec0157bd fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/x86_64/APKINDEX.tar.gz v3.11.6-90-g318b6c3504 [http://dl-cdn.alpinelinux.org/alpine/v3.11/main] v3.11.6-90-g318b6c3504 [http://dl-cdn.alpinelinux.org/alpine/v3.11/community] OK: 11271 distinct packages available (1/1) Upgrading ca-certificates-cacert (20191127-r1 -> 20191127-r2) OK: 7 MiB in 16 packages (1/2) Installing libbsd (0.10.0-r0) (2/2) Installing netcat-openbsd (1.130-r1) Executing busybox-1.31.1-r9.trigger OK: 7 MiB in 18 packages Removing intermediate container e072ec0157bd ---> 47a1f029a82a Step 3/6 : ADD ./api /src ---> 9b94170a5cf0 Step 4/6 : ADD ./contracts /contracts ---> b3aeb066ba49 Step 5/6 : WORKDIR /src ---> Running in a9a28fb066a2 Removing intermediate container a9a28fb066a2 ---> 18d1e7942b28 Step 6/6 : CMD sh -c './scripts/wait-for.sh -t 6000 qserver1:5050 -- node index.js' ---> Running in 2864f70390eb Removing intermediate container 2864f70390eb ---> 7460af4bd323 Successfully built 7460af4bd323 Successfully tagged federation/qserver:latest ```

peter_somogyvari (Mon, 29 Jun 2020 16:52:13 GMT):
That's the terminal output you should be seeing and I'm pretty confident that it works in general because we used to have the CI run this as well.

rjones (Mon, 29 Jun 2020 16:55:18 GMT):
https://tinyurl.com/y78m95zr

hartm (Mon, 29 Jun 2020 16:56:40 GMT):
Nice. And you can even customize the color scheme.

cliveb (Tue, 30 Jun 2020 00:56:32 GMT):
Added doc link to 2020-06-29 Cactus Meeting Agenda and emailed circulation. Discuss isolation for plugins and observable security: possible improvements to docs white-paper.

peter_somogyvari (Tue, 30 Jun 2020 03:09:36 GMT):
The github actions for the code coverage I was talking about are still in progress, getting there slowly but surely... :-)

peter_somogyvari (Tue, 30 Jun 2020 03:12:19 GMT):
@cliveb Thank you again for the great presentation and all the work we definitely need with regards to security: Our `secure by default` design principle is one of those requirements that is easy to state but extremely difficult to implement even when one has a blank sheet for design where legacy code is not an issue (our present, blissful state that won't last forever).

cliveb (Tue, 30 Jun 2020 05:11:24 GMT):

2020-06-25_0933.png

peter_somogyvari (Wed, 01 Jul 2020 20:31:20 GMT):
Does anybody know if Hyperledger can help us out with OSS dependency's licensing questions? There's this OSS package on Github that does NOT have a `LICENSE` file but it does have what *looks like* an Apache-2 at the of its `README.md`, but it is not being given a name in there so I'm just guessing what that license is on the bottom of the readme... This is the project in question: https://github.com/spmjs/node-scp2 Ultimately I just want confirmation that we can use this package in Cactus, because there does not some to be any good alternatives to it with straight forward licensing... Any help/pointers are very much appreciated ! cc: @JHamilton @rjones

assit (Sat, 04 Jul 2020 04:51:12 GMT):
Has joined the channel.

assit (Sat, 04 Jul 2020 17:40:22 GMT):
Has left the channel.

takeutak (Mon, 06 Jul 2020 15:04:23 GMT):
Hi everyone! cc: @peter_somogyvari @JHamilton @sfuji822 I pushed a pull-request about APIs of Ledger-Plugin on PR #217 . https://github.com/hyperledger/cactus/pull/217 I'd like to discuss about it in the next Cactus contributors' meeting.

suyukuo (Mon, 06 Jul 2020 18:13:55 GMT):
Has joined the channel.

peter_somogyvari (Tue, 07 Jul 2020 03:07:22 GMT):
@DOBEN https://marketplace.visualstudio.com/items?itemName=yzhang.markdown-all-in-one VSCode plugin for automatically generating the numberings ^^

DOBEN (Tue, 07 Jul 2020 03:10:00 GMT):
Thanks a lot Peter.

JHamilton (Thu, 09 Jul 2020 15:37:23 GMT):
#cactus for those trying to join the Cactus Contributors Western Hemisphere we were double booked, please join here https://zoom.us/my/hyperledger.community.backup

JHamilton (Thu, 09 Jul 2020 16:38:42 GMT):
Recording for today's Western Contibutors Call https://wiki.hyperledger.org/display/cactus/2020-07-09+Cactus+Contributors

peter_somogyvari (Tue, 14 Jul 2020 03:13:57 GMT):
@cliveb Responding to your message on Zoom chat: I agree. I am definitely in the CP NewSQL camp ( as in, that's my default choice) and always try to stay away from eventual consistency whenever I can because a lot of times even when someone tells you EC is fine for their requirements it turns out it is not. I'm also kinda biased against NoSQL because I've been on a few projects where someone prior made a choice to go with NoSQL despite the need for a schema and strong consistency in the data model and of course that lead to big headaches down the line... :-) Also a fan of CockroachDB, I did consider writing a storage plugin for Cactus that could be backed by a CockroachDB cluster that consortium members can operate in a shared manner (didn't do any of it yet, but been toying with the idea for quite some time).

cliveb (Wed, 15 Jul 2020 21:17:42 GMT):
On global-locks and business logic: IDK about 'CAPTUS' plugins ...https://wiki.hyperledger.org/display/AWG/2020-07-15

takeutak (Fri, 17 Jul 2020 01:43:06 GMT):
@rjones Can you add me to Hyperledger Cactus Maintainers as @JHamilton said? looks like I am missed by somehow reasons until now. https://github.com/orgs/hyperledger/teams/cactus-maintainers

JHamilton (Fri, 17 Jul 2020 01:45:32 GMT):
hey @takeutak looks like i was able to approve you after getting a request

takeutak (Fri, 17 Jul 2020 02:17:09 GMT):
@JHamilton

takeutak (Fri, 17 Jul 2020 02:17:09 GMT):
@JHamilton Thank you!

JHamilton (Fri, 17 Jul 2020 02:17:49 GMT):
gladly! it was strange not sure what happened if you had accepted before. but glad it was easy to fix B-)

JHamilton (Fri, 17 Jul 2020 02:18:03 GMT):
good luck getting to your weekend!

lucianosilva44 (Fri, 17 Jul 2020 18:44:21 GMT):
Has joined the channel.

lucianosilva44 (Fri, 17 Jul 2020 18:44:22 GMT):
Hello, everyone. Trying to run the simple asset tutorial, here. However, when I run one of the scenarios involving Fabric and Quorum, I got an error of socket hang up:

lucianosilva44 (Fri, 17 Jul 2020 18:44:25 GMT):
RequestError: Error: socket hang up

lucianosilva44 (Fri, 17 Jul 2020 18:45:29 GMT):
Does someone knows what this could be? Do I need to have a powerful environment on my host machine to run that?

peter_somogyvari (Fri, 17 Jul 2020 19:38:58 GMT):
Yes, the old examples need a lot of RAM unfortunately (around 16GB even if you omit the corda tests). Most likely one of the containers with either the ledgers or the validators is not running, that' usually the cause for the socket hung up error. Can you verify that the CI script in the tools directory works otherwise?

lucianosilva44 (Fri, 17 Jul 2020 19:40:43 GMT):
Do you mean the tools directory inside the root directory, @peter_somogyvari ?

peter_somogyvari (Fri, 17 Jul 2020 19:42:13 GMT):
No, that's the "new" CI script which should be fine with a few gigs of RAM. I meant the old one because I assumed you are working with the old examples under the `contribs` directory (do let me know if that's not the case, I may have misunderstood)

lucianosilva44 (Fri, 17 Jul 2020 19:44:26 GMT):
Yes, I am working with the examples inside `contribs`

lucianosilva44 (Fri, 17 Jul 2020 19:45:11 GMT):
`./contribs/Accenture-BIF/core/examples/simple-asset-transfer`

peter_somogyvari (Fri, 17 Jul 2020 19:47:06 GMT):
Okay, so the old CI script is this one `./contribs/Accenture-BIF/core/tools/ci.sh` and you need to run it with the `CI_NO_CORDA=true` env var:

peter_somogyvari (Fri, 17 Jul 2020 19:47:27 GMT):
And that should pass as long as your machine is not running out of memory.

peter_somogyvari (Fri, 17 Jul 2020 19:48:18 GMT):
And after that script has passed, your machine should have the containers up and running and allow you to run the examples without the socket hung up error.

peter_somogyvari (Fri, 17 Jul 2020 19:48:38 GMT):
(the script itself also runs those examples, that's basically the test in the CI script)

lucianosilva44 (Fri, 17 Jul 2020 19:49:38 GMT):
I see. I will try here. Thanks, @peter_somogyvari ! :)

lucianosilva44 (Sat, 18 Jul 2020 01:57:39 GMT):
@peter_somogyvari , tired to run `ci.sh` here, but it did not work. It only has created the Fabric network and Fabric federation. It could not instantiate the chaincode either.

lucianosilva44 (Sat, 18 Jul 2020 01:57:55 GMT):
tried to run*, correcting the first sentence

lucianosilva44 (Sat, 18 Jul 2020 01:59:02 GMT):
@peter_somogyvari , tried to run `ci.sh` here, but did not work. It only created the Fabric Network. In the step of chaincode instantiation, it failed

lucianosilva44 (Sat, 18 Jul 2020 01:59:30 GMT):
It says it cannot pull the image `hyperledger/fabric-ccenv:latest`

lucianosilva44 (Sat, 18 Jul 2020 02:00:49 GMT):
Actually, it did not even create the Fabric federation

lucianosilva44 (Sat, 18 Jul 2020 17:35:40 GMT):
Actually, I think there isn't a tag latest for fabric-ccenv anymore. Trying to change it, but don't know where in the script this tag is defined.

davidwboswell (Mon, 20 Jul 2020 17:55:38 GMT):
Has joined the channel.

davidwboswell (Mon, 20 Jul 2020 17:55:44 GMT):
I wanted to let everyone know that on July 30 Peter Somogyvari, Technology Architect for Accenture Products & Platforms (APP), will share about the newest Hyperledger project, Hyperledger Cactus at a virtual Hyperledger meetup. Details are at: https://www.meetup.com/Hyperledger-London/events/271943315/ Since this is a virtual meetup, anyone is welcome to dial in from any location. Please feel free to share this meetup with anyone you know who may be interested in learning more about Cactus and please feel free to join the meetup yourself.

lucianosilva44 (Mon, 20 Jul 2020 19:38:28 GMT):
Hello, @peter_somogyvari . Tried to execute `ci.sh` script in simple asset tutorial, but it fails claiming there is no *latest* tag to *hyperledger/fabric-ccenv* image. Do you know where could I change this tag?

peter_somogyvari (Tue, 21 Jul 2020 03:49:22 GMT):
@lucianosilva44 Hmm. You could change that tag in one of the docker-compose.yml files, but I'm not sure which one because I don't remember us using that image at all. Can you paste in the full stdout of the script you get? (or attach it as a file is even better) I'd want to take a more detailed look because I can't make much sense of the error unfortunately

lucianosilva44 (Tue, 21 Jul 2020 14:00:43 GMT):
@davidwboswell , meetup today will be at 16:00 London time, right?

lucianosilva44 (Tue, 21 Jul 2020 14:47:11 GMT):
Sure, @peter_somogyvari . Here it is

lucianosilva44 (Tue, 21 Jul 2020 14:47:24 GMT):

Captura de Tela 2020-07-21 às 11.43.58.png

lucianosilva44 (Tue, 21 Jul 2020 14:47:44 GMT):

Captura de Tela 2020-07-21 às 11.43.58.png

lucianosilva44 (Tue, 21 Jul 2020 14:48:06 GMT):
Sorry, I think it was sent twice lol

lucianosilva44 (Tue, 21 Jul 2020 15:00:59 GMT):
Sorry, I've seen now it will be next Thursday, July 30th lol

davidwboswell (Tue, 21 Jul 2020 15:37:10 GMT):
@lucianosilva44 -- yes, it will be on the 30th. hope you can make it.

peter_somogyvari (Tue, 21 Jul 2020 17:45:13 GMT):
@lucianosilva44 It seems like they chose to break it intentionally by deleting the `latest` tag for the images... :/ https://stackoverflow.com/a/62862682 I don't yet know how to fix it unfortunately.

lucianosilva44 (Wed, 22 Jul 2020 01:21:43 GMT):
Understood. Thanks, @peter_somogyvari !!

lucianosilva44 (Wed, 22 Jul 2020 15:17:59 GMT):
@peter_somogyvari , one doubt: in the simple asset transfer tutorial, who makes the signatures verification: the destiny ledger federation or the destiny ledger plugin (or connector, if I understood correctly)?

peter_somogyvari (Wed, 22 Jul 2020 16:20:24 GMT):
@lucianosilva44 The actual cryptographic operation happens on ledger, in the validator contract's `verify` method, but it is the connector that calls said method. You can trace it back in the source code if you look at these files and look for the verify method in each of them (in this case it's the besu implementation but they all work the same in the simple asset transfer example): `contribs/Accenture-BIF/core/src/plugins/connectors/ConnectorBesu.js` `contribs/Accenture-BIF/core/examples/simple-asset-transfer/besu/api/routes/actors/actors.controller.js` `contribs/Accenture-BIF/core/examples/simple-asset-transfer/besu/api/wrappers/actor.wrapper.js` `contribs/Accenture-BIF/core/examples/simple-asset-transfer/besu/contracts/Root.sol`

lucianosilva44 (Wed, 22 Jul 2020 17:21:58 GMT):
I see. Thanks, @peter_somogyvari !! :)

lucianosilva44 (Wed, 22 Jul 2020 17:22:17 GMT):
I will make the traceback here!

Rachit-gaur (Thu, 23 Jul 2020 10:16:01 GMT):
Hello, I am not able to attend the meeting due to different timezone, can someone guide me where I can contribute to?

lucianosilva44 (Thu, 23 Jul 2020 13:45:40 GMT):
Hello, everyone. One more little doubt, by curiosity: is it possible to use cactus to integrate not only DLT, but also conventional centralized databases?

sownak (Thu, 23 Jul 2020 13:49:19 GMT):
Hello @Rachit-gaur Thanks for wanting to contribute. There is this meeting for Western Hemisphere https://lists.hyperledger.org/g/cactus/viewevent?repeatid=29072&eventid=844927&calstart=2020-07-23 You can join that if you can.

lucianosilva44 (Thu, 23 Jul 2020 13:51:54 GMT):
When is this meeting, @sownak ?

sownak (Thu, 23 Jul 2020 13:52:54 GMT):
4:30 PM BST.

lucianosilva44 (Thu, 23 Jul 2020 13:53:04 GMT):
I see

lucianosilva44 (Thu, 23 Jul 2020 16:03:59 GMT):
Thanks, @peter_somogyvari , @sownak @JHamilton @suyukuo , for the meeting. Nice to meet you all once more! :)

peter_somogyvari (Thu, 23 Jul 2020 16:04:27 GMT):
Same here Luciano! Cheers!

JHamilton (Thu, 23 Jul 2020 16:04:51 GMT):
likewise! 🌵

takeutak (Tue, 28 Jul 2020 01:53:01 GMT):
@peter_somogyvari @JHamilton I checked the box "allow edits by maintainers" on PR 194, which is not able to be resolved conflicts by me. Would you mind if you resolve this conflicts? https://github.com/hyperledger/cactus/pull/194

davidwboswell (Wed, 29 Jul 2020 14:34:20 GMT):
As a reminder, there is a virtual Hyperledger meetup tomorrow at 15:00 UTC featuring a presentation about Cactus from @peter_somogyvari -- everyone here is welcome to attend and please also share this event link out with anyone you think would be interested. https://www.meetup.com/Hyperledger-London/events/271943315/

joy_2_code (Sat, 01 Aug 2020 04:51:46 GMT):
Has joined the channel.

SuperSeiyan (Mon, 03 Aug 2020 09:21:58 GMT):
Has joined the channel.

RafaelAPB (Mon, 03 Aug 2020 20:34:44 GMT):
I am working in a Polkadot (https://polkadot.network/) validator for Cactus. Can someone explain me in a greater detail what is the role of the validator, in particular the Ethereum validator? How does it validate the transactions coming from a Cactus node, to a target blockchain? When I look into "io.on('connection', function(client) " it looks more like a connector than a validator.

cliveb (Mon, 03 Aug 2020 21:01:14 GMT):
@RafaelAPB For greater detail. Cactus weekly team meeting is Monday 7pm PST https://zoom.us/my/hyperledger.community.3 / Should we add your Q to agenda? https://wiki.hyperledger.org/display/cactus/2020-08-03+Cactus+Maintainers+Meeting+Agenda

RafaelAPB (Mon, 03 Aug 2020 21:01:54 GMT):
Thanks, @cliveb, but I can only attend the western friendly meeting, as I am from Europe

cliveb (Mon, 03 Aug 2020 21:03:24 GMT):
@RafaelAPB If a core a maintainer doesn't answer. I will ask tonight on your behalf.

RafaelAPB (Mon, 03 Aug 2020 21:03:47 GMT):
Thank you, appreciate that. I will be looking forward to see your opinion on the academic paper question

hartm (Tue, 04 Aug 2020 02:18:16 GMT):
https://dl.acm.org/doi/10.1145/3190508.3190538

hartm (Tue, 04 Aug 2020 02:18:22 GMT):
Fabric acadmic paper.

cliveb (Tue, 04 Aug 2020 08:32:33 GMT):
@RafaelAPB Your question was discussed. The answer depends on further development best discussed between you and maintainers this Thu, Aug 6, 3:30pm GMT https://zoom.us/my/hyperledger.community.3 | JIC you can't make it. Last weeks talk by @peter_somogyvari https://youtu.be/IHy-5sbMrYs at 39:48 has a Ethereum Q&A on 2 phase commit.

cliveb (Tue, 04 Aug 2020 08:32:33 GMT):
@RafaelAPB Your question was discussed at Monday's 7pm meeting. The answer depends on further development best discussed between you and maintainers this Thu, Aug 6, 3:30pm GMT https://zoom.us/my/hyperledger.community.3 | JIC you can't make it. Last weeks talk by @peter_somogyvari https://youtu.be/IHy-5sbMrYs at 39:48 has a Ethereum Q&A on 2 phase commit.

cliveb (Tue, 04 Aug 2020 08:32:33 GMT):
@RafaelAPB Your questions were discussed at Monday's 7pm meeting. The answers depend on further development best discussed between you and maintainers this Thu, Aug 6, 3:30pm GMT https://zoom.us/my/hyperledger.community.3 | JIC you can't make it. Last weeks talk by @peter_somogyvari https://youtu.be/IHy-5sbMrYs at 39:48 has an Ethereum Q&A on 2 phase commit.

ysai (Thu, 06 Aug 2020 08:10:14 GMT):
Has joined the channel.

peter_somogyvari (Thu, 06 Aug 2020 16:33:10 GMT):
I uploaded the recording to the wiki. Thank you very much for taking notes @cliveb and sorry I was a bit late to the call!

calvin.heo (Mon, 10 Aug 2020 06:08:28 GMT):
Has joined the channel.

JHamilton (Tue, 11 Aug 2020 13:52:01 GMT):
minutes & recordings up from this week & prior week maintainers meeting, thanks @takeutak ! https://wiki.hyperledger.org/display/cactus/2020-08-10+Meeting+notes https://wiki.hyperledger.org/display/cactus/2020-08-03+Meeting+notes

AndrewPark 1 (Thu, 13 Aug 2020 13:32:32 GMT):
Has joined the channel.

cliveb (Thu, 13 Aug 2020 22:58:33 GMT):
@peter_somogyvari on secure public key and overwrites. See membrane discussion with Caridy Patino 00:24 https://youtu.be/yd8NCoZ5N_o

cliveb (Thu, 13 Aug 2020 22:58:33 GMT):
@peter_somogyvari on secure public key and overwrites. See membrane discussion with Caridy Patino 00:24 https://youtu.be/yd8NCoZ5N_o (I will chase this down).

peter_somogyvari (Fri, 14 Aug 2020 00:59:36 GMT):
@cliveb Thank you, that was informative. At the same time I'll double check my tests to make sure I'm not doing something wrong

JHamilton (Mon, 17 Aug 2020 23:22:38 GMT):
draft agenda, as always walk on topics welcome! https://wiki.hyperledger.org/display/cactus/2020-08-18+Cactus+Maintainers+Meeting+Agenda

JHamilton (Mon, 17 Aug 2020 23:22:38 GMT):
draft agenda, as always edits & further topics welcome! https://wiki.hyperledger.org/display/cactus/2020-08-18+Cactus+Maintainers+Meeting+Agenda

cliveb (Tue, 18 Aug 2020 03:12:48 GMT):
Tonight's Cactus meeting notes. Please make any edits needed. https://wiki.hyperledger.org/display/cactus/2020-08-18+Meeting+notes

peter_somogyvari (Tue, 18 Aug 2020 17:21:25 GMT):
Thank you Clive! I uploaded the recording.

HeMBaD (Thu, 20 Aug 2020 10:44:21 GMT):
Has joined the channel.

jcldnatv (Sat, 22 Aug 2020 17:29:07 GMT):
Has joined the channel.

JuanNogueira (Sun, 23 Aug 2020 22:58:43 GMT):
Has joined the channel.

JuanNogueira (Sun, 23 Aug 2020 22:58:44 GMT):
Hi everybody. I have one doubt about the current state of cactus. Can I use it today to interoperate two blockchains platforms or it's not ready for that yet?

peter_somogyvari (Mon, 24 Aug 2020 16:20:26 GMT):
Hi @JuanNogueira Welcome to the community! Progress is steady, BUT we are not ready for production yet (the project is in incubation status, watch out for it becoming an 'active' status project). In the meantime we have weekly calls and maintain a road map of sorts here on Github (mor to come soon) https://github.com/hyperledger/cactus/milestone/2 Also a good starting point to browser our wiki if you are interested in the details: https://wiki.hyperledger.org/display/cactus

JuanNogueira (Mon, 24 Aug 2020 21:34:21 GMT):
Ok, if the project is steady that's enough for me (even if it's not ready for prod yet). Is there any tutorial about how to interoperate two platforms? I reviewed the link you sent but didn't find any

peter_somogyvari (Mon, 24 Aug 2020 21:43:56 GMT):
@JuanNogueira We expect that to be ready by mid-September when we will (hopefully) also present the same thing at the members summit in the form of an actual demo.

peter_somogyvari (Tue, 25 Aug 2020 00:27:31 GMT):
All: I just published the meeting agenda for today here: https://wiki.hyperledger.org/display/cactus/2020-08-25+Cactus+Contributors+Meeting+Agenda Everyone should feel free to add discussion items as usual.

peter_somogyvari (Tue, 25 Aug 2020 03:19:55 GMT):
@hartm IIRC, this was the Rust compilation target I was looking into that could offer us a proper Ursa JS library (didn't get very far): https://doc.rust-lang.org/nightly/nightly-rustc/rustc_target/spec/asmjs_unknown_emscripten/index.html

JuanNogueira (Tue, 25 Aug 2020 15:04:50 GMT):
Ok. Another question. Cactus currently supports Hyperledger fabric, Quorum and Corda platforms, right?

JuanNogueira (Tue, 25 Aug 2020 15:26:55 GMT):
And also, which platforms are you planning to use for the demo?

peter_somogyvari (Tue, 25 Aug 2020 15:46:04 GMT):
@JuanNogueira The definition of what is supported versus is being worked on is kind of fluid since we are not yet finished with the initial release, but all that aside, we have all of those either supported or underway, yes and add Besu to that list. My personal goal is to have a demo that quickly demonstrates all of those in one go, but this is unlikely to happen because we are cutting it close. I can tell you that the high priority is fabric and corda

JuanNogueira (Tue, 25 Aug 2020 15:53:37 GMT):
Ok, thanks for your answers! Let me ask you one more question. Do you have an estimated date for the initial release?

peter_somogyvari (Tue, 25 Aug 2020 16:01:53 GMT):
@JuanNogueira Personally, my aim is to have an initial release out by the end of September and from then on have regularly scheduled releases every month or possibly even every week that are automated to the extent that the process is not impacting our focus. Ideally it would be a proper continuous delivery pipeline that takes the latest code at any given time, parses the commit messages (which are enforced by tooling to be in a machine readable format) for determining the type of release that should be issued according to semantic versioning rules (e.g. breaking changes trigger a major release). Everything is always a little slower than we hope/expect, but this is the vision we are driving towards. The initial release is still not planned to be something production ready, it would most likely be v0.3 and if all goes well we could have a production ready release with performance benchmarks and extensive test coverage by the end of this calendar year that we could dub as a v1.0.

bjwswang (Thu, 27 Aug 2020 02:11:25 GMT):
Has joined the channel.

jbtwist (Thu, 27 Aug 2020 13:49:19 GMT):
Has joined the channel.

jbtwist (Thu, 27 Aug 2020 13:49:19 GMT):
Hi, i am searching info about cactus, but I dont understand what does DLT fragmentation means, can any1 explain to me that?

sigma67 (Thu, 27 Aug 2020 13:50:25 GMT):
I believe it refers to the large number of DLT frameworks that are currently available and used, which results in the need for interoperability

RafaelAPB (Thu, 27 Aug 2020 15:47:04 GMT):
@jbtwist yes, sigma is right. Essentially, choosing a blockchain allows researchers and developers to implement new use case scenarios, and to keep up with recent research. However, as this technology is moving so quickly, there are bugs and performance issues. "Developers and researchers have, therefore, to choose between novelty and stability, leading to a vast diversity of choices. This diversity leads to fragmentation: there are many immature blockchain solutions. Until recently, blockchains did not consider the need for interoperability, as each one resolved specific challenges, leading to data and value silos"

jbtwist (Thu, 27 Aug 2020 15:58:36 GMT):
i think that they are not talking about that in this context: https://youtu.be/IHy-5sbMrYs?t=151

jbtwist (Thu, 27 Aug 2020 15:59:14 GMT):
but i dont understand it, i may be wrong

jbtwist (Thu, 27 Aug 2020 16:02:00 GMT):
I just want to understand that video and try to learn about how this technology works

RafaelAPB (Thu, 27 Aug 2020 18:36:08 GMT):
In that context it means that there are a lot of solutions moving at a very fast pace.

da3v21 (Thu, 27 Aug 2020 19:58:03 GMT):
Has joined the channel.

dilumb (Fri, 28 Aug 2020 00:31:29 GMT):
Has joined the channel.

hartm (Tue, 01 Sep 2020 02:08:10 GMT):
Example use of Ursa with Javascript: https://github.com/mattrglobal/bbs-signatures

hartm (Tue, 01 Sep 2020 02:08:43 GMT):
https://github.com/mattrglobal/node-bbs-signatures/blob/master/native/src/lib.rs#L461

derekbar 1 (Wed, 02 Sep 2020 18:48:02 GMT):
Has joined the channel.

hartm (Thu, 03 Sep 2020 15:36:18 GMT):
We are in https://zoom.us/my/hyperledger.community.backup

hartm (Thu, 03 Sep 2020 15:36:28 GMT):
...due to a zoom scheduling issue.

rjones (Thu, 03 Sep 2020 16:27:58 GMT):
@hartm I show your original room is free - who was using it?

hartm (Thu, 03 Sep 2020 16:28:57 GMT):
I believe it was the Fabric application developer community call.

mahoney1 (Thu, 03 Sep 2020 16:28:59 GMT):
Has joined the channel.

rjones (Thu, 03 Sep 2020 16:29:29 GMT):
weird, that doesn't show up with a meeting room :(

hartm (Thu, 03 Sep 2020 16:29:57 GMT):
Yeah, I think they had some kind of calendar issue.

rjones (Thu, 03 Sep 2020 16:30:35 GMT):
OK. I apologize. I'll try to figure it out

hartm (Thu, 03 Sep 2020 16:30:44 GMT):
No worries. And thanks!

rjones (Thu, 03 Sep 2020 16:31:24 GMT):
Sure. I see them on the calendar for the week after, but not today. Not sure what happened.

mahoney1 (Thu, 03 Sep 2020 16:31:34 GMT):
hi Rick, I had thought we had 60m slot (as we had for quite some time) and hence over-ran into 3:30 UTC slot - I might now need to use the backup zoom id instead for Developer call - apologies all around firstly - and so, cactus can have the current zoom id

mahoney1 (Thu, 03 Sep 2020 16:31:34 GMT):
hi Rick, I had thought we had 60m slot (as we had for quite some time) and hence over-ran into 3:30 UTC slot - I might now need to use the backup zoom id instead for Developer comm call - apologies all around firstly - and so, cactus can have the current zoom id

mahoney1 (Thu, 03 Sep 2020 16:31:34 GMT):
hi Ry, I had thought we had 60m slot (as we had for quite some time) and hence over-ran into 3:30 UTC slot - I might now need to use the backup zoom id instead for Developer comm call - apologies all around firstly - and so, cactus can have the current zoom id

rjones (Thu, 03 Sep 2020 16:32:15 GMT):
no worries, it's certainly some confusion on my part

rjones (Thu, 03 Sep 2020 16:32:36 GMT):
I know I changed one meeting, cactus or ursa, to another room because I saw a conflict. I probably missed this one

mahoney1 (Thu, 03 Sep 2020 16:33:36 GMT):
ok, np - so should we move to the backup zoom id for a 3-4pm slot? Or as you suggest really...

rjones (Thu, 03 Sep 2020 16:34:17 GMT):
give me a minute to work it out

rjones (Thu, 03 Sep 2020 16:39:13 GMT):
I changed the cactus call to https://zoom.us/my/hyperledger.community.backup to deconflict

mahoney1 (Thu, 03 Sep 2020 16:40:17 GMT):
thanks Ry and @hartm !

rjones (Thu, 03 Sep 2020 16:40:24 GMT):
I also edited a couple fabric calls to use the name of the zoom room instead of the number :)

sfuji822 (Fri, 04 Sep 2020 01:16:48 GMT):
jweate peter_somogyvari I see PR#190 https://github.com/hyperledger/cactus/pull/190 is still have a issue to be merged. I think you need to execute rebase for passing commit check. Since we would like to use your plugin at the demo application, please tell us about your plan to fix the issue.

sfuji822 (Fri, 04 Sep 2020 01:16:48 GMT):
@jweate @peter_somogyvari I see PR#190 https://github.com/hyperledger/cactus/pull/190 is still have a issue to be merged. I think you need to execute rebase for passing commit check. Since we would like to use your plugin at the demo application, please tell us about your plan to fix the issue.

peter_somogyvari (Fri, 04 Sep 2020 17:01:43 GMT):
@sfuji822 That one is still in progress unfortunately (it is just a draft, so not ready for review). My latest info is that the container image itself is operational, but the test automation is still being finalized. Furthermore there's this technical challenge that is unsolved by this PR about the RPC communication between Cactus and the Corda nodes/apps. There are basically 3 options to communicate from the NodeJS code with Corda 1) host a Java app as an in-between translation layer (because Corda RPC libraries are written in Kotlin) 2) run the java app in graalvm and directly invoke the RPC related code from NodeJS 3) compile the RPC corda code from Kotlin to JS and use that as a NodeJS library directly in Cactus. 4) use SSH to connect to the corda server and execute tasks via the CLI (such as deploying contracts, starting flows etc) In the #190 PR we went with option 4) because it was the simplest for a proof of concept, but longer term of course this will not scale well for high throughput, performance sensitive production deployments so my plan is to work on option 3) as the most maintainable option. Option 1 and 2 both require external processes to be running in tandem to the Cactus process so both of those are sub-optimal when it comes to maintenance and operational complexity because of the extra processes (also bad for containerization because by design a container's life-cycle is tied to a single process running in the container) That's the context so far. What I could use help with is the implementation of option 3) and if that turns out to be very high effort then option 2 as a fallback/last resort. Regarding my try on option 3 so far: Tried to add the kotlin JS plugin to my corda fork, but the build then crashes with some gradle dependency error that I haven't yet had the time to investigate properly.

peter_somogyvari (Tue, 08 Sep 2020 00:46:51 GMT):
FYI I just posted today's agenda draft here, feel free to add items as usual: https://wiki.hyperledger.org/display/cactus/2020-09-08+Cactus+Maintainers+Agenda

peter_somogyvari (Tue, 08 Sep 2020 19:04:36 GMT):
Thanks for the links @hartm, @derekbar 1 went through the project and it was extremely helpful in clearing up how the pieces fit together. Especially for the parts that handle the fallback at runtime based on platforms. FYI: I submitted a PR in an attempt to fix the browser sample: https://github.com/mattrglobal/bbs-signatures/pull/48

peter_somogyvari (Tue, 08 Sep 2020 19:04:36 GMT):
Thanks for the links @hartm, @derekbar1 went through the project and it was extremely helpful in clearing up how the pieces fit together. Especially for the parts that handle the fallback at runtime based on platforms. FYI: I submitted a PR in an attempt to fix the browser sample: https://github.com/mattrglobal/bbs-signatures/pull/48

sillysachin (Mon, 14 Sep 2020 10:38:10 GMT):
Has joined the channel.

sillysachin (Mon, 14 Sep 2020 10:38:10 GMT):
Hello

sillysachin (Mon, 14 Sep 2020 10:38:26 GMT):
https://github.com/hyperledger/cactus/tree/v0.1.0/examples/simple-asset-transfer

sillysachin (Mon, 14 Sep 2020 10:40:35 GMT):
simple-asset-transfer is no longer present in master branch

sillysachin (Mon, 14 Sep 2020 10:40:37 GMT):
https://github.com/hyperledger/cactus/tree/master/examples

sillysachin (Mon, 14 Sep 2020 10:41:16 GMT):
https://github.com/hyperledger/cactus/blob/master/docs/tutorials/simple-asset-transfer.md

sillysachin (Mon, 14 Sep 2020 10:41:32 GMT):
What is the right way to go about learning and setting this up ?

cliveb (Mon, 14 Sep 2020 23:45:58 GMT):
@peter_somogyvari Delay on chasing down Membrane proxy expert and any libraries. (I am super busy on deadline project -- back next wk).

randyshu (Tue, 15 Sep 2020 01:44:59 GMT):
Has joined the channel.

randyshu (Tue, 15 Sep 2020 07:19:18 GMT):
Hi,everyone Is cactus now support fabric cross-chain with polka?

allenyang (Tue, 15 Sep 2020 08:03:05 GMT):
Has joined the channel.

randyshu (Tue, 15 Sep 2020 09:34:57 GMT):

Clipboard - 2020年9月15日下午5点33分

allenyang (Wed, 16 Sep 2020 09:53:07 GMT):
hello, guys, I want to run the example cartrade, what is npm version when you test?

RafaelAPB (Wed, 16 Sep 2020 10:15:45 GMT):
Hello @randyshu. Not at the moment, but I have plans of developing a polkadot connector.

sillysachin (Thu, 17 Sep 2020 04:26:04 GMT):
Hello folks.... 77 Done, 11 in Progress and 29 TODO in BIF v0.2.0 Kanban - https://github.com/hyperledger/cactus/projects/1#card-44938075

sillysachin (Thu, 17 Sep 2020 04:26:33 GMT):
Is there rough timeline on when v0.2.0 will be released with Fabric/Corda example

sillysachin (Thu, 17 Sep 2020 04:35:08 GMT):
For Experimentation I have tried v0.1.0 and logged a issue i faced https://github.com/hyperledger/cactus/issues/284

JHamilton (Mon, 21 Sep 2020 14:08:46 GMT):
Thank you for filing the issue Sachin! we will take a look and communicate in the ticket itself

peter_somogyvari (Tue, 22 Sep 2020 04:02:39 GMT):
@sillysachin Can't promise any timelines, but hoping for all that to be available in the next couple of months and with a stable release hopefully this year. Everything always takes longer than expected so take this information with a grain of salt of course. ;-) I'm knee deep in both the corda and fabric examples, if you want to track the progress here's a PR that's a dependency so feel free to track this as well: https://github.com/webpack/webpack/pull/11316

knagware9 (Mon, 28 Sep 2020 10:22:34 GMT):
Hello cactus community from the Hyperledger India Chapter, we are calling for speakers to engage with the community in Asia Pacific, Europe and Africa. Please see our event details here https://www.linkedin.com/feed/update/urn:li:activity:6715897303481372672 Calling the tech enthusiasts, maintainers to be part of it.

JHamilton (Tue, 29 Sep 2020 01:47:07 GMT):
hey all, friendly reminder that Hyperledger has provided updated zooms. here is the new one for Maintainers meeting https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 PS thanks Hart for crafting the agenda! https://wiki.hyperledger.org/display/cactus/2020-09-28+Meeting+Agenda

rjones (Tue, 29 Sep 2020 03:31:47 GMT):
@JHamilton Did the meeting work?

JHamilton (Tue, 29 Sep 2020 11:19:22 GMT):
It was seamless, thank you Ry! also for whatever reason the new calendar invites are actually working with Outlook, which is nice 👏

rjones (Tue, 29 Sep 2020 13:38:40 GMT):
Cool. I’ll take credit for that even though I did nothing about outlook 😜

dgt1nsty (Fri, 02 Oct 2020 14:28:14 GMT):
Has joined the channel.

JuanNogueira (Sun, 04 Oct 2020 21:02:06 GMT):
Hello. Which hyperledger fabric version/s is cactus planning to support? And which Corda version/s? Thanks

peter_somogyvari (Mon, 05 Oct 2020 16:10:57 GMT):
@JuanNogueira In progress are these at the moment: Corda 4.x and Fabrix 1.x. You can expect Fabric 2.x later, once we have nailed down the 1.4x support first (there's not a huge difference between 1.4x and 2.x is the assumption for now)

JuanNogueira (Mon, 05 Oct 2020 20:50:55 GMT):
okay, thanks!

jakobsn (Tue, 06 Oct 2020 08:37:24 GMT):
Has joined the channel.

peter_somogyvari (Wed, 07 Oct 2020 03:47:08 GMT):
I bootstrapped the agenda draft for next week. Feel free to add discussion items as usual: https://wiki.hyperledger.org/display/cactus/2020-10-13+Cactus+Contributors+Meeting+Agenda

Sandeepk40 (Wed, 07 Oct 2020 04:28:30 GMT):
Has joined the channel.

randyshu (Tue, 13 Oct 2020 03:21:19 GMT):
Does Hyperledger Cactus refactoring finished？I see the office docs says it undergoing refactoring

peter_somogyvari (Tue, 13 Oct 2020 03:37:00 GMT):
Still in progress @randyshu I recommend you check out the milestones on GitHub to be able to track the actual progress, proposed dates, etc.

randyshu (Wed, 14 Oct 2020 08:18:49 GMT):
:thinking: Could carTrade demo support fabric tls model ? I see the default.json use grpc rather than grpcs

randyshu (Thu, 15 Oct 2020 03:05:30 GMT):
what's the function "thirdTransaction" of carTrade for ? I know the firstTransaction is for ethereum trade and the second for fabric changeCarOwner but the third why ethereum operation?

guolidong (Thu, 15 Oct 2020 03:30:22 GMT):
Has joined the channel.

peter_somogyvari (Thu, 15 Oct 2020 15:27:15 GMT):
2020-10-15 Cactus Contributors at Western Hemisphere Agenda is up: https://wiki.hyperledger.org/display/cactus/2020-10-15+Cactus+Contributors+at+Western+Hemisphere+Agenda

RafaelAPB (Sat, 17 Oct 2020 17:41:25 GMT):
For the ones interested into the academic paper, feel free to check the channel #cactus-paper

brunob15 (Sat, 17 Oct 2020 20:16:43 GMT):
Has joined the channel.

brunob15 (Sat, 17 Oct 2020 20:16:43 GMT):
Hi all, are there any updates about a tutorial to get started working with Cactus? Thank you!

mwklein (Mon, 19 Oct 2020 16:34:45 GMT):
It appears the channel is requiring a password to subscribe. Can that be removed?

RafaelAPB (Mon, 19 Oct 2020 16:47:16 GMT):
@mwklein sorry for that, I must have made some mistake. Good to go now :)

JHamilton (Mon, 19 Oct 2020 19:12:10 GMT):

Clipboard - October 19, 2020 2:12 PM

JHamilton (Mon, 19 Oct 2020 19:12:59 GMT):
👆 looks like channel still has pwd on

rjones (Mon, 19 Oct 2020 19:25:52 GMT):
fixed. it had a password, but it was blank

rjones (Mon, 19 Oct 2020 19:25:57 GMT):
now it has no password

peter_somogyvari (Tue, 20 Oct 2020 01:38:13 GMT):
A bit last minute as usual. As always, feel free to add items to the discussion list:

peter_somogyvari (Tue, 20 Oct 2020 01:38:33 GMT):
A bit last minute as usual. As always, feel free to add items to the discussion list: https://wiki.hyperledger.org/display/cactus/2020-10-20+Cactus+Maintainers+Agenda

peter_somogyvari (Tue, 20 Oct 2020 04:04:45 GMT):
Next week's meeting agenda is up. Feel free to add discussion items as always: https://wiki.hyperledger.org/display/cactus/2020-10-27+Cactus+Maintainers+Agenda

JHamilton (Thu, 22 Oct 2020 03:59:51 GMT):
As discussed in maintainers meeting Oct 19th, I have pushed the Nov 2nd session to Nov 4th. Accidentally messed up the series on first try, but think it's fixed now. just let me know if anyone see's anything wrong :) https://lists.hyperledger.org/g/cactus/viewevent?repeatid=32482&eventid=948385&calstart=2020-11-04

csunitha (Thu, 22 Oct 2020 07:41:20 GMT):
Has joined the channel.

sfuji822 (Fri, 23 Oct 2020 22:01:54 GMT):
Thank you very much.

JuanNogueira (Mon, 26 Oct 2020 22:45:40 GMT):
It's still asking me for password, I can't join that channel

rjones (Mon, 26 Oct 2020 23:10:24 GMT):
@JuanNogueira how about now?

JuanNogueira (Tue, 27 Oct 2020 20:39:14 GMT):
I do have access to the channel now. Thanks!

peter_somogyvari (Tue, 27 Oct 2020 23:10:01 GMT):
FYI: Just posted the agenda for our upcoming “Cactus Contributors Western Hemisphere” call on Thursday: https://wiki.hyperledger.org/display/cactus/2020-10-27+Cactus+Contributors+Western+Hemisphere+Agenda

JHamilton (Mon, 02 Nov 2020 22:35:36 GMT):
greetings Cactus community! as a friendly reminder, our standing Maintainers meeting is pushed by 2 days (same time as usual on Weds 4th Americas, Thurs the 5th most other geos). They Hyperledger community shows it but as I didn't see an updated invite over email wanted to repeat here :) https://lists.hyperledger.org/g/cactus/calendar

husnain (Tue, 03 Nov 2020 11:41:37 GMT):
Has joined the channel.

peter_somogyvari (Tue, 03 Nov 2020 21:16:32 GMT):
Hi All, The agenda for our holiday special maintainer's call is up on the wiki, feel free to add discussion points as usual: https://wiki.hyperledger.org/display/cactus/2020-11-05+Cactus+Maintainers+Agenda

avradip (Thu, 05 Nov 2020 00:24:17 GMT):
Has joined the channel.

randyshu (Thu, 05 Nov 2020 10:15:20 GMT):

Clipboard - 2020年11月5日晚上6点15分

randyshu (Thu, 05 Nov 2020 10:16:23 GMT):
hi, anyone meet that error and how to solve it ?

luckyrobinson (Thu, 05 Nov 2020 11:34:48 GMT):
Has joined the channel.

luckyrobinson (Thu, 05 Nov 2020 11:34:49 GMT):
hi, all, anyone meets the error?

luckyrobinson (Thu, 05 Nov 2020 11:34:55 GMT):

Clipboard - 2020年11月5日晚上7点34分

AndrewPark 1 (Fri, 06 Nov 2020 09:32:53 GMT):
I'm studing about cactus.

AndrewPark 1 (Fri, 06 Nov 2020 09:33:31 GMT):
Is it possible to exchange between NFT and FT?

peter_somogyvari (Fri, 06 Nov 2020 21:53:47 GMT):
@randyshu What command(s) did you run after cloning the repo to get these errors?

peter_somogyvari (Fri, 06 Nov 2020 21:55:45 GMT):
@luckyrobinson Haven't seen that one. From the logs it looks like maybe @takeutak / @sfuji822 could help?

peter_somogyvari (Sat, 07 Nov 2020 01:17:00 GMT):
Hi All, the meeting agendas are up for next week, feel free to add discussion items as usual: https://wiki.hyperledger.org/display/cactus/2020-11-10+Cactus+Maintainers+Agenda https://wiki.hyperledger.org/display/cactus/2020-11-12+Cactus+Contributors+Western+Hemisphere+Agenda

randyshu (Sat, 07 Nov 2020 02:24:43 GMT):
1. cd ${GOPATH}/src/github.com/hyperledger/cactus/packages && npm install 2. npm run package-build

peter_somogyvari (Sat, 07 Nov 2020 02:28:28 GMT):
@randyshu I see, if you are trying to get the cartrade example working I'm not sure how to help, but pinging @takeutak should yield some info there hopefully.

peter_somogyvari (Sat, 07 Nov 2020 02:37:20 GMT):
@AndrewPark 1 Depends, do you mean atomic swaps?

luckyrobinson (Mon, 09 Nov 2020 02:59:06 GMT):
how I could deploy the cartrade example? I refer to the README.md in the path of cactus/examples/cartrade, but can't start the service. anyone can direct？ thank you

luckyrobinson (Mon, 09 Nov 2020 03:22:54 GMT):
hello, how I could deploy the cartrade example? I refer to the README.md in the path of cactus/examples/cartrade, but can't start the service. thank you

JHamilton (Mon, 09 Nov 2020 21:23:46 GMT):
@sfuji822 @takeutak can you help with this?

DVasin (Tue, 10 Nov 2020 11:16:07 GMT):
Has joined the channel.

sfuji822 (Wed, 11 Nov 2020 00:12:41 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=Ns8fnRkTbcvaSh3AN) Hi @luckyrobinson. We FUJITSU team is preparing to submit a PR for adding detailed instruction in a few days. Can you wait for it?

Daniela_Barbosa (Wed, 11 Nov 2020 03:36:48 GMT):
Has joined the channel.

luckyrobinson (Thu, 12 Nov 2020 01:41:17 GMT):
@sfuji822 Thank you. How I could config the iterms in examples/cartrade/config/default.json. Is there any explain or example for that? Thank you

luckyrobinson (Thu, 12 Nov 2020 01:42:43 GMT):

Clipboard - 2020年11月12日上午9点42分

luckyrobinson (Thu, 12 Nov 2020 01:42:56 GMT):
Thank you. How I could config the iterms in examples/cartrade/config/default.json. Is there any explain or example for that?

luckyrobinson (Thu, 12 Nov 2020 01:43:18 GMT):

Clipboard - 2020年11月12日上午9点43分

luckyrobinson (Thu, 12 Nov 2020 01:44:02 GMT):
@sfuji822 Thank you. How I could config the iterms in examples/cartrade/config/default.json. Is there any explain or example for that?

luckyrobinson (Thu, 12 Nov 2020 01:44:34 GMT):

Clipboard - 2020年11月12日上午9点44分

jagpreet (Thu, 12 Nov 2020 04:02:45 GMT):
Has joined the channel.

AndrewPark 1 (Thu, 12 Nov 2020 04:30:01 GMT):
@peter_somogyvari Yes. I need atomic swap functionality. For examples, ethereum NFT card and our own coin made by HLF.

peter_somogyvari (Thu, 12 Nov 2020 04:35:40 GMT):
@AndrewPark 1 Gotcha. We don't have anything concrete implemented for atomic swaps yet, but there are plans: Basically we want to enable it through plugins so there could be different flavors of ideas such as hash time-lock contracts (HTLCs) or any of the other (relatively) well researched atomic swap algorithms/protocols that people have proposed. So if you are looking to contribute then the way to get started would be to write a plugin that can do atomic swaps in general, but if you would rather just use something out of the box then the best I can say for now is to wait until we have an implementation ready. :-)

luckyrobinson (Fri, 13 Nov 2020 02:51:11 GMT):

Clipboard - November 13, 2020 10:50 AM

luckyrobinson (Fri, 13 Nov 2020 07:02:27 GMT):
Now I can do the firstTransaction in examples/cartrade successfully，but the secondTransaction and ThirdTransaction is not working. What the reason results it. Anyone can help? Thank you

peter_somogyvari (Mon, 16 Nov 2020 23:08:52 GMT):
cc: @takeutak @sfuji822

peter_somogyvari (Mon, 16 Nov 2020 23:09:30 GMT):
`2020-11-17 Cactus Maintainer's Meeting Agenda` is up, feel free to add discussion items as usual: https://wiki.hyperledger.org/display/cactus/2020-11-17+Cactus+Maintainer%27s+Meeting+Agenda

JHamilton (Tue, 17 Nov 2020 04:20:06 GMT):
dear Cactus community, maintainers meeting on Nov 24th has been cancelled due to US Thanksgiving holiday week. please ping here if any topics requiring a one off meeting

gortaire (Tue, 17 Nov 2020 15:47:59 GMT):
Has joined the channel.

peter_somogyvari (Tue, 17 Nov 2020 15:55:23 GMT):
The agenda is up for the upcoming call on Thursday (which got moved up from next Thursday) Feel free to add discussion topics as usual: https://wiki.hyperledger.org/display/cactus/2020-11-19+Cactus+Contributors+Western+Hemisphere+Agenda

RMX (Fri, 20 Nov 2020 12:54:51 GMT):
Has joined the channel.

RMX (Fri, 20 Nov 2020 12:54:52 GMT):
Good afternoon, it is a pleasure to join all of you in your endeavour to write a paper and contribute to the project. I tried to install and run Cactus, but ran into an issue on Mac OS Catalina and could not finish the Build. Does somebody know how to resolve this issue? npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! @hyperledger/cactus@ test:all: `tap --jobs=1 --timeout=600 "packages/cactus-*/src/test/typescript/{unit,integration}/"` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the @hyperledger/cactus@ test:all script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /Users/romanmuhlberger/.npm/_logs/2020-11-20T12_19_40_308Z-debug.log 2020-11-20T13:19:40+0100 [CI] FAILURE - runtime=5323 seconds.

RMX (Fri, 20 Nov 2020 12:54:52 GMT):
Good afternoon, it is a pleasure to join all of you in your endeavour to write a paper and contribute to the project. I tried to install and run Cactus, but ran into an issue on Mac OS Catalina and could not finish the Build. Does somebody know how to resolve this issue? Regards, Roman npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! @hyperledger/cactus@ test:all: `tap --jobs=1 --timeout=600 "packages/cactus-*/src/test/typescript/{unit,integration}/"` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the @hyperledger/cactus@ test:all script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /Users/romanmuhlberger/.npm/_logs/2020-11-20T12_19_40_308Z-debug.log 2020-11-20T13:19:40+0100 [CI] FAILURE - runtime=5323 seconds.

peter_somogyvari (Fri, 20 Nov 2020 19:45:33 GMT):
Hey Roman, cheers, it is a pleasure to have you joining us! Regarding the error, two questions: 1. After cloning the code what steps did you take exactly? Did you follow the build guide[1] or just ran the test script right away? [1]: https://github.com/hyperledger/cactus/blob/master/BUILD.md 2. Is there any more logs on the terminal? Usually when running the tests I'd have expected some more details about which test case failed.

peter_somogyvari (Fri, 20 Nov 2020 21:45:38 GMT):
Hi All, the agenda for our next meeting has been posted (which is not next week so make sure to double check the dates!) https://wiki.hyperledger.org/display/cactus/2020-12-01+Cactus+Maintainers+Agenda As usual, feel free to add more items or just show up and then grab the mic at the ad-hoc discussion part of the meeting before we move on to the PR grind.

Senthil1 (Sat, 21 Nov 2020 04:36:58 GMT):
Has joined the channel.

piyushmaheshwari65 (Wed, 25 Nov 2020 04:21:32 GMT):
Has joined the channel.

heena066 (Thu, 03 Dec 2020 09:09:16 GMT):
Has joined the channel.

peter_somogyvari (Mon, 07 Dec 2020 18:35:41 GMT):
Hi All, the agenda for our next meeting has been posted: https://wiki.hyperledger.org/display/cactus/2020-12-08+Cactus+Maintainers+Meeting+Agenda As usual, feel free to add more items or just show up and then grab the mic at the ad-hoc discussion part of the meeting before we move on to process pull requests.

hartm (Tue, 08 Dec 2020 02:39:18 GMT):
https://docs.google.com/document/d/1Gbj_Ehe-xMw_lVyRqV-OsLbJ2GUYtUL7mMWlGBM4Gjw/edit?usp=sharing

hartm (Tue, 08 Dec 2020 02:39:35 GMT):
Above: basic doc on vulnerability disclosure processes.

githubckgoh1439 (Tue, 08 Dec 2020 08:01:40 GMT):
Has joined the channel.

rjones (Tue, 08 Dec 2020 18:29:17 GMT):
https://github.com/hyperledger/cactus/issues/419

jorgeRodriguez (Wed, 09 Dec 2020 17:54:06 GMT):
Has joined the channel.

peter_somogyvari (Wed, 09 Dec 2020 18:24:41 GMT):
2020-12-10 Cactus Contributors Western Hemisphere Agenda is up: https://wiki.hyperledger.org/display/cactus/2020-12-10+Cactus+Contributors+Western+Hemisphere+Agenda As usual, feel free to add more items or just show up and then grab the mic at the ad-hoc discussion part of the meeting .

peter_somogyvari (Mon, 14 Dec 2020 19:44:08 GMT):
Our last two meetings for the year of 2020 now both have agenda documents posted, feel free to add new items as usual: 2020-12-15 Cactus Maintainers Agenda: https://wiki.hyperledger.org/display/cactus/2020-12-15+Cactus+Maintainers+Agenda 2020-12-17 Cactus Contributors Western Hemisphere Agenda: https://wiki.hyperledger.org/display/cactus/2020-12-17+Cactus+Contributors+Western+Hemisphere+Agenda

peter_somogyvari (Wed, 16 Dec 2020 00:58:20 GMT):
FYI: we'll be renaming the default branch of Cactus early next year. (This is a prior announcement to make sure everyone is ready/prepared) Here's more context https://github.com/hyperledger/cactus/issues/424 and GitHub's own explanation on how this might affect your day-to-day work in version control: https://github.com/github/renaming If anyone hits any issues with git mechanics, feel free to hit me up on the mailing list or on Rocket Chat. Happy to help.

rjones (Wed, 16 Dec 2020 16:29:23 GMT):
@peter_somogyvari might make a nice announcement for this week's newsletter

takeutak (Mon, 21 Dec 2020 07:15:31 GMT):
Thank you and sorry for late replying. I updated the tutorial of examples/cartrade. Could you please try following this README?

takeutak (Mon, 21 Dec 2020 07:15:31 GMT):
@luckyrobinson Thank you and sorry for late replying. I updated the tutorial of examples/cartrade. Could you please try following this README?

RafaelAPB (Mon, 21 Dec 2020 22:22:16 GMT):
A WEF report on blockchain interoperability: http://www3.weforum.org/docs/WEF_Interoperability_C4IR_Smart_Contracts_Project_2020.pdf

peter_somogyvari (Tue, 22 Dec 2020 04:38:55 GMT):
Thank you for continuing to provide me with curated reading materials! :-) (still not done with the accountability paper, but getting there)

RafaelAPB (Tue, 22 Dec 2020 16:50:42 GMT):
Awesome. That one for sure is a good paper :)

hartm (Wed, 23 Dec 2020 15:26:09 GMT):
Candidate names: threshold (for actual implementation and BLS), T-Shnorr (for one round Schnorr), T-2Round-Group (for ECDSA and BBS+).

peter_somogyvari (Mon, 04 Jan 2021 18:11:08 GMT):
Meeting agendas posted for the week: https://wiki.hyperledger.org/display/cactus/2021-01-05+Cactus+Maintainers+Agenda https://wiki.hyperledger.org/display/cactus/2021-01-07+Cactus+Contributors+Western+Hemisphere+Agenda

peter_somogyvari (Mon, 04 Jan 2021 18:13:33 GMT):
@hartm Apologies, I'm totally lost/forgotten the topic. What are we giving a name to?

rjones (Mon, 04 Jan 2021 18:45:03 GMT):
@peter_somogyvari I touched your recurring meeting invite - is this time correct? https://lists.hyperledger.org/g/cactus/viewevent?repeatid=32482&eventid=1023000&calstart=2021-01-05

rjones (Mon, 04 Jan 2021 18:45:18 GMT):
I'm suspicious that somehow my personal timezone clobbered yours

hartm (Mon, 04 Jan 2021 18:45:22 GMT):
Wrong chat, sorry! This was supposed to go in the Ursa chat.

peter_somogyvari (Mon, 04 Jan 2021 18:45:36 GMT):
Checking

peter_somogyvari (Mon, 04 Jan 2021 18:47:17 GMT):
Correct still IMO, it's at CST 8 PM which is Pacific 6 PM which is the expected time, no clobbering. :-)

peter_somogyvari (Mon, 04 Jan 2021 18:47:17 GMT):
Correct still IMO, it's at CST 8 PM which is Pacific 6 PM which is the expected time, no clobbering. :-) @rjones

rjones (Mon, 04 Jan 2021 18:47:56 GMT):
on Monday, today, though?

rjones (Mon, 04 Jan 2021 18:48:29 GMT):

Screen Shot 2021-01-04 at 10.48.20 AM.png

peter_somogyvari (Mon, 04 Jan 2021 18:48:39 GMT):
Ahh, okay! No worries at all, I was concerned that I completely forgot about something that we may or may not have talked about before the long holiday break. ;-)

peter_somogyvari (Mon, 04 Jan 2021 18:49:25 GMT):
It's Monday in the US time zones, but crosses over to actually being Tuesday in GMT (and because of that we usually put down the date of Tuesdays in the meeting agenda titles for example)

rjones (Mon, 04 Jan 2021 18:49:53 GMT):
OK, right, I'm in UTC with this account. Where are you?

peter_somogyvari (Mon, 04 Jan 2021 18:50:02 GMT):
Pacific

rjones (Mon, 04 Jan 2021 18:50:21 GMT):
OK. if it's right, it's right :)

peter_somogyvari (Mon, 04 Jan 2021 18:51:33 GMT):
I think it's correct yeah, it never showed it in my own time zone anyway for some reason it always showed it in the time zone of the person who created the meeting (originally it was Jonathan I think and he is in central)

peter_somogyvari (Mon, 04 Jan 2021 18:51:49 GMT):

Screenshot from 2021-01-04 10-50-10.png

peter_somogyvari (Mon, 04 Jan 2021 18:52:03 GMT):
So I'm seeing it in central despite me being in Pacific

peter_somogyvari (Mon, 04 Jan 2021 18:52:17 GMT):
(still has the correct time, just a fun fact)

rjones (Mon, 04 Jan 2021 18:52:28 GMT):
If you want to cancel the series and recreate it, I'm fine with it.

peter_somogyvari (Mon, 04 Jan 2021 18:53:00 GMT):
I'm good thank you, know it by heart now anyways :-)

hartm (Tue, 05 Jan 2021 02:08:57 GMT):
By the way--we have the quarterly report due next week. I can take point on a first draft if people want me to do so.

peter_somogyvari (Tue, 05 Jan 2021 21:54:31 GMT):
@rjones Sent you a join request on BinTray => https://bintray.com/hyperledger-org

rjones (Tue, 05 Jan 2021 22:30:27 GMT):
approved

peter_somogyvari (Tue, 05 Jan 2021 22:30:42 GMT):
Thank you very much!

rjones (Tue, 05 Jan 2021 22:31:05 GMT):
sure thing. I'm sure there will be more I need to do to enable you - just let me know when you hit a blocker

rjones (Tue, 05 Jan 2021 22:34:50 GMT):
you should have permissions to create repos now

peter_somogyvari (Tue, 05 Jan 2021 22:35:34 GMT):
@rjones Going off-topic: on dockerhub it still only lets me select the bot when linking github to the repo (and then the bot doesn't have anything in the next dropdown)

rjones (Tue, 05 Jan 2021 22:35:53 GMT):
I totally forgot about that, sorry

peter_somogyvari (Tue, 05 Jan 2021 22:38:57 GMT):
No worries, just checking in! Still not urgent, but figured it's worth a bump! :-)

peter_somogyvari (Tue, 05 Jan 2021 22:42:35 GMT):
Verified, permission works to create repos. Can I get more permissions to rename (or delete) repos as well? I already made a mistake where I gave the repo the name that was meant to be the name of a package inside the repo... :fearful:

rjones (Tue, 05 Jan 2021 23:20:37 GMT):
you're an admin, you have as much permission as I do, I think

rjones (Tue, 05 Jan 2021 23:22:02 GMT):
If you go here: https://bintray.com/beta/#/hyperledger-org/cactus-api-client/edit

rjones (Tue, 05 Jan 2021 23:22:11 GMT):
in the upper right, do you have a "delete" button?

rjones (Tue, 05 Jan 2021 23:22:50 GMT):
if not, I'll do it @peter_somogyvari

peter_somogyvari (Tue, 05 Jan 2021 23:29:15 GMT):
Got it, button was there. I swear I didn't see it before /facepalm :-D

peter_somogyvari (Tue, 05 Jan 2021 23:29:22 GMT):
Thank you very much!

rjones (Tue, 05 Jan 2021 23:29:40 GMT):
sure thing! Took me a while to find it, as well

RafaelAPB (Thu, 07 Jan 2021 15:26:24 GMT):
That would be nice. I can collaborate on the report by pointing out the developments on the paper, if you think it's worth it (we did not write that much so far).

RafaelAPB (Thu, 07 Jan 2021 15:26:24 GMT):
That would be nice @hartm . I can collaborate on the report by pointing out the developments on the paper, if you think it's worth it (we did not write that much so far).

rjones (Thu, 07 Jan 2021 18:03:22 GMT):
well, I figured it out. Go forth and set up as you like :)

peter_somogyvari (Thu, 07 Jan 2021 18:04:37 GMT):
It works!!! Thank you very much! What was the issue, I'm curious :-)

rjones (Thu, 07 Jan 2021 18:04:50 GMT):
the GitHub account must be an org owner, which is insane.

peter_somogyvari (Thu, 07 Jan 2021 18:05:04 GMT):
Ouch. That is insane...

peter_somogyvari (Thu, 07 Jan 2021 18:05:47 GMT):
Thought they'd allow you to apply the least privilege principle and use some stripped down account that can pretty much only read the code and that's it.

rjones (Thu, 07 Jan 2021 18:05:57 GMT):
hahahaha

takeutak (Fri, 08 Jan 2021 09:59:47 GMT):
@peter_somogyvari Thank you for chaging default branch to "main". It's very cool! By the way, Cactus GitHub toppage is still "master", since "master" is default branch in the current status as GitHub system. https://github.com/hyperledger/cactus Could you delete master branch or switch main as default branch?

takeutak (Fri, 08 Jan 2021 10:03:32 GMT):
@peter_somogyvari It seems that this guideline shows how to switch default branch. https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/changing-the-default-branch

rjones (Fri, 08 Jan 2021 15:05:45 GMT):
@takeutak I've updated it

rjones (Fri, 08 Jan 2021 15:12:34 GMT):
https://github.com/hyperledger/cactus/pull/461 https://github.com/hyperledger/cactus/pull/460

rjones (Fri, 08 Jan 2021 15:13:09 GMT):
@peter_somogyvari please merge in the order 461, 460

peter_somogyvari (Fri, 08 Jan 2021 16:34:25 GMT):
@takeutak Oops, thanks for the heads up. Seems like I did everything except the most important step, no idea how I forgot it. /faceplalm Switched it over now!

peter_somogyvari (Fri, 08 Jan 2021 16:35:42 GMT):
Hmm, then maybe something is wrong on Github's end because I just went there a minute ago and it was still master as the default in the settings. Maybe I haven't forgotten after all.

rjones (Fri, 08 Jan 2021 16:35:51 GMT):
@peter_somogyvari you need to merge my two PRs

rjones (Fri, 08 Jan 2021 16:36:38 GMT):
merge 461, 460

peter_somogyvari (Fri, 08 Jan 2021 16:37:01 GMT):
Ohh, it's the config file. Okay. Apologies. :-)

rjones (Fri, 08 Jan 2021 16:37:16 GMT):
merge in that order ;)

rjones (Fri, 08 Jan 2021 16:45:55 GMT):
https://github.com/hyperledger/cactus is now using `main`. I would suggest not deleting `master` branch for some time.

peter_somogyvari (Fri, 08 Jan 2021 16:52:41 GMT):
Gonna delete it right now

hartm (Sat, 09 Jan 2021 00:34:32 GMT):
I've created a first version of our quarterly report. Please feel free to edit it as you like. In particular, add things to "overall activity" and "current plans" that you'd like the TSC to see. Thanks everyone! Link: https://wiki.hyperledger.org/display/TSC/2021+Q1+Hyperledger+Cactus

hartm (Tue, 12 Jan 2021 03:03:58 GMT):
Was the meeting wrong on my calendar? It was at 6:00, right?

peter_somogyvari (Wed, 13 Jan 2021 17:27:41 GMT):
Yeah, I think your calendar somehow ended up with the old version of the calendar invite. (sorry for the slow response)

hartm (Wed, 13 Jan 2021 18:28:56 GMT):
Nah, my fault totally. I was just obliviously working along and blindly following my calendar...

hartm (Wed, 13 Jan 2021 18:29:28 GMT):
But yeah, I think that's what happened. Guess I need to do a calendar sync.

hartm (Wed, 13 Jan 2021 18:29:56 GMT):
Should be a pretty light agenda for us tomorrow: https://wiki.hyperledger.org/display/TSC/2021+01+14+TSC+Meeting+Record

peter_somogyvari (Wed, 13 Jan 2021 19:15:35 GMT):
@sfuji822 Working on my couple of slides for the language independence, will send it out shortly. Sorry for leaving it to the last minute!

hartm (Wed, 13 Jan 2021 19:18:36 GMT):
No worries!

peter_somogyvari (Wed, 13 Jan 2021 19:29:46 GMT):
@sfuji822 Here are the slides: First part is about the language independence and then the call to action for contributions: https://docs.google.com/presentation/d/1QOn9JJSqqF6c-1RpWzIq6YuxaB29oW3SBXq9vi5z75I/edit?usp=sharing

peter_somogyvari (Wed, 13 Jan 2021 22:23:48 GMT):
Fun fact, I got an email from the HL calendar just now reminding me that there's a TSC call on the 5th of November, 2020 :D => Technical Steering Committee (TSC) When: Thursday, 5 November 2020 7:00am to 8:00am (UTC-08:00) America/Los Angeles Repeats: Weekly on Thursday

hartm (Wed, 13 Jan 2021 22:24:52 GMT):
I still occasionally get notifications for the original TSC meetings that were on webex! It's like some kind of ghost is haunting me.

hartm (Wed, 13 Jan 2021 22:29:46 GMT):
I actually just got that Nov. 2020 notification too. Weird.

peter_somogyvari (Thu, 14 Jan 2021 23:38:19 GMT):
@rjones Could you please create a couple more repos for some new images coming down the pipe on DockerHub? `hyperledger/cactus-keychain-vault-server` and `hyperledger/cactus-corda-4-6-all-in-one-obligation` ?

rjones (Thu, 14 Jan 2021 23:58:58 GMT):
[one](https://hub.docker.com/repository/docker/hyperledger/cactus-corda-4-6-all-in-one-obligation) [two](https://hub.docker.com/repository/docker/hyperledger/cactus-keychain-vault-server)

rjones (Thu, 14 Jan 2021 23:59:05 GMT):
@peter_somogyvari permissions are the same

peter_somogyvari (Thu, 14 Jan 2021 23:59:26 GMT):
Thank you very much!!!

peter_somogyvari (Fri, 15 Jan 2021 00:02:17 GMT):
Success, I have the rights to set up the auto-build, awesome, thank yo uagain!

VipinB (Wed, 20 Jan 2021 14:18:18 GMT):
Hello everyone, This is to bring DCGI (Digital Currency Global Initiative) to your attention. DCGI is a collaboration between ITU-T (an arm of ITU, a UN special agency) and Stanford U business school. ITU-T is a standards body, it has been involved in some important technical standards such as MP3. More than 197 national bodies and private enterprises are involved in ITU. Digital Currencies that DCGI is looking at includes Crypto-Currencies, CBDC (both wholesale and retail), Stablecoins and e-Money (or private money). The Interoperability WS will create technical recommendations for standards development. We are engaging with ISO, and some other standards bodies as well. There are three working groups with sub workstreams; one of them is the Interoperability workstream inside the Policy & Governance WG. I am the vice-chair of this group and would like to bring Hyperledger Cactus into the discussion. Please reply to this or email to engage.-

sfuji822 (Thu, 21 Jan 2021 02:32:46 GMT):
Hi @VipinB , thanks for contacting us. I suggest you arrange an online discussion as part of the CACTUS contributors meeting or a dedicated meeting. Anyway, what time zone you are living in?

VipinB (Thu, 21 Jan 2021 07:43:45 GMT):
EST-

ajayjadhav (Thu, 21 Jan 2021 12:11:16 GMT):
Has left the channel.

hartm (Thu, 21 Jan 2021 15:00:28 GMT):
The weekly dev newsletter is looking for submissions, in case anyone is interested: https://wiki.hyperledger.org/display/DR/2021

sfuji822 (Fri, 22 Jan 2021 03:08:22 GMT):
We are holding weekly zoom meetings every Monday at 31:00 in EST. https://lists.hyperledger.org/g/cactus/calendar I believe you can bring discussion materials to the meeting. If the time does not work for you, can you suggest dedicated meeting to exchange our thoughts.

sfuji822 (Fri, 22 Jan 2021 03:08:22 GMT):
We are holding weekly zoom meetings every Monday at 21:00 in EST. https://lists.hyperledger.org/g/cactus/calendar I believe you can bring discussion materials to the meeting. If the time does not work for you, can you suggest dedicated meeting to exchange our thoughts.

peter_somogyvari (Tue, 26 Jan 2021 01:54:17 GMT):
Maintainer's calls agenda is up: https://wiki.hyperledger.org/display/cactus/2021-01-26+Maintainers+Agenda

peter_somogyvari (Tue, 26 Jan 2021 21:44:50 GMT):
@rjones Auto-merge is my new favorite feature on GitHub, thanks for the tip earlier! :-)

rjones (Tue, 26 Jan 2021 22:06:49 GMT):
I love it

RafaelAPB (Wed, 27 Jan 2021 20:29:32 GMT):
Hey Cactus community! I'm working with the Internet Engineering Task Force on defining a digital asset protocol that can be used by enterprises - ODAP. https://www.ietf.org/archive/id/draft-hargreaves-odap-01.txt https://datatracker.ietf.org/doc/draft-belchior-gateway-recovery/ The work that we are doing at Cactus is quite important, IMO, for this protocol. If anyone is interested in contributing, please let me know.

jgiron (Thu, 28 Jan 2021 08:02:16 GMT):
Has joined the channel.

ac77ra (Thu, 28 Jan 2021 08:57:42 GMT):
Has joined the channel.

E.alcazar (Thu, 28 Jan 2021 09:05:24 GMT):
Has joined the channel.

peter_somogyvari (Fri, 29 Jan 2021 02:50:29 GMT):
@RafaelAPB Count me in. Is there anything specific as a task that I can pick up and work on regarding this?

peter_somogyvari (Fri, 29 Jan 2021 19:01:05 GMT):
2021-02-02 Maintainers Agenda is up: https://wiki.hyperledger.org/display/cactus/2021-02-02+Maintainers+Agenda

RafaelAPB (Sat, 30 Jan 2021 03:54:50 GMT):
I'm planning to do the ODAP gateway implementation on Cactus, so if I struggle with anything, i'll let you know :) Besides, if you want to directly contribute at IETF, feel free to DM

hartm (Mon, 01 Feb 2021 19:53:26 GMT):
I'd like to discuss this today, if possible, and will add it to the agenda: https://linuxfoundation.smapply.io/prog/hyperledger_global_forum_2021/

hartm (Mon, 01 Feb 2021 19:53:47 GMT):
Guess someone added it already. Perfect!

hartm (Mon, 01 Feb 2021 20:01:24 GMT):
I think we should probably propose multiple talks and let the committee sort out which ones they think fit best. Of note: "CFP must be submitted in English; however, talks can be presented in your language of choice. In particular, we’d love to see talks in Chinese, Spanish, Portuguese, and Japanese." I'm thinking we could propose some foreign language talks @takeutak @sfuji822 @RafaelAPB

E.alcazar (Fri, 05 Feb 2021 08:39:35 GMT):
That's a great idea! I can help doing a presentation on Spanish I'm also trying to move the same thing for Hyperledger local events, I can help accelerate that if you guys want to do a presentation in your language in your region

peter_somogyvari (Tue, 09 Feb 2021 02:25:41 GMT):
FYI: I just cancelled the maintainer's call that's 2 weeks from now as we discussed in tonight's call.

chakshujain (Wed, 10 Feb 2021 09:26:08 GMT):
Has joined the channel.

jmc171144 (Fri, 12 Feb 2021 15:31:34 GMT):
Has joined the channel.

jmc171144 (Fri, 12 Feb 2021 15:31:35 GMT):
Hello everyone, I've been interested in HL cactus lately and I saw in a survey that: "The roadmap predicts integration with public blockchains" but I can't find any info about it. Does the roadmap predict integration with public blockchains? If anyone can help me with this it would be very nice!

hartm (Fri, 12 Feb 2021 15:56:29 GMT):
Hello! Are you asking if we plan to support public blockchains with Cactus? If so, the answer is yes, although there are some caveats (for instance, integration with bitcoin requires some extra assumptions).

jmc171144 (Mon, 15 Feb 2021 07:13:06 GMT):
Ok thanks! Yes I wanted to know if some public blockchain integrations were planned in the 2021 roadmap or if this remains an ambition?

E.alcazar (Mon, 15 Feb 2021 10:34:48 GMT):
Theoretically it already supports Ethereum through the Besu connector plugin, and the HTLC plugins we are about to merge. It's theoretical because AFAIK we haven't tested it yet, we are still in early stages implementation-wise. If you have a specific suggestion or idea, we encourage you to join one of our meetings and collaborate with the team to develop new plugins :grinning:

peter_somogyvari (Mon, 15 Feb 2021 18:45:51 GMT):
@rjones What's the algorithm to find a free zoom link if I want to introduce a new daily meeting to do Cactus pair programming? I created the calendar entry[1] but wasn't sure what zoom link I could put in there for people to join because it's at the busiest time of the day with 3-4 other meetings running at the same time with zoom links. :/ [1]: https://lists.hyperledger.org/g/cactus/viewevent?repeatid=35080&eventid=1059700&calstart=2021-02-15 We could also just use a google meets link, but I don't know if we are supposed to do that or should stick specifically to the HL Zoom.

rjones (Mon, 15 Feb 2021 19:02:30 GMT):
@peter_somogyvari you could use Google if you like, but in the near-ish future, Zoom meetings will become a) much easier b) mandatory

rjones (Mon, 15 Feb 2021 19:03:09 GMT):
Basically, there won't be "hyperledger Zoom" accounts any more, there will be a pool of API keys that are used

rjones (Mon, 15 Feb 2021 19:03:24 GMT):
but that is late q2 or q3

rjones (Mon, 15 Feb 2021 19:04:03 GMT):
do you have a second for a quick zooooom?

peter_somogyvari (Mon, 15 Feb 2021 19:04:15 GMT):
Hehe, I suspected b) was either already happening or has happened. Thanks for the info. :-) Yeah, sure thing

rjones (Mon, 15 Feb 2021 19:04:33 GMT):
https://zoom.us/my/ry.jones?pwd=RTJ1Q0R2aXVoNi8xajZ6SlM4SzVqQT09

peter_somogyvari (Mon, 15 Feb 2021 19:11:25 GMT):
Upcoming Maintainer Call Agenda: https://wiki.hyperledger.org/display/cactus/2021-02-16+Cactus+Maintainers+Agenda

rjones (Mon, 15 Feb 2021 19:11:35 GMT):
well, the automation is "Ry looks at the calendar" :)

peter_somogyvari (Mon, 15 Feb 2021 19:31:09 GMT):
:grinning:

peter_somogyvari (Mon, 15 Feb 2021 19:38:56 GMT):
We’ve created a regular call that runs from 8:00 to 8:30 AM Pacific Time every week day: https://lists.hyperledger.org/g/cactus/viewevent?repeatid=35080&eventid=1059700&calstart=2021-02-15 Feel free to drop by anytime and ask code related questions from maintainers/contributors. Questions can be ranging anywhere from starting a contribution/building the code to finalizing PR reviews. It’s an informal setting where no issue is too small to be brought up: If you show up, share your screen and we figure out that a semicolon was missing and that’s why it wasn’t working, that’s a great outcome and the meeting will have worked as intended. There’s no pressure or barrier to entry as long as it’s related to Cactus, we’ll be glad to discuss it on the call in a first come first serve ad-hoc basis.

RafaelAPB (Tue, 16 Feb 2021 20:12:20 GMT):
Hello All! I won't be able to show up at this week's meeting. If discussing the papers, please feel free to reach out after.

AllanLundHansen (Fri, 19 Feb 2021 11:17:18 GMT):
Has joined the channel.

AllanLundHansen (Fri, 19 Feb 2021 11:57:58 GMT):
please excuse me if this is a complete noob question, and if the concept is misunderstood, but I am curious of the election process of the validator nodes for the different DLTs, also is there a list of the current ones?

hartm (Fri, 19 Feb 2021 15:57:31 GMT):
What do you mean by "election process?"

AllanLundHansen (Fri, 19 Feb 2021 16:15:18 GMT):
Maybe a rephrasing is better: "The Cactus consortium operates for each connected blockchain a group of validator nodes, which as a group provides the proofs of the state of the connected ledger" (from whitepaper) so the question relates to who are validator nodes? How do they get to be designated as such? And who is the governing body that choose validator nodes?

hartm (Fri, 19 Feb 2021 23:17:25 GMT):
Ah, thanks for explaining. Whoever is running the particular Cactus consortium in question gets to choose who the validator nodes are (or what the process is to select them). Or goal with Cactus is to make this as flexible as possible since we suspect that many different people who want to use Cactus will have different needs and choices for validator sets.

AllanLundHansen (Sat, 20 Feb 2021 08:01:20 GMT):
That sounds great thank you for the answer!

takeutak (Mon, 22 Feb 2021 06:20:31 GMT):
@peter_somogyvari (cc: @jham)

takeutak (Mon, 22 Feb 2021 06:21:46 GMT):
Hi, @peter_somogyvari ! (cc: @JHamilton @sfuji822 @hartm ) I am looking at implementing code to run cactus-ledger-connector-besu (or fabric, quorum) from the Ledger Plugin Verifier . Therefore, I'm currently investigating Peter's codes, but there are some things that I cannot understand yet. Would you mind if you answer the following two questions (1) and (2) ? (1) As I surveyed, cactus-ledger-connector-besu can be called with a RESTful OpenAPI, and I think the call is what the OpenAPI Generator does. I think the definition of API to create is written in openapi.json below. * Besu: signTransactionRequest "transactionHash", "keychainId", "keychainRef" * Fabric: RunTrasactionRequest "keychainId", "keychainRef", "channelName", "chainCodeId", "invocationType", "functionName", "functionArgs" Then, let me question about it. Could you mind if you tell me what parameter values are specifically assigned to these parameters in a sample application such as supply-chain-app? For example, it would be helpful if you could tell me the relevant part of the code. (2) After the transaction was issued by cactus-ledger-connector-besu (or fabric, quorum), did you obtain the response for the transaction result in this code? So does it include some kind of blockchain monitoring? If you have some kind of monitoring function, it would be helpful if you could tell me the relevant part of the code.

peter_somogyvari (Mon, 22 Feb 2021 07:32:38 GMT):
@takeutak 1) Sure thing, here are some relevant parts of the code: - examples/cactus-example-supply-chain-frontend/src/app/bamboo-harvest/bamboo-harvest-list/bamboo-harvest-list.page.ts ( method name: `clickAddNew()` ) - examples/cactus-example-supply-chain-frontend/src/app/bookshelf/bookshelf-list/bookshelf-list.page.ts `clickAddNew()` method - examples/cactus-example-supply-chain-business-logic-plugin/src/main/typescript/business-logic-plugin/web-services/insert-bamboo-harvest-endpoint.ts `handleRequest` method - examples/cactus-example-supply-chain-business-logic-plugin/src/main/typescript/business-logic-plugin/web-services/insert-bookshelf-endpoint.ts `handleRequest` method 2) Yes: Immediately available transaction results are sent back with the HTTP response. There's no support for streaming/monitoring events so if your smart contract uses events then polling is necessary at the moment (once we have the websocket/gRPC support this will improve of course)

hartm (Mon, 22 Feb 2021 18:43:41 GMT):
We did cancel today's meeting, right?

peter_somogyvari (Mon, 22 Feb 2021 19:21:01 GMT):
That's right

hartm (Mon, 22 Feb 2021 19:22:35 GMT):
Great, thanks! Just wanted to make sure.

peter_somogyvari (Tue, 23 Feb 2021 02:07:46 GMT):
Ghosts are chasing me too now. I just got the email reminder for the meeting that I distinctively remember cancelling myself in the HL calendar. I went and double checked and the meeting is there (despite me also remembering that I had double checked it not being there before!)

peter_somogyvari (Tue, 23 Feb 2021 02:08:09 GMT):
(just a fun fact)

takeutak (Thu, 25 Feb 2021 08:42:29 GMT):
@peter_somogyvari Thank you for the information! It helps me a lot. What I want to ask is what parameters are specifically assigned to "transactionHash", "keychainId" and "keychainRef" (or "keychainId", "keychainRef", "channelName", "chainCodeId", "invocationType", "functionName", "functionArgs"). Is there an appropriate code?

hartm (Thu, 25 Feb 2021 15:33:19 GMT):
Do we have a western meeting today? If so, I apologize--I'll be late.

peter_somogyvari (Thu, 25 Feb 2021 16:13:21 GMT):
I think it's next week, can't see it on the calendar for today

hartm (Thu, 25 Feb 2021 16:28:34 GMT):
You're right. Sorry--just swamped and losing mental track of my meetings!

peter_somogyvari (Fri, 26 Feb 2021 19:21:34 GMT):
@takeutak Maybe these ones helps more with the keychain related parameters (let me know if it's still unclear, I can try and provide more code location links): https://github.com/hyperledger/cactus/blob/main/examples/cactus-example-supply-chain-backend/src/main/typescript/supply-chain-app.ts#L147 https://github.com/hyperledger/cactus/blob/main/examples/cactus-example-supply-chain-backend/src/main/typescript/supply-chain-app.ts#L87 As for the other parameters, I'm not sure I understand the question, the parameters you listed are being assigned in the code sections that I pointed to in my earlier message. There you can see those parameters being assigned to from other values so I thought that would answer what is is that's being set for those parameters "specifically" because it's literally right there in the code what assignments are.

peter_somogyvari (Mon, 01 Mar 2021 23:12:45 GMT):
2021-03-02 Cactus Maintainers Agenda => https://wiki.hyperledger.org/display/cactus/2021-03-02+Cactus+Maintainers+Agenda

baziorek (Wed, 03 Mar 2021 09:17:43 GMT):
Has joined the channel.

baziorek (Thu, 04 Mar 2021 13:33:40 GMT):
Hello, I'm new in Cactus, or rather I'm thinking about being new in Cactus. I've watched intro video (https://www.youtube.com/watch?v=IHy-5sbMrYs) - everything looks good, but I need to ask hard question - what are practical disadvantages of Cactus? I'm asking because I've checked Quilt (https://www.hyperledger.org/use/quilt) and integration with Iroha (https://wiki.hyperledger.org/display/INTERN/HL+Iroha+and+HL+Quilt+Integration) and I've found some disadvantages. I know some disadvantages of Quilt and I need to know what are disadvantages of Cactus to compare what is better interledger communication project? To be more specific, are those disadvantages in Cactus (there are in Quilt as I know): - Tokens can be added but not taken from source account - Accounts between networks should be "copied" to Quilt's node - Credit for accounts - impossible to not have credit. If You don't want to answer me on public please tell me through priv message:D.

RafaelAPB (Thu, 04 Mar 2021 21:10:30 GMT):
Hello @baziorek. I've done some work on interoperability that could answer your questions: https://arxiv.org/pdf/2005.14282.pdf A new version, with a comparative framework is about to come out. Hope that helps

RafaelAPB (Thu, 04 Mar 2021 21:12:01 GMT):
Adding a bit, the main disadvantage of Cactus right now is that cross-chain communication across a set of members cannot be "enforced" - the price to pay for heterogeneous interoperability with arbitrary business logic. But we are working on it.

baziorek (Thu, 04 Mar 2021 21:49:17 GMT):
@RafaelAPB If I understood You correctly - it is possible that when transferring between networks it is possible that some of tokens would not be transferred from account A, but will be transferred to account B

baziorek (Thu, 04 Mar 2021 21:50:01 GMT):
______ Is there any roadmap for Cactus: when more interactions between different blockchains would be implemented?

RafaelAPB (Fri, 05 Mar 2021 13:16:56 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=SNjzyzJEbb99rnPYm) I don't understand what you mean

RafaelAPB (Fri, 05 Mar 2021 13:17:44 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=kAqkNYzzTnXt4oWKC) That behavior is encoded in business logic plugins. Currently there are a few; cross-chain atomic swaps on the way (using HTLCs you could have n-party cross-swaps)

baziorek (Sat, 06 Mar 2021 11:26:19 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=JLzFRSxwSyqPTFkSZ) Sorry for not precise question. I meen situation like that: 1. bob in blockchain1 wants to send 1 * token1 to alice in blockchain2. So is it possible that bob sends but alice would not receive? Or alice receive but bob would not send (e.g. because suddenly he will not have enough balance)?

kenty (Sat, 06 Mar 2021 16:02:23 GMT):
Has joined the channel.

baziorek (Sat, 06 Mar 2021 17:18:40 GMT):
I'm having questions, because I'm proposing Hyperledger Internship Project to connect Cactus and Hyperledger Iroha, so my questions (deadline for submissions is 8th March): 1. Is anybody adding integration between Iroha and Cactus? I don't want to duplicate work. 2. To integrate Cactus with other blockchain is necessarily to just code plugin and run Cactus with the plugin? (I was reading documentation, but I need to make sure, since I'm really new). 3. Plugin can be coded in any programming language, since Cactus is using REST API (https://github.com/hyperledger/cactus/blob/main/whitepaper/whitepaper.md#53-apis-and-communication-protocols-between-cactus-components)? Or it must be in TypedScript as rest of implemented plugins? 4. Is it allowed to integrate two networks of the same blockchain, e.g. Two separate Fabric networks to transfer with Cactus?

RafaelAPB (Sat, 06 Mar 2021 21:16:42 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=2JLmmxPdyfRppRKSx) No, if this is implemented via HLTCs or via gateways - please see Hermes: https://web.ist.utl.pt/~ist180970/papers/2021/hermes-middleware-2021.pdf

RafaelAPB (Sat, 06 Mar 2021 21:17:58 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=sC2KSjGPeRw6BpKud) I think @peter_somogyvari is the most qualified person to answer that, but I'll try: 1) I don't think so 2) "just"? 3) PLease ask Peter 4) Yes!

peter_somogyvari (Sun, 07 Mar 2021 05:16:29 GMT):
@baziorek 1. Nobody is working on it as far as I'm aware (so chances are that no one is). With that said it would be a most welcome contribution for sure so thank you for considering/doing this! 2. Yes, it's not easy to make it so, but this is one of our core design principles and have been focusing on this a lot when it comes to architecture. 3. Yes. We have a working example of a plugin that was written in Rust here for example: https://github.com/hyperledger/cactus/tree/main/packages/cactus-plugin-keychain-vault/src/cactus-keychain-vault-server It's a standalone web server capable of serving API requests conformant what is in the openapi spec file here: https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-keychain-vault/src/main/json/openapi.json The example above is not an example of a ledger connector plugin but instead is a keychain plugin, but the concept is the same: If you want to implement a plugin that runs on something other than NodeJS then on top of implementing your plugin logic you will also have to implement the web server part, but for this I recommend using the OpenAPI generator instead of rolling your own (I used the rust template to generate the linked keychain plugin above). As another example we have the recently added (and for now kinda half-baked) corda plugin which follows the same pattern but instead of rust it is a JVM spring boot app written in Kotlin: https://github.com/hyperledger/cactus/tree/main/packages/cactus-plugin-ledger-connector-corda/src/main-server And again, the only code I actually wrote was the code that implements the REST endpoints, all the other boilerplate is auto-generated from the OpenAPI specs that we give you. This is how the corda connector generates it's API server boilerplate for example: https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-ledger-connector-corda/package.json#L16 4. Yes it is.Plugin instances have a uinque `instanceId` property which will allow us in the future to route requests to different plugin instances where they can be connected to separate ledgers of the same kind such as two distinct Fabric ledgers. 5. We have a daily pair programming call where everyone is welcome to join and ask about code, building, project setup, architectural decisions, etc. so feel free to drop by there as well and I'll be happy to chat about everything I just wrote in more detail or actually demonstrate how it all works: https://lists.hyperledger.org/g/cactus/viewevent?repeatid=35080&eventid=1059715&calstart=2021-03-08

Jane94 (Sun, 07 Mar 2021 05:59:01 GMT):
Has joined the channel.

peter_somogyvari (Sun, 07 Mar 2021 23:04:03 GMT):
Hi All, I've got nothing for our upcoming maintainer's meeting, should we cancel it or does anyone else have proposed agenda items? As for HGF submissions, I'm working on a couple of my own right now 1 for a supply chain app demo of Cactus and another for some kind of hands-on coding workshop (in the spirit of "everyone just submit everything they got and we'll figure it out later")

baziorek (Mon, 08 Mar 2021 08:13:35 GMT):
@peter_somogyvari Thanks for all answers. I've prepared internship proposal, now it is as draft, but I'd like to invite You to take a look before publishing, if You agree? I have few more questions (to precise description of proposal): 2. To sum up - to integrate Cactus with some blockchain it is enough to code *plugin*, but it is not easy task, am I right? But it is OK for summer internship (3 months), or rather too hard? 3. To sum-up technology to create plugin - the easiest is to code in NodeJS. It is also possible in other technologies (working implementations are in Rust, Kotlin) but it is necessarily to create also web-server, which can be generated with [openapi-generator] (https://openapi-generator.tech).

peter_somogyvari (Mon, 08 Mar 2021 14:01:58 GMT):
@baziorek My pleasure. Sure thing, I'm happy to take a look at the proposal as well if you have a link to the document. 2) I agree that it should be doable if they go with the path of least resistance for implementation which seems to be the option of using the Iroha JS client to implement the Cactus ledger connector plugin. Since the connector plugin runs in NodeJS and not the browser I assume we also don't need the grpc-web-proxy that the readme talks about here https://github.com/hyperledger/iroha-javascript So if the basic connectivity between the Cactus plugin and the Iroha ledger can be trivially established as above without further issues (not always the case), then the rest of the connector development is largely just about writing the open API specs file and then make sure that there's a compliant implementation and proper, end to end test coverage with pristine ledgers being pulled up in containers as part of the integration tests, like we do it here: https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-ledger-connector-fabric/src/test/typescript/integration/fabric-v1-4-x/run-transaction-endpoint-v1.test.ts I think this is doable in 3 months because for most of it there's existing examples just for other kinds of ledgers plus if they get stuck with anything we are available every day through the pair programming sessions as well. Plus, personally, if they really get stuck hard on something I don't mind jumping in and helping with the code itself either, usually it's just a matter of pinging me with a question and a link to your fork+branch name and I'll be happy to check it out. Note: since we consider end to end test coverage crucial for accepting pull requests I would recommend planning on finishing the connector itself ahead of time maybe in 2 months and then allocate the last month specifically for test coverage and hammering out the details (which I think is doable if one is provided with help whenever they get stuck which we are happy to provide) 3) Yes, all correct.

peter_somogyvari (Mon, 08 Mar 2021 14:01:58 GMT):
@baziorek My pleasure. Sure thing, I'm happy to take a look at the proposal as well if you have a link to the document. 2) Yes, all correct and I agree that it should be doable if they go with the path of least resistance for implementation which seems to be the option of using the Iroha JS client to implement the Cactus ledger connector plugin. Since the connector plugin runs in NodeJS and not the browser I assume we also don't need the grpc-web-proxy that the readme talks about here https://github.com/hyperledger/iroha-javascript So if the basic connectivity between the Cactus plugin and the Iroha ledger can be trivially established as above without further issues (not always the case), then the rest of the connector development is largely just about writing the open API specs file and then make sure that there's a compliant implementation and proper, end to end test coverage with pristine ledgers being pulled up in containers as part of the integration tests, like we do it here: https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-ledger-connector-fabric/src/test/typescript/integration/fabric-v1-4-x/run-transaction-endpoint-v1.test.ts I think this is doable in 3 months because for most of it there's existing examples just for other kinds of ledgers plus if they get stuck with anything we are available every day through the pair programming sessions as well. Plus, personally, if they really get stuck hard on something I don't mind jumping in and helping with the code itself either, usually it's just a matter of pinging me with a question and a link to your fork+branch name and I'll be happy to check it out. Note: since we consider end to end test coverage crucial for accepting pull requests I would recommend planning on finishing the connector itself ahead of time maybe in 2 months and then allocate the last month specifically for test coverage and hammering out the details (which I think is doable if one is provided with help whenever they get stuck which we are happy to provide) 3) Yes, all correct.

hartm (Mon, 08 Mar 2021 21:42:57 GMT):
Did we decide on the meeting?

JHamilton (Tue, 09 Mar 2021 00:24:20 GMT):
i assumed no responses as confirming cancel but if somoene else see otherwise please speak up :)

peter_somogyvari (Tue, 09 Mar 2021 00:26:08 GMT):
+1, I'll cancel it now

takeutak (Tue, 09 Mar 2021 00:42:49 GMT):
Could you wait for a cancellation? There is a possibility that there is an agenda.

takeutak (Tue, 09 Mar 2021 00:42:49 GMT):
@peter_somogyvari Could you wait for a cancellation? There is a possibility that there is an agenda.

takeutak (Tue, 09 Mar 2021 01:55:11 GMT):
@peter_somogyvari @JHamilton @sfuji822 @hartm At today's meeting, I would like to discuss the contents of the next release and commit to the README. If there is no other agenda, let's shorten today's meeting.

takeutak (Tue, 09 Mar 2021 01:55:11 GMT):
@peter_somogyvari @JHamilton @sfuji822 @hartm At today's meeting, I would like to discuss the contents of the next release and the some commits of README. If there is no other agenda, let's shorten today's meeting.

hartm (Tue, 09 Mar 2021 01:59:17 GMT):
We officially cancelled it already--are people still coming?

hartm (Tue, 09 Mar 2021 02:06:05 GMT):
In the future, let's affirmatively cancel 24 hours in advance if we're going to cancel. Once we cancel, let's not un-cancel either. Some people have to stay up late/get up early for meetings, so the affirmative, advance notice of a cancellation is really nice for these folks. Thanks!

E.alcazar (Tue, 09 Mar 2021 02:20:12 GMT):
https://github.com/hyperledger/cactus/issues/604

baziorek (Tue, 09 Mar 2021 09:49:04 GMT):
@peter_somogyvari Thanks for Your reply, I've sent You link to draft of proposal as private message.

Koushik (Tue, 09 Mar 2021 23:26:21 GMT):
Has joined the channel.

Koushik (Tue, 09 Mar 2021 23:38:30 GMT):
Hi guys/gals, I am really interested in cactus and specifically the interoperability problem that cactus is solving. However, when I looked at the github page it says a massive restructuring is being done. Can anyone point to the some documents that are relevant or suggest me that best starting point. I been using hyperledger fabric for the past 3-4 years and have some exp in the public blockchain space, want to learn more about cactus framework?

peter_somogyvari (Wed, 10 Mar 2021 07:50:24 GMT):
@Koushik You could take a look at the supply chain app example that we have. You can get started with a one liner shell command as long as you have a functioning docker installation on your machine. Link: https://github.com/hyperledger/cactus#supply-chain-example The code for the example demonstrates how an application developed using Cactus, leveraging multiple ledgers can look like and the code for it is in the packages here with the matching prefix: https://github.com/hyperledger/cactus/tree/main/examples Prefix: `cactus-example-supply-chain....` So I'd start there by running the example, looking at the code, etc. and if you have any questions feel free to drop by one of our daily pair-programming sessions where it's totally cool to ask even the smallest of questions regarding the code or the architecture at large. Link: https://lists.hyperledger.org/g/cactus/viewevent?repeatid=35080&eventid=1059717&calstart=2021-03-10 If the time zone is not a good fit then we can also schedule a pair programming session in a different one, this is something that we are planning to do anyway.

peter_somogyvari (Wed, 10 Mar 2021 21:04:17 GMT):
@rjones Could you please create (yet) another image on DockerHub? It's going to be for our Corda connector plugin's backend and this is the name I dreamt up: `hyperledger/cactus-connector-corda-server`

rjones (Thu, 11 Mar 2021 01:37:04 GMT):
lol no

rjones (Thu, 11 Mar 2021 01:40:05 GMT):
@peter_somogyvari go here to configure plz: https://hub.docker.com/repository/docker/hyperledger/cactus-connector-corda-server/builds

peter_somogyvari (Thu, 11 Mar 2021 16:02:04 GMT):
Thank you sir!

peter_somogyvari (Thu, 11 Mar 2021 16:47:39 GMT):
Hmm, is it possible that I did not get permissions for it like I did for the other ones? Can't seem to configure it (screenshot)

peter_somogyvari (Thu, 11 Mar 2021 16:47:50 GMT):

Screenshot from 2021-03-11 08-46-25.png

rjones (Thu, 11 Mar 2021 17:10:11 GMT):
try both

rjones (Thu, 11 Mar 2021 17:10:11 GMT):
try now

peter_somogyvari (Thu, 11 Mar 2021 17:11:03 GMT):
Awesome, now I have the extra buttons for the corda connector server too! Thank you very much!

peter_somogyvari (Fri, 12 Mar 2021 16:35:17 GMT):
Jonathan is out of office next week so I figured maybe we could do a trial run of the maintainer's call being in a slightly different time where it's a little easier for Enrique to dial in. Does this sound okay? If there isn't any opposition to the idea, we could converse further about which direction and how much the call could be moved. I for one am happy to have it later than it is planned (just an example).

peter_somogyvari (Fri, 12 Mar 2021 16:51:09 GMT):
Maybe like this one? https://www.timeanddate.com/worldclock/converter.html?iso=20210313T060000&p1=248&p2=224&p3=141

RafaelAPB (Fri, 12 Mar 2021 22:52:31 GMT):
Has anyone thought about the best way to benchmark Cactus?

rjones (Sat, 13 Mar 2021 00:10:21 GMT):
there is Caliper

hartm (Sat, 13 Mar 2021 02:15:32 GMT):
I'm not sure that Caliper has defined their tests in a way that makes sense for cross-blockchain transactions, although I haven't looked in a while.

rjones (Sat, 13 Mar 2021 04:06:43 GMT):
I'm sure Caliper would like some PRs to that end, tho.

hartm (Sat, 13 Mar 2021 04:07:31 GMT):
If it was as simple as a PR, I'd say just do it. But I imagine that it would involve re-litigating the performance metrics, which would be a time-consuming thing.

hartm (Sat, 13 Mar 2021 04:07:46 GMT):
Maybe we should have a conversation though.

RafaelAPB (Sat, 13 Mar 2021 21:31:49 GMT):
Perhaps that would be interesting - in the medium long term we will need this.

takeutak (Mon, 15 Mar 2021 08:24:13 GMT):
I would like to discuss the contents of the next release. Could you hold the meeting at the scheduled time? If it is difficult time-zone to participate for Enrique, I think it is a good idea to discuss in a new time frame different from the Maintainer meeting.

takeutak (Mon, 15 Mar 2021 08:24:13 GMT):
I would like to discuss the contents of the next release. Could you hold the meeting at the usual time? I would like to discuss how committers from different time zones like Enrique will participate in the meetings after next week.

takeutak (Mon, 15 Mar 2021 08:24:13 GMT):
I would like to discuss the contents of the next release. Could you hold the next meeting at the usual time? I would like to discuss how committers from different time zones like Enrique will participate in the meetings after next week.

takeutak (Mon, 15 Mar 2021 09:01:14 GMT):
2021-03-16 Cactus Maintainers Agenda https://wiki.hyperledger.org/display/cactus/2021-03-16+Cactus+Maintainers+Agenda

peter_somogyvari (Mon, 15 Mar 2021 14:54:28 GMT):
Yes, it's too late to change it now anyway.

peter_somogyvari (Mon, 15 Mar 2021 17:18:25 GMT):
All I'm going to say is: Containers containers containers. In other words, whatever we have, I want it to be runnable anywhere from a dev laptop to the data center without manual steps. The dream would be to have an npm script so that one can just say: `npm run benchmark` And this would run the speed tests with some mechanism baked in that can compare the results of different source code revisions so that any two commits can be compared and performance degradation detected automatically.

rjones (Mon, 15 Mar 2021 17:22:26 GMT):
(please build arm images for Mac)

peter_somogyvari (Mon, 15 Mar 2021 17:23:44 GMT):
On the to do list (though priority is not as high as it should be) https://github.com/hyperledger/cactus/issues/481

takeutak (Tue, 16 Mar 2021 01:43:58 GMT):
I am sorry that I couldn't attend the conference because I didn't notice the change of US time zone. Today's meeting will be held at the original scheduled time (19:00 PDT), right?

takeutak (Tue, 16 Mar 2021 01:43:58 GMT):
@peter_somogyvari @JHamilton @hartm @sfuji822 I am sorry that I couldn't attend the conference because I didn't notice the change of US time zone. Today's meeting will be held at the original scheduled time (19:00 PDT), right?

takeutak (Tue, 16 Mar 2021 01:43:58 GMT):
@peter_somogyvari @JHamilton @hartm @sfuji822 I am sorry that I couldn't attend the meeting because I didn't notice the change of US time zone. Today's meeting will be held at the original scheduled time (19:00 PDT), right?

hartm (Tue, 16 Mar 2021 01:56:12 GMT):
No worries! The original scheduled time was 6:00 ;). But yes, we are planning on rejoining at 7:00 (assuming zoom allows).

hartm (Tue, 16 Mar 2021 01:59:24 GMT):
In the future, you may want to subscribe to the (canonical) calendar through lists.hyperledger.org.

RealDeanZhao (Fri, 19 Mar 2021 05:29:18 GMT):
Has joined the channel.

peter_somogyvari (Mon, 22 Mar 2021 04:42:49 GMT):
Meeting agenda for upcoming maintainers' call: https://wiki.hyperledger.org/display/cactus/2021-03-23+Maintainers+Agenda

HighBrow (Mon, 22 Mar 2021 11:07:20 GMT):
Has joined the channel.

peter_somogyvari (Mon, 22 Mar 2021 16:26:21 GMT):
Just to make doubly sure, here's the calendar entry for the upcoming maintainers' meeting: https://lists.hyperledger.org/g/cactus/viewevent?repeatid=32482&eventid=1070227&calstart=2021-03-23 (posting this again because it looks like when I did the calendar entry edit originally, it didn't move the entry I edited but instead created a copy of it at my intended new date and time so now I deleted the single instance of the original one to avoid confusion)

peter_somogyvari (Tue, 23 Mar 2021 17:23:09 GMT):
FYI All: The CI hot-fix I provided for the docker resource pruning works great, but there appears to be other issues with the CI too so going to hammer away on that today.

peter_somogyvari (Wed, 24 Mar 2021 04:07:22 GMT):
2021-03-23 - Cactus Daily Update ================================ 1. Epic battle with the CI flakes is finally won (it appears to be anyway). Will never be 100% flake free but we are in a sea of green right now vs. 99% red from yesterday so there's cause for celebration. Recommending for everyone whose PRs are in the red as false negatives to rebase onto PR #656 which has a bunch of different fixes for flakes. 2. PR draft for a new roadmap document that contains information that prior to this you'd have to obtain by looking at the GH milestones => https://github.com/hyperledger/cactus/blob/284e9bee6b4e169ef7f09417f57747ca07886ce5/ROADMAP.md 3. PR: updated the documentation specific PRs (both of them) as per the request from Shingo & Takuma to have the development flow showcase and the build script decision tree tucked away instead of being visible on the main readme page. 4. PR to start using the ./tools/ci.sh script within the GH actions (this is thorougher compared to what the GHA currently does for CI) 5. Rebased a dozen or so PRs onto the branch that has the CI fixes baked in (updated PR to show dependencies, etc.)

peter_somogyvari (Thu, 25 Mar 2021 07:42:29 GMT):
2021-03-24 - Cactus Daily Update 1. docs(cmd-api-server): finish writing the readme file #341 #722 2. ci: fix wsl2 lsmem: This system does not support memory blocks #556 3. feat(corda-connector): params factory pattern support #620

peter_somogyvari (Fri, 26 Mar 2021 02:00:57 GMT):
2021-03-25 Daily Updates 1. Finalized fix(general): fixed unused deps and updated them #581 2. Admin chores: shoveling in approved PRs, rebase rebase rebase 3. Finalized feat(corda-connector): dsl support jvm collection types and enums #622

takeutak (Fri, 26 Mar 2021 07:37:37 GMT):
@peter_somogyvari cc: @hartm @JHamilton @E.alcazar @sfuji822 The following pull-request cannot be merged due to the CI check error. https://github.com/hyperledger/cactus/pull/707 The cause of error is not the PR code but Peter's other code. I'm afraid it looks like an error in the CI check function. Could you investigate the cause and take action? Looking at the list of pull-request, I see similar CI check error in most PRs other than this PR. Since the release of V0.4 is near, could you please solve it as soon as possible? I am also going to issue a new PR depending on the PR, and I would like to include it in V 0.4. I will ask for an early solution.

takeutak (Fri, 26 Mar 2021 08:19:40 GMT):
Regarding the problem with the above CI check tool, I succeeded in restarting the CI check without any error. I solved the problem of my PR707 for now.

takeutak (Fri, 26 Mar 2021 08:19:40 GMT):
@peter_somogyvari Regarding the problem with the above CI check tool, I succeeded in restarting the CI check without any error. I solved the problem of my PR707 for now. Thank you.

takeutak (Fri, 26 Mar 2021 08:19:40 GMT):
@peter_somogyvari cc: @hartm @JHamilton @E.alcazar @sfuji822 Regarding the problem with the above CI check tool, I succeeded in restarting the CI check without any error. I solved the problem of my PR707 for now. Thank you.

peter_somogyvari (Sun, 28 Mar 2021 08:40:16 GMT):
2021-03-26 - Cactus Daily Update 1. More PR/rebase shoveling 2. Fixes in PR #620 to make tests play nice with GHA CI 3. Provisioned freestyle dev machine on dev1.infra.cactus.stream

sfuji822 (Mon, 29 Mar 2021 05:02:36 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=SQnKWagNoHiMKGDQw) Is this proposal for future releases? They sound good to me. Can we discuss details at the weekly meeting?

E.alcazar (Mon, 29 Mar 2021 14:53:54 GMT):
It's a way to track updates of what maintainers have been working on during the day across different timezones, we plan to start doing this to sync up on what everyone is doing with a 2 mins read every day. Maybe we'll move this to a different channel, but this way it's open for everyone

peter_somogyvari (Mon, 29 Mar 2021 17:21:34 GMT):
^^ +1 These are just my personal updates of stuff that I've been working on, but everyone is welcome to do the same, it's probably the best kind of conversation starter if someone joins the channel and they look at the logs they'll immediately see what's new and what's being worked on in almost "real time"

ac77ra (Tue, 30 Mar 2021 06:19:23 GMT):
.

peter_somogyvari (Tue, 30 Mar 2021 06:46:15 GMT):
2021-03-29 Cactus Daily Update 1. Rebase approved PRs that are not dependent on other PRs. The filter I use in case anyone else wants to use it: https://github.com/hyperledger/cactus/pulls?q=is%3Aopen+is%3Apr+review%3Aapproved+-label%3Adependent 2. Getting ready to 0.4.0 release (yaaay) 3. Attempt to fix the new security vulnerability report that popped up (upgraded fabric network but it's now failing the CI so will have to further investigate)

rjones (Tue, 30 Mar 2021 14:00:10 GMT):
Has left the channel.

peter_somogyvari (Tue, 30 Mar 2021 15:08:39 GMT):
Hi All, starting to issue the v0.4.0 release now, please refrain from merging new PRs in the meantime.

peter_somogyvari (Wed, 31 Mar 2021 04:08:00 GMT):
2021-03-30 Cactus Daily Update 1. DONE => Issue v0.4.0 release 2. DONE => fix(docs): supply chain example container image exact versions #751 3. DONE => fix(release): package.json publish config non-public #753 5. DONE => fix(connector-fabric): cve-2020-7774 Prototype Pollution high sev. #745 #746 4. STARTED => docs(api-client): finish writing the readme file #342

peter_somogyvari (Thu, 01 Apr 2021 00:26:32 GMT):
2021-03-31 Cactus Daily Update 1. DONE => docs(api-client): finish writing the readme file #342 2. STARTED => docs(examples): add carbon-account-app #540

takeutak (Thu, 01 Apr 2021 08:50:53 GMT):
@peter_somogyvari cc: @hartm @E.alcazar @sfuji822

takeutak (Thu, 01 Apr 2021 08:50:53 GMT):
@peter_somogyvari cc: @hartm @E.alcazar @sfuji822 Thank you for releasing V0.4.0! Thank you for your hard work. Incidentally, the pull-request #581, which was committed just before the release of V0.4.0, caused the examples/car-trade and examples/electricity-trade to malfunction due to incorrect corrections made to packages/package.json which is required for LedgerPlugin. Regarding this correction, I have already posted the pull-request https://github.com/hyperledger/cactus/pull/761 to solve this. Then, I have two favors to ask you. First, would you mind if you approve this PR ? Second, after this pull-request is merged, I would like to tag V0.4.1 as a minor change of V0.4.0. The reason is that examples/car-trade and examples/electricity-trade do not work in the version of V0.4.0 for the above reason, and if this situation continues, new users will not be able to try the sample application. As for the issue of V0.4.1, we plan to request it again after the above PR is approved. We kindly ask for your understanding.

jscode017 (Thu, 01 Apr 2021 13:29:02 GMT):
Has joined the channel.

jscode017 (Thu, 01 Apr 2021 13:34:30 GMT):
Hi, I am new to cactus. I built it from source today. And when I execute '''./tools/ci.sh''' command. And all package-lock.json in all directories change(showed by command git status), did I do something run?

peter_somogyvari (Thu, 01 Apr 2021 14:17:59 GMT):
Hi @jscode017 no that could happen if you are using npm v7 Could you double check what does this command print? ```npm --version```

peter_somogyvari (Thu, 01 Apr 2021 14:18:39 GMT):
@jscode017 Also would want to know if the ./tools/ci.sh script itself otherwise finished successfully or not

jscode017 (Thu, 01 Apr 2021 14:19:00 GMT):
yeah, my version is 7.7.6

jscode017 (Thu, 01 Apr 2021 14:19:26 GMT):
I think the script finished successfully, since I can pass the unit tests

peter_somogyvari (Thu, 01 Apr 2021 14:21:07 GMT):
Okay that's great to hear that the script itself worked. Then at the end of the day the package-lock.json changes don't matter that much, for now you could just safely ignore them and soon we'll add support for npm 7 and this won't be happening

jscode017 (Thu, 01 Apr 2021 14:21:25 GMT):
Thanks a lot

peter_somogyvari (Thu, 01 Apr 2021 14:22:18 GMT):
Anytime! If there's more questions just hit me up, I'm trying to optimize the documentation/scripts so that it's as easy as possible to get started

peter_somogyvari (Thu, 01 Apr 2021 14:22:31 GMT):
So knowing where you get stuck (if you do) is valuable info for me

peter_somogyvari (Thu, 01 Apr 2021 17:10:01 GMT):
@takeutak Works for me, I just accepted 761. Let me know when you are ready and I can create the accompanying 0.4.1 release

takeutak (Fri, 02 Apr 2021 12:12:43 GMT):
@peter_somogyvari Thanks for approval for my PR and releasing v0.4.1! Would you add the tag of v0.4.1 to the commit ID a93e4511ca05dc242697e4bc91618318f9d4e85d ? This commit is already updated by the PR 761

takeutak (Fri, 02 Apr 2021 12:12:43 GMT):
@peter_somogyvari Thanks for approval for my PR and releasing v0.4.1! Would you add the tag of v0.4.1 to the commit ID "a93e4511ca05dc242697e4bc91618318f9d4e85d" ? This commit is already updated by the PR 761.

peter_somogyvari (Fri, 02 Apr 2021 19:17:31 GMT):
@takeutak No worries, yeah sure, I'll just need you to approve this PR that contains the version bump and then I can apply the tag right after that => https://github.com/hyperledger/cactus/pull/765

peter_somogyvari (Sat, 03 Apr 2021 00:09:38 GMT):
2021-04-02 & 2021-04-01 Cactus Daily Update 1. DONE test(connector-besu): fix hardcoded test port #767 #768 2. DONE feat(api-server): ability to install plugins at runtime #764 #769 3. IN_PROGRESS docs(examples): add carbon-account-app #540

peter_somogyvari (Sat, 03 Apr 2021 06:22:43 GMT):
@takeutak v0.4.1 is out => https://github.com/hyperledger/cactus/releases

pritam_01 (Sun, 04 Apr 2021 13:56:30 GMT):
Has joined the channel.

peter_somogyvari (Tue, 06 Apr 2021 03:53:38 GMT):
2021-04-05 Cactus Daily Update 1. IN_PROGRESS => docs(examples): add carbon-account-app #540 2. STARTED => feat(core-api): role based access control through oauth2 scopes #770

suvajit-sarkar (Tue, 06 Apr 2021 04:03:14 GMT):
Has joined the channel.

RafaelAPB (Tue, 06 Apr 2021 19:01:58 GMT):
@takeutak , @sfuji822 , @JHamilton would you like to collaborate on the academic paper we are writing? There is some room for writing up the implementation/plugin architecture sections.

peter_somogyvari (Tue, 06 Apr 2021 19:29:22 GMT):
FYI: https://lists.hyperledger.org/g/cactus/message/269 (There's now an additional pair programming session for the Eastern Hemisphere for those who cannot make it to the current pair programming session due to time zone issues)

RafaelAPB (Wed, 07 Apr 2021 14:05:49 GMT):
Thanks!

RafaelAPB (Wed, 07 Apr 2021 14:06:02 GMT):
Those I cannot attend, as I'm lecturing on those slots

peter_somogyvari (Wed, 07 Apr 2021 20:06:14 GMT):
Is the other one (8 AM Pacific Time) at a good time? If none of them are actually a good time then I shall look into adding some more!

E.alcazar (Thu, 08 Apr 2021 07:04:32 GMT):

Clipboard - April 8, 2021 9:03 AM

E.alcazar (Thu, 08 Apr 2021 07:05:34 GMT):
@takeutak @sfuji822 I have a couple of questions, I'll ping them as a thread to avoid spam

E.alcazar (Thu, 08 Apr 2021 07:13:17 GMT):
1. Is the verifier Factory is acting as the factory pattern to create verifiers without exposing the creation logic, so developers can have a common way to instantiate any verifier? The verifier is instantiated by the developer and the validator has to be instantiated by the network owners so we can deduce that network owners know about their network specifically and therefore they don't need a factory for the validator. Is that assumption correct?

E.alcazar (Thu, 08 Apr 2021 07:15:44 GMT):
2. In step 6 I'm subscribing to an specific event that my application is subscribing? If so, can you point us to the interface of that endpoint? It's critical that we make sure that the interface is common for as many protocols as possible

E.alcazar (Thu, 08 Apr 2021 07:27:23 GMT):
3. Where does the verifier get the keys of the validator? are they provided during the creation process or the connection with the validator? 4. Is there a CA in the key emission process? are they attached to specific DNSs? (Maybe we should worry about this after the initial release) 5. With this process I can receive events I subscribe to and trust they are valid as long as I trust the validator. But there is no way for me to validate that a piece of data resides on the validator's blockchain. Is that assumption right? if so, I think I can create a small PoC showcasing how that would look like in the next meeting :) It will be limited on scope but I'll explain how it can be expanded

RafaelAPB (Thu, 08 Apr 2021 17:48:03 GMT):
Yes!

RafaelAPB (Thu, 08 Apr 2021 17:49:21 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=kry7tweZhiBWG7mbE) I would upvote this. A common interface for validators and connectors is a crucial point in the mid term. Such an interface would also be beneficial for BLPs

RafaelAPB (Thu, 08 Apr 2021 17:50:54 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=9tJfixXNZA5hpbHD7) Could the verifiers be the BLP themselves? Using connectors, they could cross-validate what the validators are outputting. If a validator lives in a private blockchain, I suppose the assumption for the existance of a quorum of validators is a good starting point

peter_somogyvari (Fri, 09 Apr 2021 01:01:12 GMT):
Oh okay, just making sure I'm covering as many zones as possible. :-) Thanks Rafael!

peter_somogyvari (Fri, 09 Apr 2021 06:29:40 GMT):
2021-04-08 Cactus Daily Updates 1. https://github.com/hyperledger/cactus/pull/776 2. https://github.com/hyperledger/cactus/pull/777 3. https://github.com/hyperledger/cactus/pull/779 4. AuthZ MVP: Tests are now passing for OAuth2 and OIDC, need to do code clean up and then ready to go.

kenty (Fri, 09 Apr 2021 15:34:14 GMT):
quick question: what is the minimum spec to run cactus?

kenty (Fri, 09 Apr 2021 16:01:35 GMT):
nice to meet you guys! a little background about myself: https://linkedin.com/in/kentglau

peter_somogyvari (Fri, 09 Apr 2021 16:03:02 GMT):
@kenty The bare minimum for general development (building the code, running the tests, etc) would be around 2 CPU cores (4 threads) and 6 GB RAM free/available. A recommended setup would be for a dev machine in my opinion is 16 GB RAM 4 CPU cores (8 threads) and of course SSD for persistent storage. Anecodte: I've ran the tests on a VPS with 4 GB RAM in it once and the only test that failed was the Corda ones because those are hungrier than the others. Also, if and whne people read this in the future, always inflate the numbers a bit as we continue to add more and more tests every day (test automation is very important to us)

peter_somogyvari (Fri, 09 Apr 2021 16:03:02 GMT):
@kenty The bare minimum for general development (building the code, running the tests, etc) would be around 2 CPU cores (4 threads) and 6 GB RAM free/available. A recommended setup would be for a dev machine in my opinion is 16 GB RAM 4 CPU cores (8 threads) and of course SSD for persistent storage. Anecodte: I've ran the tests on a VPS with 4 GB RAM in it once and the only test that failed was the Corda ones because those are hungrier than the others. Also, if and when people read this in the future, always inflate the numbers a bit as we continue to add more and more tests every day (test automation is very important to us)

peter_somogyvari (Fri, 09 Apr 2021 16:03:28 GMT):
Same here and thank you again for the pointers on the docs!

sfuji822 (Mon, 12 Apr 2021 00:08:24 GMT):
@E.alcazar 1. Yes. This mechanism is following the design pattern "Factory pattern" which can absorb the difference between the implementation of Verifier which can handle the data formats used by connecting DLT. 2. No, it is something different. In step 6, Verifier will realize the communication channel is established with Validator. BLP will subscribe to events from Verifier by issuing the startMonitor() command.

sfuji822 (Mon, 12 Apr 2021 00:21:36 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=9tJfixXNZA5hpbHD7) @E.alcazar 3. We assumed the (public) key is set by the administrator of Cactus Node. 4. I do not think CA is requied. CA will provide the trust on the key based on the trust in the identity of themselves. This trust model is not applicable to us. The administrator(s) can verify the origin of the key based on its own trust policy. Of course, the policy may be used the CA-certified digital certificate, or retrieve the key from the website if it is considered trustworthy. 5. That's a good point. The current implementation of Verifier parses the block data and Verifier breaks the data into a set of transaction data. That means there is no way to verify the validity of the transaction by BLP itself. I interpreted the design of BIF as such. However, if we can improve this for the better, I would like to see your proposal. :-)

sfuji822 (Mon, 12 Apr 2021 00:38:16 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=jWp5WmLshkmvTYTS8) @RafaelAPB @E.alcazar Thank you for your careful consideration of our proposal. Technically integration of BLP and Verifier is possible, but I suggest it will be keep separated from BLP. I assume BLP(s) may be multiple instances (just like web apps), and it may reduce overhead on the duplication task of Verifier if the mechanism can be shared with multiple BLPs as a trustworthy, common event source.

jscode017 (Wed, 14 Apr 2021 12:35:57 GMT):
Hi, may I ask that which npm version to use to prevent package-lock.json to change when building?

peter_somogyvari (Wed, 14 Apr 2021 14:59:12 GMT):
@jscode017 Do you mean the temporary changes that lerna applies (and then reverts) or do you mean a change in your lock file that stays there even after a successful build?

jscode017 (Wed, 14 Apr 2021 21:55:18 GMT):
The one that after successful build.

peter_somogyvari (Thu, 15 Apr 2021 00:05:23 GMT):
Gotcha. The short answer is that the lock files should not just after a build unless mistakes were made (which happen all the time though) If you did change the dependency versions in the package.json files then you just need to revert it back to whatever it was under version control but I'm guessing this is not the case. If you have your fork/branch up on github I can also take a look if none of this helps. Just let me know. In theory you just need to leave the npm versions as is to have the lock files remain stable, unless there was a mistake and someone committed code where they didn't update the lock file in tandem with their dependency changes. I checked the latest main as of right now with a fresh clone + `npm run configure` and the lock files are untouched so what I can suggest is to drop the changes that were made to your lock files, rebase onto the latest main branch state and then do npm run configure and the only lock file changes after that should be the ones that are legit, e.g. they are there because you yourself changed some dependency versions in the package.json.

jscode017 (Thu, 15 Apr 2021 12:49:46 GMT):
Thanks, this helpes. Previously I’ve building with tools/ci.sh, which would somehow change those files at my local repo. But simply npm run configure works quite well and leave those files unchange.

jscode017 (Thu, 15 Apr 2021 12:49:46 GMT):
Thanks, this helps. Previously I’ve building with tools/ci.sh, which would somehow change those files at my local repo. But simply npm run configure works quite well and leave those files unchange.

VipinB (Thu, 15 Apr 2021 14:00:07 GMT):
@peter_somogyvari & @sfuji822 Can we revive this discussion. I will try to be there for the next cactus weekly zoom meeting to present our project on Digital Currency interoperability....

peter_somogyvari (Thu, 15 Apr 2021 14:31:48 GMT):
Awesome, glad i could help! I'll double c heck what's going on with the ci.sh script too because it's not supposed to change the locks either so thank you for the info on that one!

peter_somogyvari (Thu, 15 Apr 2021 14:43:59 GMT):
@VipinB Yes! And sorry for the thread going dead earlier! We have a rotating schedule for the maintainers call now and luckily the upcoming one next week is at a reasonable time for New York! => https://lists.hyperledger.org/g/cactus/viewevent?repeatid=36253&eventid=1109492&calstart=2021-04-19 I added an agenda item for it.

TonyRowntree (Mon, 19 Apr 2021 11:19:43 GMT):
Has joined the channel.

VipinB (Mon, 19 Apr 2021 13:31:42 GMT):
@peter_somogyvari I see the agenda item. Cannot for the life of me find the exact time of this meeting is. Clicking the link just brings me to the generic cactus lists page

VipinB (Mon, 19 Apr 2021 13:33:42 GMT):
@peter_somogyvari - found it

hartm (Mon, 19 Apr 2021 15:26:10 GMT):
Thanks @VipinB !

hartm (Mon, 19 Apr 2021 15:33:17 GMT):
It's totally reasonable to expect people to either expect or comment on a PR within a week.

hartm (Mon, 19 Apr 2021 15:33:32 GMT):
Even a comment--we need to discuss this at a meeting--is fine.

hartm (Mon, 19 Apr 2021 18:19:26 GMT):
Or a "I'm on vacation, leave me alone!"

VipinB (Tue, 20 Apr 2021 10:42:52 GMT):
@peter_somogyvari @sfuji822 I had sent some of the material from DCGI after our conversation. Hopefully it did not go into your spam folder and you have access to it we can continue conversation on mailing list

peter_somogyvari (Tue, 20 Apr 2021 19:33:44 GMT):
@VipinB Thank you again, very helpful document! I sent a question back :-)

peter_somogyvari (Tue, 20 Apr 2021 19:56:28 GMT):
@kenty Sorry I think I forgot to finish what I was going to say this morning: The getting started guide is awesome and I just wanted to suggest a place to put it which could either be a dedicated section of the BUILD.md document or maybe a brand new GETTING_STARTED.md document (not sure which one is better, I'd be happy to support the PR in either one of those files). Also a note to self: If you decide to add it as a new document then we should also hook that up to the readthedocs site so it's easy to find for people. Other note to self: Same goes for the wiki page which should also have a reference to the detailed screencast. P.S.: As usual, let me know if there's anything I can help with!

jscode017 (Wed, 21 Apr 2021 10:13:27 GMT):
Hi, I am currently starting my first pr to the project. (pr812) And I would like to know how to add packages dependencies. I am currently trying to import "@hyperledger@cactus-core" in cactus/packages/cactus-plugin-ledger-connector-corda/src/main/typescript/plugin-ledger-connector-corda.ts / What I've done is adding "@hyperledger@cactus-core" in the dependencies section of package.json, but does not seems to work(and somehow create other issues). Is there anyway to do this?

peter_somogyvari (Wed, 21 Apr 2021 12:54:01 GMT):
@jscode017 Check these out: https://github.com/hyperledger/cactus/blob/main/CONTRIBUTING.md#adding-a-sibling-package-npm-dependency-to-one-of-the-packages https://github.com/hyperledger/cactus/blob/main/CONTRIBUTING.md#adding-a-new-public-npm-dependency-to-one-of-the-packages

jscode017 (Wed, 21 Apr 2021 13:47:16 GMT):
Thanks, so I think `npx lerna add @hyperledger/cactus-core --scope '*/*plugin-ledger-connector-corda' --exact` should do the work?

jscode017 (Wed, 21 Apr 2021 13:47:45 GMT):
BTW, is it normal to get something like `lerna ENOENT: no such file or directory, open '/Users/jasonwang/cactus/examples/cactus-example-supply-chain-backend/node_modules/.bin/cactusapi'`

peter_somogyvari (Wed, 21 Apr 2021 13:48:26 GMT):
Yeah that should do it. It is "normal" in the sense that the addition of the dependency still works IIRC, so you can ignore that error, but obviously not normal in the sense that we should fix that.

peter_somogyvari (Wed, 21 Apr 2021 13:49:19 GMT):
Other pro tip: You might need to restart VSCode to load the type definitions of the package you just added

peter_somogyvari (Wed, 21 Apr 2021 13:49:29 GMT):
I usually do that by hitting F1 and then search for "reload window"

peter_somogyvari (Wed, 21 Apr 2021 14:21:15 GMT):
Also added this little piece of advice to the contributing.md doc just now => https://github.com/hyperledger/cactus/pull/830

jscode017 (Wed, 21 Apr 2021 14:31:29 GMT):
Thanks for the help, really appreciate that.

jscode017 (Wed, 21 Apr 2021 14:32:03 GMT):
BTW, should `./node_modules/.bin/lerna bootstrap` change package-lock.json?

peter_somogyvari (Wed, 21 Apr 2021 14:32:15 GMT):
No worries. If you get any more questions just keep 'em coming, it helps us make the documentation better.

jscode017 (Wed, 21 Apr 2021 14:32:25 GMT):
I think the error I got previously by lerna add

jscode017 (Wed, 21 Apr 2021 14:32:53 GMT):
`lerna ENOENT: no such file or directory, open '/Users/jasonwang/cactus/examples/cactus-example-supply-chain-backend/node_modules/.bin/cactusapi'` this one

peter_somogyvari (Wed, 21 Apr 2021 14:32:57 GMT):
If you changed any of the dependences / dev dependencies in the package.json then the lock file should be updated accordingly as well yes

jscode017 (Wed, 21 Apr 2021 14:33:12 GMT):
Is mainly because every time I run

jscode017 (Wed, 21 Apr 2021 14:33:14 GMT):
./node_modules/.bin/lerna bootstrap

jscode017 (Wed, 21 Apr 2021 14:33:26 GMT):
it would change my package-lock

jscode017 (Wed, 21 Apr 2021 14:33:34 GMT):
So I did not do this previously

peter_somogyvari (Wed, 21 Apr 2021 14:33:47 GMT):
You can make that error go away if you do an `npm run configure`

peter_somogyvari (Wed, 21 Apr 2021 14:34:24 GMT):
I'm yet to figure out where that error is coming from exactly, just haven't had time yet, but it's on the backlog fo rsure

peter_somogyvari (Wed, 21 Apr 2021 14:34:26 GMT):
for sure*

jscode017 (Wed, 21 Apr 2021 14:35:15 GMT):
Yes, thanks a lot. But I think good news is that `lerna ENOENT: no such file or directory, open '/Users/jasonwang/cactus/examples/cactus-example-supply-chain-backend/node_modules/.bin/cactusapi'` is not a issue. It just some error occured by my local side.

VipinB (Wed, 21 Apr 2021 17:52:48 GMT):
@peter_somogyvari I answered via email: The generic top level view is most useful. We can refer to the specifics to illustrate how the framework can be adapted for different interop solutions

peter_somogyvari (Wed, 21 Apr 2021 17:54:46 GMT):
I'm working on the document, will send it over the email thread later today (fingers crossed) :-) Thanks again for the rosetta one, it's very helpful!

VipinB (Wed, 21 Apr 2021 17:55:48 GMT):
Rosetta was just meant as illustration. I can help with final draft of Cactus doc.

hartm (Mon, 26 Apr 2021 17:00:25 GMT):
Looks like we graduated from incubation everyone! Check https://wiki.hyperledger.org/ !

hartm (Mon, 26 Apr 2021 17:00:32 GMT):
(It's a mistake on the wiki).

izuru (Mon, 26 Apr 2021 23:48:39 GMT):
Has joined the channel.

peter_somogyvari (Tue, 27 Apr 2021 00:17:59 GMT):
We keep getting lucky with these things, definitely a good sign. (the other instance of a similar event that comes to mind is when we somehow slipped through the cracks with the quarterly reports :-) )

pranjay (Mon, 03 May 2021 11:39:03 GMT):
Has joined the channel.

peter_somogyvari (Mon, 03 May 2021 20:52:46 GMT):
FYI: https://wiki.hyperledger.org/display/cactus/2021-05-10+Cactus+Maintainers+Agenda+-+Planning+Session

arijit_6 (Wed, 05 May 2021 10:03:09 GMT):
Has joined the channel.

arijit_6 (Wed, 05 May 2021 10:12:50 GMT):
Hi All, I am trying out the Cactus Corda plugin and want to understand how this (https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/jvm-kotlin-spring-server.test.ts#L152) JSON is created for flow invocation. Is there tool is used for this or the JSON is created manually? @peter_somogyvari

peter_somogyvari (Wed, 05 May 2021 13:09:34 GMT):
@arijit_6 That JSON is created manually for now, but of course we have plans to improve on that ;-) Corda 5.x might ship with advanced RPC features that will allow us to make it much simpler.

arijit_6 (Thu, 06 May 2021 05:49:49 GMT):
thanks for the response :)

arijit_6 (Thu, 06 May 2021 05:50:16 GMT):
do we have any guide to create the JSON manually ?

hristiy4n (Thu, 06 May 2021 14:49:09 GMT):
Has joined the channel.

hristiy4n (Thu, 06 May 2021 14:49:11 GMT):
Hi everyone! I am trying to run tools/ci.sh, but the tests are running for over 50 mins now. Referring to a post I found in this chat, my laptop should be within the minimum requirements - 8GB RAM, Dual core CPU (4 threads), OS is Fedora release 33 (Thirty Three). Is this expected as my laptop is slightly above the min. requirements?

peter_somogyvari (Thu, 06 May 2021 14:56:34 GMT):
@hristiy4n Yes, that's expected unfortunately. The CI suite has grown quite a lot due to us adding a lot of tests which is good in itself, but not when you think about the runtime). At that point the ci script should be running the tests already so what you can do if you don't want to wait for it is to just stop it and run `npm run configure` instead which will skip test execution but still perform an initial build that you'll need to get cracking with the code.

RafaelAPB (Thu, 06 May 2021 14:56:46 GMT):
Hey @hristiy4n . I would say that is normal.

peter_somogyvari (Thu, 06 May 2021 14:58:10 GMT):
@arijit_6 No worries, thanks for asking these questions, it helps me prioritize my efforts when it comes to documentation and features. ;-) No guide on writing the JSON just yet unfortunately, but I can whip something up today, I'll keep you in the loop.

hristiy4n (Thu, 06 May 2021 15:42:01 GMT):
Great! Thanks for the swift reply. I will follow the README and see if I can get the API server up and running :)

hristiy4n (Thu, 06 May 2021 15:43:01 GMT):
Alright, I will avoid running the full test suite locally then :)

peter_somogyvari (Thu, 06 May 2021 17:10:59 GMT):
Note to self: We need to update BUILD.md to stop leading with ci.sh because it has grown so big.

arijit_6 (Fri, 07 May 2021 04:51:46 GMT):
That will be great :)

peter_somogyvari (Fri, 07 May 2021 04:53:21 GMT):
Probably will need some more time, but on Friday it should happen.

peter_somogyvari (Fri, 07 May 2021 04:53:36 GMT):
(It's Thursday night here right now)

arijit_6 (Fri, 07 May 2021 05:12:01 GMT):
I am facing one issue with cactus-corda-plugin, getting 404 error when try to call any method apart from `networkMapV1()`. Only network map is giving proper response. cactus version is : "@hyperledger/cactus-plugin-ledger-connector-corda": "^0.4.1" docker image version : petermetz/cactus-connector-corda-server:latest

arijit_6 (Fri, 07 May 2021 05:12:29 GMT):
any help around that will be great

peter_somogyvari (Fri, 07 May 2021 05:12:52 GMT):
Do you have a corda network running that your connector is connected to?

arijit_6 (Fri, 07 May 2021 05:15:10 GMT):
yes it is running and the main-server (Docker process) is connected with it

peter_somogyvari (Fri, 07 May 2021 05:16:12 GMT):
And you are using the api client object to invoke the methods, correct?

arijit_6 (Fri, 07 May 2021 05:17:33 GMT):

Clipboard - May 7, 2021 10:47 AM

arijit_6 (Fri, 07 May 2021 05:17:40 GMT):
this is working

arijit_6 (Fri, 07 May 2021 05:18:24 GMT):

Clipboard - May 7, 2021 10:48 AM

arijit_6 (Fri, 07 May 2021 05:18:36 GMT):
but this is not working..

peter_somogyvari (Fri, 07 May 2021 05:19:57 GMT):
Can you share the entire code maybe in a github repo by any chance?

peter_somogyvari (Fri, 07 May 2021 05:20:14 GMT):
Or the exact repro steps on a terminal

peter_somogyvari (Fri, 07 May 2021 05:20:36 GMT):
It's hard to say why some endpoints would be 404 because we have automated tests for all those endpoints

peter_somogyvari (Fri, 07 May 2021 05:21:09 GMT):
My best guess is that maybe the 0.4.1 version main-server didn't yet have those endpoints, checking that now

peter_somogyvari (Fri, 07 May 2021 05:22:51 GMT):
Nah, v0.4.1 does have the list flows endpoint so I'll really need the steps you took from the beginning

peter_somogyvari (Fri, 07 May 2021 05:23:06 GMT):
(or a repro code)

arijit_6 (Fri, 07 May 2021 05:26:15 GMT):
cant share the entire code base but sharing the steps I performed 1. 3 Node setup of this corda sample - https://github.com/corda/samples-java/tree/master/Advanced/obligation-cordapp 2. started the docker using the below command - sudo docker run -e SPRING_APPLICATION_JSON='{"cactus":{"corda":{"node": {"host": "172.41.50.87"}, "rpc":{"port": 10008, "username":"user1", "password": "password"}}}}' -p=8080:8080 petermetz/cactus-connector-corda-server:latest 3. Then executed this code ```var {DefaultApi} = require("@hyperledger/cactus-plugin-ledger-connector-corda") async function getNodeDetails(){ const apiClient = new DefaultApi({ basePath: 'http://localhost:8080' }); const flowsRes = await apiClient.listFlowsV1(); console.log(flowsRes.status); console.log(flowsRes.data); } getNodeDetails();```

arijit_6 (Fri, 07 May 2021 05:26:33 GMT):
plugin version - "@hyperledger/cactus-plugin-ledger-connector-corda": "^0.4.1"

peter_somogyvari (Fri, 07 May 2021 05:27:51 GMT):
This should be enough for me to repro, let me try

arijit_6 (Fri, 07 May 2021 05:28:14 GMT):
is there any version mismatch between docker image and cactus library ?

peter_somogyvari (Fri, 07 May 2021 05:28:50 GMT):
There might be, but I know for a fact that the list flows endpoint didn't change so that is probably not the issue

arijit_6 (Fri, 07 May 2021 05:31:52 GMT):
Ok, and not only list flows diagnoseNodeV1 and invokeContractV1 is also not working. Getting the same error

arijit_6 (Fri, 07 May 2021 05:31:55 GMT):
If you found some thing please let me know

peter_somogyvari (Fri, 07 May 2021 05:32:53 GMT):
Actually, the docker image might be out of date now that I think about it. Could you try launching this container instead, the tag being: `hyperledger/cactus-connector-corda-server:2021-03-30-b03611f`

peter_somogyvari (Fri, 07 May 2021 05:35:57 GMT):
Yeah, it must be the docker container being old, you were right.

peter_somogyvari (Fri, 07 May 2021 05:36:35 GMT):
So if you try with that image tag , it should work. If it still doesn't ,then potentially this one instead `2021-03-25-feat-622` (because this is the one that the test cases use)

arijit_6 (Fri, 07 May 2021 05:43:33 GMT):
Thank you so much this tag worked `2021-03-30-b03611f`

peter_somogyvari (Fri, 07 May 2021 05:43:53 GMT):
YES! No worries, thanks for giving it a try!

peter_somogyvari (Fri, 07 May 2021 05:44:23 GMT):
Would love to hear what features are you missing if any, could help with proiritization.

arijit_6 (Fri, 07 May 2021 05:45:21 GMT):
sure

arijit_6 (Fri, 07 May 2021 05:45:51 GMT):
if could provide some help around that JSON that will be great..

peter_somogyvari (Fri, 07 May 2021 05:46:26 GMT):
Ahh yes, that JSON is a monster for sure... alright, I'll definitely get it done on Friday (my tomorrow)

peter_somogyvari (Fri, 07 May 2021 05:46:53 GMT):
The short story of it is that you need to specify the exact JVM fully qualified class names (e.g. with packages)

peter_somogyvari (Fri, 07 May 2021 05:47:44 GMT):
But I'll come up with a better way to explain it

peter_somogyvari (Fri, 07 May 2021 05:48:09 GMT):
And also a better way to handle that whole thing because Ideally you could just pass in a "normal" JSON that everybody's used to in Javascript

peter_somogyvari (Fri, 07 May 2021 05:48:29 GMT):
(much harder to do than say because Java has strict requirements for types)

arijit_6 (Fri, 07 May 2021 05:57:31 GMT):
yes I understand the challenge with Java, it will be great if we able to simplify the RPC invocation process..

arijit_6 (Fri, 07 May 2021 07:34:30 GMT):
A suggestion I have, currently we can invoke those cordapps flows which are deployed through the cactus connector (main-server) but cant invoke a cordapps which is already deployed or running on the network. We can have a option to upload the jar existing cordapp on cactus connector and which will be stored in the spring boot app class path as the cordapp class are required for deserialization. I think in that way we can invoke the existing cordaap also without deployment.

peter_somogyvari (Fri, 07 May 2021 18:38:44 GMT):
Hi all, A merge freeze is in effect until the 0.5.0-alpha.0 goes through: https://github.com/hyperledger/cactus/pull/927 See a detailed explanation about the why and how here: https://github.com/hyperledger/cactus/issues/451 Important note to reviewers: Keep chugging along with those reviews. A merge freeze doesn't mean that PRs cannot be reviewed, just that they won't be merged until after the freeze is over. TLDR `Do NOT seize/put on hold any of your review activities on account of the merge freeze.`

peter_somogyvari (Fri, 07 May 2021 18:44:39 GMT):
@arijit_6 I think you might be able to achieve that outcome of only uploading the jars to the spring boot connector app by passing an empty array for the `cordappDeploymentConfigs` property of the deployment request. That way the connector will accept and put the jars on it's own class path and just call it a day without trying to shell into the node (because the array is empty). Note to self: This should explicitly be documented in some shape or form because it's not obvious unless you have read the code of the connector itself (which is obviously not very user friendly as a requirement :-) )

peter_somogyvari (Sat, 08 May 2021 00:14:43 GMT):
@arijit_6 I got started with the examples here: https://github.com/hyperledger/cactus/pull/944 This only covers the simple cases for now but the more advanced ones will be there next week too.

peter_somogyvari (Sat, 08 May 2021 00:15:16 GMT):
And I had the idea that maybe we could ease the pain of it by creating our own VSCode extension, but that's sort of a moonshot idea I'm just floating around for now to see what people think.

siv2r (Sun, 09 May 2021 17:44:32 GMT):
Has joined the channel.

arijit_6 (Mon, 10 May 2021 05:09:45 GMT):
@peter_somogyvari thank you so much for all the details. Now it will be easier to use the corda-connector. :)

hartm (Mon, 10 May 2021 15:22:44 GMT):
Here is a good definition of threshold signatures (section 6.1): https://eprint.iacr.org/2017/251.pdf

hartm (Mon, 10 May 2021 15:22:50 GMT):
We wouldn't want to use that scheme, though.

hartm (Mon, 10 May 2021 15:23:17 GMT):
Here is a variant of the threshold scheme that most people implement: https://www.cc.gatech.edu/~aboldyre/papers/bold.pdf

kikoncuo (Tue, 11 May 2021 13:16:58 GMT):
Has joined the channel.

kikoncuo (Tue, 11 May 2021 13:20:11 GMT):
@sfuji822 @peter_somogyvari Hello, I'm Enrique for some reason I had to create another account, trying to organize the meeting to review where we are going to be pulling validator related data from and the new HTLC design without smart contracts as outlined by @sfuji822

kikoncuo (Tue, 11 May 2021 13:20:34 GMT):
@peter_somogyvari has proposed this time: https://www.timeanddate.com/worldclock/converter.html?iso=20210512T060000&p1=224&p2=141&p3=136&p4=tz_jst Thrusday

tkuhrt (Tue, 11 May 2021 17:31:28 GMT):
Not sure if you received this question via the Confluence page: https://wiki.hyperledger.org/display/TSC/Move+the+Blockchain+Integration+Framework+%28BIF%29+lab+to+a+Project?focusedCommentId=51611192#comment-51611192

tkuhrt (Tue, 11 May 2021 18:02:29 GMT):
@Haissam is the person asking the question regarding integrating Fabric and Quorum. Pulling him into the channel to ask specifics about what he is trying to accomplish.

Haissam (Tue, 11 May 2021 18:02:29 GMT):
Has joined the channel.

RafaelAPB (Tue, 11 May 2021 18:26:14 GMT):
Hey @Haissam. Perhaps a good way to get started is for you to run the example at the README: https://github.com/hyperledger/cactus

Haissam (Tue, 11 May 2021 18:40:07 GMT):
@RafaelAPB Hi Rafael Base on the documentation https://wiki.hyperledger.org/display/cactus saying "Cactus is a pluggable enterprise-grade framework to transact on multiple distributed ledgers without introducing yet another competing blockchain." and "To address blockchain fragmentation; Allow developers to connect and perform transactions across different blockchain networks."

Haissam (Tue, 11 May 2021 18:46:16 GMT):
@peter_somogyvari Hi Peter Base on the documentation https://wiki.hyperledger.org/display/cactus saying "Cactus is a pluggable enterprise-grade framework to transact on multiple distributed ledgers without introducing yet another competing blockchain." and "To address blockchain fragmentation; Allow developers to connect and perform transactions across different blockchain networks."

Haissam (Tue, 11 May 2021 18:51:11 GMT):
@peter_somogyvari Because I need to integrate Quorum with different blockchain framework like Hypeledger fabric or Quorum to Quorum by plugin Cactus

cmhacker (Wed, 12 May 2021 06:56:42 GMT):
Has joined the channel.

dbdagr8 (Wed, 12 May 2021 11:16:37 GMT):
Has joined the channel.

dbdagr8 (Wed, 12 May 2021 11:16:38 GMT):
Hi All , I am trying besu/Quorum plugins and facing issues while deploying contract. - In Quorum, contract without constructor args is working fine, but no option available to pass constructor args. - In Besu, I passed constructor args, contract ABI. What to pass in keychain ID? It is throwing error without keychain ID and contract Name. I passed random string, but it is finding keychain ID in preconfigured map. What if I do not want to use predefined map? How to deploy without keychain?

VijayMichalik (Wed, 12 May 2021 11:26:15 GMT):
Has joined the channel.

peter_somogyvari (Wed, 12 May 2021 18:46:04 GMT):
@dbdagr8 Right now the keychain is mandatory unfortunately, but improvements for this (to make it fully optional) are scheduled to be released. https://github.com/hyperledger/cactus/issues/963 Constructor arguments for contracts: Same thing, I just opened an issue for it as well so please track this one: https://github.com/hyperledger/cactus/issues/962 and maybe put a thumbs up on it to signal that you'd like this to be prioritized ;-)

peter_somogyvari (Wed, 12 May 2021 20:36:11 GMT):
Thank you very much Tracy!

peter_somogyvari (Wed, 12 May 2021 20:42:37 GMT):
@sfuji822 @kikoncuo Yupp, that time works for me. Here's the updated link with the date being set to Thursday (my time - Friday in your times) https://www.timeanddate.com/worldclock/converter.html?iso=20210514T060000&p1=224&p2=141&p3=136&p4=tz_jst

dbdagr8 (Thu, 13 May 2021 05:39:00 GMT):
Sure @peter_somogyvari

dbdagr8 (Thu, 13 May 2021 05:39:00 GMT):
Sure @peter_somogyvari. Thanks

jscode017 (Fri, 14 May 2021 10:58:51 GMT):
Hi, does anyone has experience of dealing with `Starting of dummy infrastructure crashed: Error: BesuTestLedger#waitForHealthCheck() timed out (120000ms) -> Error: read ECONNRESET` when running the supply-chain example? Previously, I run the supply-chain example using docker, I thought it was due to the docker pull cactus-fabric-all-in-one takes too long. So I switch to run the application locally and use `docker pull hyperledger/cactus-fabric-all-in-one:2021-03-02-ssh-hotfix` ahead of npm run start But still getting this error Any helps would be hugely appreciated

jscode017 (Fri, 14 May 2021 12:01:59 GMT):
sorry, my bad. get it working by changing my docker desktop settings

charith1994 (Sat, 15 May 2021 17:03:39 GMT):
Has joined the channel.

peter_somogyvari (Sat, 15 May 2021 23:45:15 GMT):
@jscode017 Would you mind sharing what setting you had to change? We could add an entry to the FAQ.md file explaining how to fix it

jscode017 (Sun, 16 May 2021 14:47:09 GMT):
Yeah, of course. But it was more like a stupid error on my side. I change the setting to only allocate 2 cpus to my docker desktop about last week and forget to change it back when running the example. Though it do get me a while to get to that issue since the `starting dummy infrastructure `seems like do not need much resource.

peter_somogyvari (Mon, 17 May 2021 18:32:57 GMT):
Thanks for sharing, I still think this is a great addition to our FAQ because if it happened to you, it could also happen to others (whatever reason you had to change your docker CPU count could also happen to others, etc) Thanks again, I'll open a PR to add this to the FAQ.md

peter_somogyvari (Mon, 17 May 2021 18:33:39 GMT):
One more question actually: What number of CPUs did you set up to get it working? Was it 4 or 6 maybe?

jscode017 (Tue, 18 May 2021 01:04:21 GMT):
I set up 4 cpu with 16gb memory to get it working

siv2r (Tue, 18 May 2021 01:13:43 GMT):
Hey, I am new to the cactus community. I am working on a PoC for the Iroha ledger connector plugin for the HL Cactus + HL Iroha integration project. In the documentation of Ledger Plugin API (https://github.com/hyperledger/cactus/blob/main/whitepaper/whitepaper.md#532-ledger-plugin-api), I see Verifier functions like `getSmartContractList()`, `getBalance()` etc. I do not find implementation for these functions in the fabric ledger connector plugin (https://github.com/hyperledger/cactus/tree/main/packages/cactus-plugin-ledger-connector-fabric). Shouldn't these functions be implemented for every ledger connector plugin? If not, then How does a ledger connector plugin get this information from the ledger?

siv2r (Tue, 18 May 2021 01:25:15 GMT):
Also, Is there a dummy ledger connector plugin implementation or a template that I can refer to?

siv2r (Tue, 18 May 2021 01:26:43 GMT):
Also, Is there a dummy ledger connector plugin implementation or a template that I can refer to?

peter_somogyvari (Tue, 18 May 2021 04:00:29 GMT):
Hi @siv2r That discrepancy is there in the API surface as a temporary thing that we are trying to work out as we speak. If you want a super bare-bones example then here is one for that: https://github.com/hyperledger/cactus/tree/main/packages/cactus-cmd-api-server/src/test/typescript/fixtures/plugin-ledger-connector-stub BUT what I recommend is to just literally copy and paste one of the existing ledger plugin packages instead and then rename the package in it, gut the code down to the minimum, etc. Lastly: I think the mentorship candidate selection process hasn't concluded yet so you might want to hold off with that work until that's done otherwise the work might become duplicated.

siv2r (Tue, 18 May 2021 13:27:38 GMT):
@peter_somogyvari Thanks for the information. I wanted to submi this PoC as part of the mentorship selection process since, I got an email regarding the extra work (deadline 19 May).

siv2r (Tue, 18 May 2021 13:27:38 GMT):
@peter_somogyvari Thanks for the information. I wanted to submit this PoC as part of the mentorship selection process since, I got an email regarding the extra work (deadline 19 May).

siv2r (Tue, 18 May 2021 14:24:33 GMT):
I don't think I can finish the PoC by 19th :sweat_smile:. I will submit one of my other projects for the extra task assigned and work on this on the side till the 21st since it is the last date for selecting the candidates. I will stop working on this if I didn't get selected, and this work might help the chosen candidate :)

jscode017 (Wed, 26 May 2021 12:13:47 GMT):
Sorry, I am not sure if this is the right place to ask. But I am currently trying to implement connector plugin for burrow(issue292), but stuck for days for the docker setup. Could I make a [do not merge] pull request?

jscode017 (Wed, 26 May 2021 12:13:47 GMT):
Sorry, I am not sure if this is the right place to ask. But I am currently trying to implement connector plugin for burrow(issue292), and stuck for days for the docker setup. Could I make a [do not merge] pull request?

peter_somogyvari (Wed, 26 May 2021 14:37:47 GMT):
@jscode017 Yeah, just make sure to mark it as 'draft' (there's a button for this when you are opening the PR). Let me know if you need more help

Ben10ers (Thu, 27 May 2021 19:12:39 GMT):
Has joined the channel.

RafaelAPB (Tue, 01 Jun 2021 22:57:48 GMT):
@peter_somogyvari regarding the update to npm v7: do you also recommend updating to node 16.1 (LTS)?

peter_somogyvari (Tue, 01 Jun 2021 23:00:21 GMT):
Depends on your appetite for being on the bleeding edge. :-) Only updating npm v7 is the safer choice for now and in the coming weeks we'll gain more confidence in also upgrading node itself, but for now I'd recommend doing just npm v7. There's a pending PR that will add Node v16 to the test suite matrix meaning that we'll know a lot more about potential v16 specific bugs in the coming weeks, but right now, not so much.

RafaelAPB (Tue, 01 Jun 2021 23:03:00 GMT):
Thanks - I'll keep hanging with v14. For now :)

peter_somogyvari (Thu, 03 Jun 2021 17:18:35 GMT):
@RafaelAPB I've been on Node 16 for the last few days and we also now have the CI matrix testing against it, so at this point I can give the update that as far as I know right now it is safe to switch over to Node 16. (still not necessary, but it looks good so far). If a few weeks pass from now and we still haven't found any issues that we couldn't solve then I'll start recommending that everyone switch to Node 16 if they can. (for now I'm just making the declaration that it appears to be ready, but not recommending just yet)

TanvirHossain (Sat, 05 Jun 2021 18:20:05 GMT):
Has joined the channel.

TanvirHossain (Sat, 05 Jun 2021 18:20:06 GMT):
Hi there. i am new in this hyperledger cactus framework. i really need some guidance on something. I want to connect 2 separate fabric ledger , where one user from one system can access data from another fabric system, is there any way to do this by cactus or any other way? if yes , please guide me, or i can knock any helping hand personally, i badly need some resource on this. my teacher is pressuring me,(sorry to express on this)

Ben10ers (Sun, 06 Jun 2021 21:59:11 GMT):
Hey. Been trying to learn a bit about cactus and was trying to run the cartrade example for Cactus. And it seems to get stuck on the second transaction with "TransactionFabric - error at Invoke: err=Error: 14 UNAVAILABLE: failed to connect to all addresses" Is this a known problem or am I doing something wrong?

takeutak (Mon, 07 Jun 2021 03:56:52 GMT):
@Ben10ers Thanks for using the cartrade example! In order to resolve your error, could you tell me about the following items? (1) When you execute the command "docker ps" on the console after the command of "script-start-ledgers.sh", what containers are launched on your environment? If any of the following containers does not be launched, that may be the cause of the error.

takeutak (Mon, 07 Jun 2021 03:56:52 GMT):
@Ben10ers Thanks for using the cartrade example! In order to resolve your error, could you tell me about the following items? When you execute the command "docker ps" on the console after the command of "script-start-ledgers.sh", what containers are launched on your environment? If any of the following containers does not be launched, that may be the cause of the error. dev-peer0.org1.example.com-fabcar-1.0 - cli - peer0.org1.example.com - couchdb - ca.example.com - orderer.example.com - geth1

takeutak (Mon, 07 Jun 2021 03:56:52 GMT):
@Ben10ers Thanks for using the cartrade example! In order to resolve your error, could you tell me about the following items? When you execute the command "docker ps" on the console after the command of "script-start-ledgers.sh", what containers are launched on your environment? If any of the following containers does not be launched, that may be the cause of the error. - dev-peer0.org1.example.com-fabcar-1.0 - cli - peer0.org1.example.com - couchdb - ca.example.com - orderer.example.com - geth1

takeutak (Mon, 07 Jun 2021 03:56:52 GMT):
@Ben10ers Thanks for using the cartrade example! In order to resolve your error, could you tell me about the following question? When you execute the command "docker ps" on the console after the command of "script-start-ledgers.sh", what containers are launched on your environment? If any of the following containers does not be launched, that may be the cause of the error. - dev-peer0.org1.example.com-fabcar-1.0 - cli - peer0.org1.example.com - couchdb - ca.example.com - orderer.example.com - geth1 As the README of "boot method" describes, in the normal case the above seven containers launches. According to your error message "UNAVAILABLE: failed to connect to all addresses", I think that some fabric peers were not safely launched.

takeutak (Mon, 07 Jun 2021 04:03:03 GMT):
@Ben10ers Thanks for using the cartrade example! In order to resolve your error, could you tell me about the following question? When you execute the command "docker ps" on the console after the command of "script-start-ledgers.sh", what containers are launched on your environment? If any of the following containers does not be launched, that may be the cause of the error. - dev-peer0.org1.example.com-fabcar-1.0 - cli - peer0.org1.example.com - couchdb - ca.example.com - orderer.example.com - geth1 As the README of "boot method" describes, in the normal case the above seven containers launches. According to your error message "UNAVAILABLE: failed to connect to all addresses", I think that some fabric peers were not safely launched in your case. If that is right, I may be able to supply some alternative method.

RafaelAPB (Mon, 07 Jun 2021 10:36:55 GMT):
Hello @TanvirHossain . Could you be more specific on what do you need?

Ben10ers (Mon, 07 Jun 2021 11:02:45 GMT):

Clipboard - June 7, 2021 12:02 PM

Ben10ers (Mon, 07 Jun 2021 11:02:47 GMT):
Yeh I'm missing some of those. Just tested and the ones that launched are these.

Ben10ers (Mon, 07 Jun 2021 11:02:47 GMT):
Yeh I'm missing some of those. Just tested and the ones that launched are these. Sorry for late answer :)

dbdagr8 (Mon, 07 Jun 2021 13:41:42 GMT):
Hi, I am using cactus hyperledger fabric plugin to deploy, invoke and query chaincode. On deploy I am not able to understand the sshConfig part and what to specify in that. I want to deploy locally using APIs. Invoke and query are working fine but on deploy I am getting following error: ``` AssertionError [ERR_ASSERTION]: config must be a valid object at NodeSSH.connect (node_modules/node-ssh/lib/cjs/index.js:123:25) at PluginLedgerConnectorFabric.deployContract (node_modules/@hyperledger/cactus-plugin-ledger-connector-fabric/dist/lib/main/typescript/plugin-ledger-connector-fabric.js:98:19) ``` Why sshConfig is always required? I initialized PluginLedgerConnectorFabric as below: ``` let connector = new PluginLedgerConnectorFabric({ connectionProfile: connectionProfileJson, discoveryOptions: { asLocalhost: true, enabled: true }, instanceId: instanceIdConnector, pluginRegistry: pluginRegistry, eventHandlerOptions: { strategy: DefaultEventHandlerStrategy }, }); ``` What I am missing? Please help!!

RafaelAPB (Mon, 07 Jun 2021 15:47:30 GMT):
Hey, welcome to the community. sshConfig is needed because operations like deploying chaincode rely on establishing an ssh connection between the test ledger container and the peer containers. Which test are you running?

dbdagr8 (Tue, 08 Jun 2021 05:17:58 GMT):
I am not running any test, instead I am using cactus to expose APIs to deploy, invoke,query etc for my fabric network.

dbdagr8 (Tue, 08 Jun 2021 05:17:58 GMT):
I am not running any test, instead I am using cactus to expose APIs to deploy, invoke,query etc for my fabric network. What to specify in sshConfig for local running fabric containers?

takeutak (Tue, 08 Jun 2021 07:23:10 GMT):
@peter_somogyvari Regarding the CI check tool. According to the current configuration, every time a Pull request is merged into the main branch, the CI check must be redone. Considering that it takes more than an hour to complete a CI check, I think that I cannot cope with a situation where the code needs frequent changes. However, it is not large enough that all code has to be CI checked every time (For example, there is no need to do CI check on the document pull-request, right?). Since CI check is mandatory for all pull-requests, this inconvenience will occur. I would like to be able to choose to avoid CI checks when merging pull-requests. Is it possible to change the specification?

takeutak (Tue, 08 Jun 2021 07:25:27 GMT):
@peter_somogyvari Regarding the CI check tool. According to the current configuration, every time a Pull request is merged into the main branch, the CI check must be redone. Considering that it takes more than an hour to complete a CI check, I think that I cannot cope with a situation where the code needs frequent changes. However, it is not large enough that all code has to be CI checked every time (For example, there is no need to do CI check on the document pull-request, right?). Since CI check is mandatory for all pull-requst, this inconvenience will occur. I would like to be able to choose to avoid CI checks when merging pull-requests. Is it possible to change the specification?

takeutak (Tue, 08 Jun 2021 07:25:27 GMT):
@peter_somogyvari Regarding the CI check tool. According to the current configuration, every time a Pull request is merged into the main branch, the CI check must be redone. Considering that it takes more than an hour to complete a CI check, I think that I cannot cope with a situation where the code needs frequent changes. However, it is not large enough that all code has to be CI checked every time (For example, there is no need to do CI check on pull-requests including only document files, right?). Since CI check is mandatory for all pull-requst, this inconvenience will occur. I would like to be able to choose to avoid CI checks when merging pull-requests. Is it possible to change the specification?

takeutak (Tue, 08 Jun 2021 07:25:27 GMT):
@peter_somogyvari Regarding the CI check tool. According to the current configuration, every time a Pull request is merged into the main branch, the CI check must be redone. Considering that it takes more than an hour to complete a CI check, I think that I cannot cope with a situation where the code needs frequent changes. However, it is not large enough that all code has to be CI checked every time (For example, there is no need to do CI check on pull-requests including only document files, right?). Since CI check is mandatory for all pull-requst, this inconvenience will occur. I would like to be able to choose to avoid CI checks when merging pull-requests. Is it possible to change the specification? (c.f.) Issue #1014: https://github.com/hyperledger/cactus/issues/1014

takeutak (Tue, 08 Jun 2021 07:52:22 GMT):
@Ben10ers Thanks for your replying. I think that your error was caused by the error when you executed the command of script-start-ledgers.sh. (1) What is OS and version of node.js in your machine environment? Especially, at the present time we recommend node.js-v12 when we use car-trade. (The latest version of node.js will be available in near future.) (2) Could you share the log when you execute the command of script-start-ledger.sh as txt file? I think that the log includes clues to resolve your problem. I'm sorry for the inconvenience, but we would like to solve this problem soon. We would appreciate your cooperation.

takeutak (Tue, 08 Jun 2021 07:52:22 GMT):
@Ben10ers Thanks for your replying. I think that your error was caused by the error when you executed the command of script-start-ledgers.sh. I'd like to ask you about the following two questions in order to find out the method to fix your error. (1) What is OS and version of node.js in your machine environment? Especially, at the present time we recommend node.js-v12 when we use car-trade. (The latest version of node.js will be available in near future.) (2) Could you share the log when you execute the command of script-start-ledger.sh as txt file? I think that the log includes clues to resolve your problem. I'm sorry for the inconvenience, but we would like to solve this problem soon. We would appreciate your cooperation.

takeutak (Tue, 08 Jun 2021 07:52:22 GMT):
@Ben10ers Thanks for your replying. I think that your error was caused by the error when you executed the command of script-start-ledgers.sh. I'd like to ask you about the following two questions in order to find out a method to fix your error. (1) What is OS and version of node.js in your machine environment? Especially, at the present time we recommend node.js-v12 when we use car-trade. (The latest version of node.js will be available in near future.) (2) Could you share the log when you execute the command of script-start-ledger.sh as txt file? I think that the log includes clues to resolve your problem. I'm sorry for the inconvenience, but we would like to solve this problem soon. We would appreciate your cooperation.

Ben10ers (Tue, 08 Jun 2021 09:38:19 GMT):
Will give you all this info once I'm home again, and reply here.

Ben10ers (Tue, 08 Jun 2021 12:15:38 GMT):
Hey (also answered in dm but) node version is v14.13.1 and i didn't entirely understand your second question, do you want me to save the output of running the script onto a txt file?

RafaelAPB (Tue, 08 Jun 2021 12:26:01 GMT):
Which package are you looking into? The supply chain example?

pritam_01 (Tue, 08 Jun 2021 15:16:15 GMT):
Hello Guys!! I am trying to start supply chain application without docker Steps I Followed 1. `npm run configure` - from root 2. `npm run start:example-supply-chain` - from root Error that I got

pritam_01 (Tue, 08 Jun 2021 15:16:38 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=kia2fny4MSrd6qYyD)
Screenshot from 2021-06-08 20-35-03.png

peter_somogyvari (Wed, 09 Jun 2021 05:55:39 GMT):
@takeutak Agreed that this needs improvement. See my answers on GH!

peter_somogyvari (Wed, 09 Jun 2021 05:59:28 GMT):
@pritam_01 , yeah, sorry about that, you can fix up the configuration like I did on my branch (just haven't had time to finish the work on it yet) Branch: https://github.com/petermetz/cactus/tree/docs-examples-fix-container-build Commit: https://github.com/petermetz/cactus/commit/101ae907c61fcf8bc77ce60a670a89166dbd7d89 Env vars to fix that particular issue : AUTHORIZATION_PROTOCOL=NONE AUTHORIZATION_CONFIG_JSON="{}"

pritam_01 (Wed, 09 Jun 2021 06:29:30 GMT):
Thank you @peter_somogyvari.

pritam_01 (Wed, 09 Jun 2021 06:29:30 GMT):
Thank you @peter_somogyvari

Ben10ers (Wed, 09 Jun 2021 09:13:53 GMT):
Also sent you the Log in DM @takeutak

barankilic (Wed, 09 Jun 2021 18:33:43 GMT):
Has joined the channel.

dbdagr8 (Thu, 10 Jun 2021 05:54:27 GMT):
I installed this one in my own fabric project: ``` https://www.npmjs.com/package/@hyperledger/cactus-plugin-ledger-connector-fabric ```

klenik (Thu, 10 Jun 2021 12:26:34 GMT):
Has joined the channel.

klenik (Thu, 10 Jun 2021 12:26:35 GMT):
Hi everyone! I started playing around with the Cactus `cartrade` example (on commit `a93e451`). As a first step, I planned to switch from the provided `fabric-samples` Fabric network to my custom Fabric network (different org/node names, TLS, no CAs), but the chaincode is the same `fabcar`. I have newly generated `crypto-config` and corresponding `wallet` directories for the my network members. I'll continue with the details in the thread ->

klenik (Thu, 10 Jun 2021 12:27:05 GMT):
So I tried to locate every file (config or JS/TS) that contains Fabric connection information, and I found these: 1. `examples/cartrade/config/default.json ` 2. `examples/cartrade/validatorDriver/queryCar.js` 3. `examples/cartrade/validatorDriver/config/default.js` 4. `examples/cartrade/validatorDriver/src/config/default.ts` 5. `packages/ledger-plugin/fabric/validator/src/dependent/PluginConfig.ts` 6. `packages/ledger-plugin/fabric/validator/src/dependent/connection.json`

klenik (Thu, 10 Jun 2021 12:28:32 GMT):
However, I'm facing some issues with the configuration. For example, in file 1, how can I provide cert information for the nodes, as required by TLS?

klenik (Thu, 10 Jun 2021 12:29:47 GMT):
Also in file 1, it seems like the CA component is not optional. Why does the app needs a CA? Every identity is already generated and present. Is the CA mandatory?

klenik (Thu, 10 Jun 2021 12:34:25 GMT):
I'd really not like to downgrade to a network without TLS (and with solo orderer), so any pointer is appreciated!

klenik (Fri, 11 Jun 2021 07:27:15 GMT):
@peter_somogyvari Do you have any insights into the cartrade app's TLS support?

RafaelAPB (Fri, 11 Jun 2021 13:33:41 GMT):
Ok - what you need to provide for the sshConfig is defined on the typings ->index.d.ts of the node-ssh package. More practically, you can check examples on the connectors' test files

peter_somogyvari (Fri, 11 Jun 2021 17:32:52 GMT):
@klenik I'm mostly familiar with the supply chain and the carbon accounting examples of ours. Car trade is best known by Takuma. @takeutak Could you please check this out?

piyushmaheshwari99 (Sun, 13 Jun 2021 12:22:16 GMT):
Has joined the channel.

CatarinaPedreira (Mon, 14 Jun 2021 13:07:35 GMT):
Has joined the channel.

CatarinaPedreira (Mon, 14 Jun 2021 13:07:36 GMT):
Hello, everyone :) Cactus beginner here. I'm working on building a connector for Polkadot in Hyperledger Cactus and currently trying to implement the "deployContract" function for Polkadot, for the deployment of a smart contract. Based on the other connectors, both the request and response of this function (and other parameters, such as Web3SigningCredential types) are first generated on an open api json file, specific to each connector. Do I also need to build the open api for the Polkadot connector for this function's implementation, or can I build it after the implementation? Also, is the open api file required for the generation of the SDK? Thank you in advance!

takeutak (Tue, 15 Jun 2021 13:42:02 GMT):
@klenik Very sorry to reply late. Thank you very much for your question. You would like to replace the Fabric network provided by car-trade with a custom Fabric network. Would you mind if you wait my answer for a little, as I am planning to answer after we verify it among the development members? I will reply this week.

klenik (Tue, 15 Jun 2021 13:44:40 GMT):
Sure, thanks for the effort :) As I saw in the code, when the fabric node objects are created, the required tls artifacts are not loaded, although there were attempts, which are now commented out

peter_somogyvari (Tue, 15 Jun 2021 21:44:01 GMT):
Hi Catarina, welcome welcome welcome! :-) 1. You can start without defining the OpenAPI specs if you prefer. If you do this your test case will have to directly call the connector instance instead of going through the API client (which is okay to start) 2. Yes, the generation of the SDK is 100% based on the openapi.json file

peter_somogyvari (Tue, 15 Jun 2021 21:44:01 GMT):
Hi @CatarinaPedreira , welcome welcome welcome! :-) 1. You can start without defining the OpenAPI specs if you prefer. If you do this your test case will have to directly call the connector instance instead of going through the API client (which is okay to start) 2. Yes, the generation of the SDK is 100% based on the openapi.json file 3. If any more questions, feel free to send them here or join at one of our pair programming calls that run daily as well.

takeutak (Wed, 16 Jun 2021 00:46:19 GMT):
FYI to other members: I am currently discussing this matter with @Ben10ers through I am currently verifying the error situation from the other party, and I am planning to reply today.

takeutak (Wed, 16 Jun 2021 00:46:19 GMT):
FYI to other members: I am already discussing this matter with @Ben10ers through I am currently verifying the error situation from the other party, and I am planning to reply today.

takeutak (Wed, 16 Jun 2021 00:46:19 GMT):
FYI to other members: I am already discussing this matter with @Ben10ers through DM. I am currently verifying the error situation from him, and I am planning to reply today.

takeutak (Wed, 16 Jun 2021 00:46:19 GMT):
[FYI to other members] I am already discussing this matter with @Ben10ers through DM. I am currently verifying the error situation from her/him, and I am planning to reply today. @Ben10ers Sorry to wait for my answer but I will answer soon.

Ben10ers (Wed, 16 Jun 2021 09:18:53 GMT):
Its all good!

klenik (Wed, 16 Jun 2021 10:45:29 GMT):
@takeutak The cartrade example issues raw transactions toward the Ethereum verifier . In this line (https://github.com/hyperledger/cactus/blob/main/examples/cartrade/BusinessLogicCartrade.ts#L140), the `contract` object is left empty. What should it contain, if we wanted to transfer tokens instead of wei (i.e., we have a deployed contract on the Ethereum node)? Any help is appreciated :)

dbdagr8 (Mon, 21 Jun 2021 12:16:32 GMT):
Hi, I have 2 questions regarding corda connector: 1. This corda sample `https://github.com/corda/samples-kotlin/tree/master/Basic/flow-database-access` and other examples where invoke flow doesn't change state throwing some Signing Transaction error. How to fix that? 2. I need to know in corda connector, can we pass jar path instead of passing base64 jars if jars are present on same system locally and docker can mount jarpath directly?

hartm (Mon, 21 Jun 2021 15:01:59 GMT):
Can someone post the meeting link in chat? The wiki appears to be down.

takeutak (Wed, 23 Jun 2021 03:29:31 GMT):
Sorry to late replying. Your question is how to call the functions of Ethereum smart contract from Go-Ethereum Validator. Now we are developing the functions of Go-Ethereum Validator to call smart contract on car-trade. So, I will contact you after this update. I'm sorry for keeping you waiting, but I will try this update soon.

takeutak (Wed, 23 Jun 2021 03:33:47 GMT):
Sorry to late replying. I'm still verifying the customization of car-trade fabric nodes on car-trade and will notify you when it is complete. Would you mind if you wait my answer for a little?

albusaidi (Wed, 23 Jun 2021 07:08:21 GMT):
Has joined the channel.

albusaidi (Wed, 23 Jun 2021 07:08:23 GMT):
Hello there , i want to know how we can install hypeledger cactus in virtual machine (Ubuntu) or in windows 10 ??

takeutak (Wed, 23 Jun 2021 13:20:27 GMT):
I created the issue reflecting your update request as the following. https://github.com/hyperledger/cactus/issues/1082 If some update will be reflected on Cactus GitHub code, some notification will appear on the above Issue. Could you subscribe it?

takeutak (Wed, 23 Jun 2021 13:20:27 GMT):
@klenik I created the issue reflecting your update request as the following. https://github.com/hyperledger/cactus/issues/1082 If some update will be reflected on Cactus GitHub code, some notification will appear on the above Issue. Could you subscribe it?

takeutak (Wed, 23 Jun 2021 13:22:43 GMT):
@klenik Considering your update request, I created the issue about docker environment for using custom ledgers. https://github.com/hyperledger/cactus/issues/1083 If some update will be reflected on Cactus GitHub code, some notification will appear on the above this issue. Could you mind if you subscribe it?

takeutak (Wed, 23 Jun 2021 13:54:42 GMT):
@albusaidi Thank you for contact us! To test the behavior of Hyperledger Cactus, it would be faster to actually use the sample business-logic applications. You can try the following three applications with an Ubuntu virtual machine: (1) car-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/cartrade Cactus car-trade is a sample application where users can exchange car ownership (represented by Fabcar chaincode tokens on a Hyperledger Fabric blockchain) for ETH currency on a private Ethereum blockchain. (2) electricity-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/electricity-trade Cactus electricity-trade is a sample application for exchanging electricity (which is measured by a device that is logging to a Sawtooth blockchain) for ETH currency on a private Ethereum blockchain. When the measuring device detects power usage, a Sawtooth transaction triggers a Cactus LedgerEvent to pay the device user's currency on the Ethereum blockchain, where the amount paid is proportional to the amount of power usage recorded on the Sawtooth blockchain. In this example, we use the Sawtooth intkey transaction processor as an application for power measurement logging. (3) supply-chain-app: https://github.com/hyperledger/cactus#run-the-examples Cactus supply-chain-app is a sample application for supply-chain traceability using Fabric, Quorum, and Besu ledgers. Their usages are described in the READMEs of the above URLs. If these sample apps cannot work well, please ask me via e-mail or RocketChat ? If your question is related with car-trade or electricity-trade, I can help you. Otherwise, if your question is related with supply-chain-app, I will ask another Cactus maintainer to help you. BR, Takuma

takeutak (Wed, 23 Jun 2021 13:54:42 GMT):
@albusaidi Thank you for contact us! To test the behavior of Hyperledger Cactus, it would be faster to actually use the sample business-logic applications. You can try the following three applications with an Ubuntu virtual machine: (1) car-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/cartrade Cactus car-trade is a sample application where users can exchange car ownership (represented by Fabcar chaincode tokens on a Hyperledger Fabric blockchain) for ETH currency on a private Ethereum blockchain. (2) electricity-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/electricity-trade Cactus electricity-trade is a sample application for exchanging electricity (which is measured by a device that is logging to a Sawtooth blockchain) for ETH currency on a private Ethereum blockchain. When the measuring device detects power usage, a Sawtooth transaction triggers a Cactus LedgerEvent to pay the device user's currency on the Ethereum blockchain, where the amount paid is proportional to the amount of power usage recorded on the Sawtooth blockchain. In this example, we use the Sawtooth intkey transaction processor as an application for power measurement logging. (3) supply-chain-app: https://github.com/hyperledger/cactus#run-the-examples Cactus supply-chain-app is a sample application for supply-chain traceability using Fabric, Quorum, and Besu ledgers. Their usages are described in the READMEs of the above URLs. If these sample apps cannot work well, please ask us via RocketChat ? If your question is related with car-trade or electricity-trade, I can help you. Otherwise, if your question is related with supply-chain-app, I will ask another Cactus maintainer to help you. BR, Takuma

takeutak (Wed, 23 Jun 2021 13:54:42 GMT):
@albusaidi Thank you for contact us! To test the behavior of Hyperledger Cactus, it would be faster to actually use the sample business-logic applications. You can try the following three applications with an Ubuntu virtual machine: (1) car-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/cartrade Cactus car-trade is a sample application where users can exchange car ownership (represented by Fabcar chaincode tokens on a Hyperledger Fabric blockchain) for ETH currency on a private Ethereum blockchain. (2) electricity-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/electricity-trade Cactus electricity-trade is a sample application for exchanging electricity (which is measured by a device that is logging to a Sawtooth blockchain) for ETH currency on a private Ethereum blockchain. When the measuring device detects power usage, a Sawtooth transaction triggers a Cactus LedgerEvent to pay the device user's currency on the Ethereum blockchain, where the amount paid is proportional to the amount of power usage recorded on the Sawtooth blockchain. In this example, we use the Sawtooth intkey transaction processor as an application for power measurement logging. (3) supply-chain-app: https://github.com/hyperledger/cactus#run-the-examples Cactus supply-chain-app is a sample application for supply-chain traceability using Fabric, Quorum, and Besu ledgers. Their usages are described in the READMEs of the above URLs. If these sample apps cannot work well, please ask us via this RocketChat ? If your question is related with car-trade or electricity-trade, I can help you. Otherwise, if your question is related with supply-chain-app, I will ask another Cactus maintainer to help you. cc: @peter_somogyvari

takeutak (Wed, 23 Jun 2021 13:54:42 GMT):
@albusaidi Thank you for contact us! To test the behavior of Hyperledger Cactus, it would be faster to actually use the sample business-logic applications. You can try the following three applications with an Ubuntu virtual machine: (1) car-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/cartrade Cactus car-trade is a sample application where users can exchange car ownership (represented by Fabcar chaincode tokens on a Hyperledger Fabric blockchain) for ETH currency on a private Ethereum blockchain. (2) electricity-trade: https://github.com/hyperledger/cactus/tree/v0.4.1/examples/electricity-trade Cactus electricity-trade is a sample application for exchanging electricity (which is measured by a device that is logging to a Sawtooth blockchain) for ETH currency on a private Ethereum blockchain. When the measuring device detects power usage, a Sawtooth transaction triggers a Cactus LedgerEvent to pay the device user's currency on the Ethereum blockchain, where the amount paid is proportional to the amount of power usage recorded on the Sawtooth blockchain. In this example, we use the Sawtooth intkey transaction processor as an application for power measurement logging. (3) supply-chain-app: https://github.com/hyperledger/cactus#run-the-examples Cactus supply-chain-app is a sample application to ensure supply-chain traceability via three ledgers of Fabric, Quorum, and Besu. Their usages are described in the READMEs of the above URLs. If these sample apps cannot work well, please ask us via this RocketChat ? If your question is related with car-trade or electricity-trade, I can help you. Otherwise, if your question is related with supply-chain-app, I will ask another Cactus maintainer to help you. cc: @peter_somogyvari

albusaidi (Wed, 23 Jun 2021 14:00:18 GMT):
Great thanks a lot

albusaidi (Wed, 23 Jun 2021 14:02:53 GMT):
what about the hyperledger Cactus architecture ? Actually i did not find full explanation about its architecture. Since I am beginner in this field I need to understand all things in details

takeutak (Wed, 23 Jun 2021 14:06:48 GMT):
Thanks for your question about Cactus architecture. The system architecture diagram of Cactus is described on the diagram on the following whitepaper section 5.2. - https://github.com/hyperledger/cactus/blob/main/whitepaper/whitepaper.md#52-system-architecture-and-basic-flow

hartm (Thu, 24 Jun 2021 15:37:39 GMT):
It looks like no one is showing up to the "Hemisphere" meetings. Can we take them off the calendar so new people don't show up? Thanks!

gccgpl (Thu, 24 Jun 2021 22:56:33 GMT):

Clipboard - June 24, 2021 5:56 PM

gccgpl (Thu, 24 Jun 2021 22:57:59 GMT):
Has joined the channel.

gccgpl (Thu, 24 Jun 2021 22:57:59 GMT):
Hi, I am working on Cactus's iroha plugin. I have a question for the compiling error. I understand that TS's current configuration file probably will report error if any parameter is unused.

gccgpl (Thu, 24 Jun 2021 22:59:36 GMT):
The above error appears when I was doing "npm run configure"

gccgpl (Thu, 24 Jun 2021 22:59:36 GMT):
The above error appears when I was doing "npm run configure" for the fork repo that I am working on.

gccgpl (Thu, 24 Jun 2021 23:00:36 GMT):
However, if I try to compile the original repo. For "besu-test-ledger.ts" or some other files, similar issue exists. (the 'header' is declared but its value is never read) But it compiles successfully.

gccgpl (Thu, 24 Jun 2021 23:01:15 GMT):

Clipboard - June 24, 2021 6:01 PM

gccgpl (Thu, 24 Jun 2021 23:14:28 GMT):
I understand that changing 'header' to '_header' will fix this temporarily, but I did not know why it popped up. (maybe I broke something?)

gccgpl (Thu, 24 Jun 2021 23:14:28 GMT):
I understand that (changing the parameter 'header' to '_header') or ( change "noUnusedParameters" to false inside the tsconfig.json file) will fix this temporarily, but I did not know why it popped up. (maybe I broke something?)

klenik (Mon, 28 Jun 2021 09:31:26 GMT):
@takeutak Thank you, I started following the issue :)

klenik (Mon, 28 Jun 2021 09:35:02 GMT):
@takeutak The main issue is that I'd like to use TLS, but the cartrade example doesn't allow the specification of TLS certs. So it's mainly a demo issue, the Fabric validator allows for the same, since it's using the common connection profile of the Fabric SDK.

klenik (Mon, 28 Jun 2021 09:38:27 GMT):
So while the above issue is valid, I think the core issue is that the configuration file of the cartrade demo is not flexible enough. Relying on the Fabric SDK connection profile (embedded in the cartrade config file, or as a reference to an external connection config) would be more straightforward, and would circumvent potential feature gaps

peter_somogyvari (Mon, 28 Jun 2021 16:42:51 GMT):
@gccgpl Can you show the output of `git status` ?

pritam_01 (Thu, 01 Jul 2021 16:11:15 GMT):
how often cactus npm packages are re-published ? can we have a minor bug fix release of xdai connector ?

peter_somogyvari (Sat, 03 Jul 2021 02:50:12 GMT):
@pritam_01 Usually bi-weekly, I'll issue a new release today, will ping you when it's done.

hartm (Tue, 13 Jul 2021 01:27:52 GMT):
Hi everyone, I've created a preliminary quarterly report

hartm (Tue, 13 Jul 2021 01:27:55 GMT):
https://wiki.hyperledger.org/display/TSC/2021+Q3+Hyperledger+Cactus

hartm (Tue, 13 Jul 2021 01:28:02 GMT):
Please feel free to add to it as you see fit. Thanks!

RafaelAPB (Wed, 14 Jul 2021 18:13:12 GMT):
Report looks good to me. Don't know if its relevant, but we have three hyperledger summer internships dedicated to Cactus: https://wiki.hyperledger.org/display/INTERN/2021+Projects We have two incoming contributors from my University, in the next quarter though (blockchain migration tool & Polkadot connector)

RafaelAPB (Thu, 22 Jul 2021 16:59:24 GMT):
Hello #cactus . I've missed the Connector Standardization talk by mistake - is there a recording/notes? Can someone please provide a summary? Thanks in advance :)

hartm (Thu, 22 Jul 2021 17:00:04 GMT):
We are still talking.

hartm (Thu, 22 Jul 2021 17:00:17 GMT):
Join Zoom Meeting https://accenture.zoom.us/j/9526643832?pwd=ODEzdWd1ZUErN0NaeGxLV0V2Wi91dz09 Meeting ID: 952 664 3832 Passcode: ek5JiB One tap mobile +16699006833,,9526643832#,,,,*655543# US (San Jose) +12532158782,,9526643832#,,,,*655543# US (Tacoma) Dial by your location +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 952 664 3832 Passcode: 655543 Find your local number: https://accenture.zoom.us/u/adLheS1HNr

RafaelAPB (Fri, 23 Jul 2021 09:01:35 GMT):
Unfortunately I've posted the message and exited the chat :( Haven't seen it. I'll catch up later in the PP meeting

knagware9 (Fri, 23 Jul 2021 16:29:49 GMT):

Survey on Blockchain Interoperability.pdf

izuru (Thu, 05 Aug 2021 08:02:52 GMT):
I've uploaded meeting notes of 2021-08-02. I failed to write down attendees in that session. Any attendee who isn't on the list inform me

RafaelAPB (Fri, 06 Aug 2021 08:18:07 GMT):
@peter_somogyvari, regarding ODAP, BUNGEE, CC-TX-Viz, and packages that use connectors: is it fine if they receive API clients instead of a plugin registry? I understnad that if you have a plugin registry you can access plugins IF 1) you have an api server, and 2) if they are running on your api server (?); But that might not be the case; our plugin might benefit from obtaining data from a connector running somewhere outside our node. Is passing API clients a good option?

peter_somogyvari (Fri, 06 Aug 2021 14:48:44 GMT):
@RafaelAPB I'd say yes to the API clients with the caveat that instead of passing the API clients I'd be passing the options of said API clients so that it's JSON serializable. Second thing: The plugin registry and the API client within your plugin implementation are not mutually exclusive, they both can be there and used at the same time if you like.

peter_somogyvari (Fri, 06 Aug 2021 14:55:33 GMT):
Someone by the name of Himanshu Vastish is trying to join the daily pair programming call, but it's not working, so this is a message for them: I just wanted to let you know that you should try joining from a Chrome browser, Firefox doesn't always work unfortunately.

luisabrunhosa (Tue, 10 Aug 2021 20:37:10 GMT):
Has joined the channel.

luisabrunhosa (Tue, 10 Aug 2021 20:37:10 GMT):
hello everyone :slight_smile: I'm a Cactus beginner and I'm implementing a smart contract migrator between heterogeneous blockchains, and I have a question regarding Cactus. Is it possible to deploy a Typescript smart contract in fabric using Cactus? Also I would like to know if it is possible to use Cactus feature to instance a test ledger to test the fabric test files, according to the example given in deploy-cc-from-typescript-source.test.ts file in cacus-plugin-ledger-connector-fabric directory and if you could explain me how do I configure to do that? Thank you very much for your help in advance! :slight_smile:

RafaelAPB (Tue, 10 Aug 2021 21:05:58 GMT):
Thanks, @peter_somogyvari !

peter_somogyvari (Tue, 10 Aug 2021 21:09:10 GMT):
@luisabrunhosa Yeah please take a look at this one for an example: https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-ledger-connector-fabric/src/test/typescript/integration/fabric-v2-2-x/deploy-cc-from-typescript-source.test.ts > if you could explain me how do I configure to do that? Sorry, not sure what you mean, all the configuration necessary is in the test case including the pulling up of the ledger. Or do you mean something additional?

peter_somogyvari (Tue, 10 Aug 2021 21:09:54 GMT):
And before I forget, welcome to the OSS community ;-)

luisabrunhosa (Tue, 10 Aug 2021 21:20:37 GMT):
[ ](https://chat.hyperledger.org/channel/cactus?msg=6JuyneRx4METDEd72) Thank you very much! I have seen that file to try to understand how the test files work using Cactus, but my question is, having a test file similar to the deploy-cc-from-typescript-source.test.ts how can I run that file? Only need to execute node run name_of_the_file.ts? Thank you very much again!

peter_somogyvari (Tue, 10 Aug 2021 21:36:45 GMT):
@luisabrunhosa Gotcha, now I see what you mean! You can run it via the test runner tap as shown in these examples in the documentation: https://hyperledger-cactus.readthedocs.io/en/latest/contributing.html#running-a-single-test-case You can also do it via `yarn ts-node $YOUR_TEST_CASRE_FILE_RELATIVE_PATH`

luisabrunhosa (Tue, 10 Aug 2021 21:37:45 GMT):
@peter_somogyvari Thank you very much!!

pritam_01 (Fri, 13 Aug 2021 08:47:24 GMT):
Hello !! I have create a issue of type enhancement. the issue is about proposal for fabric-secure-connector https://github.com/hyperledger/cactus/issues/1212 Please have a look and do comment :relaxed: Thank you

iulia.mihaiu (Mon, 16 Aug 2021 10:48:39 GMT):
Has joined the channel.

iulia.mihaiu (Mon, 16 Aug 2021 10:48:40 GMT):
Hi all! I'm new to the Cactus community. I'm currently working on the Visualization and Analysis of Cross-chain Transaction Hyperledger project. I'm making a user study and we need to build some understanding on what the Hyperledger community needs in terms of visualizing cross-chain transactions. It would be really helpful if you have some time to fill out this brief survey(https://forms.gle/V4WQU2PhLSHdXjS2A ). Thank you:)

luisabrunhosa (Sat, 21 Aug 2021 18:07:56 GMT):
Hello everyone!

luisabrunhosa (Sat, 21 Aug 2021 18:18:08 GMT):
Hello everyone!! I'm studying the cactus-plugin-ledger-connector-fabric and cactus-plugin-ledger-connector-besu in order to integrate them with my tool. However, I have some questions regarding the besu connector. How can I compile my local smart contract to a .json file to use in the test? Also, how can I integrate both connectors in my tool, is there any tutorial or any steps available so I could follow? Thank you very much for your help in advance!! :slight_smile:

trevoro1 (Sun, 22 Aug 2021 04:10:46 GMT):
Has joined the channel.

trevoro1 (Sun, 22 Aug 2021 04:11:00 GMT):
Is Cactus in a PoC mode?

peter_somogyvari (Mon, 23 Aug 2021 18:17:52 GMT):
@trevoro1 In a way yes,. It is an incubation status project in Hyperledger meaning that it is not ready for production just yet, BUT we are intending to get to that point indeed.

peter_somogyvari (Mon, 23 Aug 2021 18:19:57 GMT):
@luisabrunhosa I personally use the solidity extension of VSCode and sometimes also an npm package called HardHat if I need the compilation to be scripted/non-manual. If you clone the project sources VSCode should automatically show a pop-up offering to install the recommended Extensions and the solidity extension mentioned above is one of them so you should accept that pop-up and then you are good to go meaning that after that you can right click on any solidity file in VSCode and have an option to compile it which will place the JSON artifact(s) in the ./bin/ directory of the project root afterwards.

luisabrunhosa (Mon, 23 Aug 2021 18:21:47 GMT):
Perfect!! @peter_somogyvari thank you very much!!

peter_somogyvari (Mon, 23 Aug 2021 18:22:43 GMT):
@luisabrunhosa No worries, glad to help! :-) For future reference: If you need more help we have daily pair programming calls where you can join and ask questions with screen sharing as well. => https://wiki.hyperledger.org/display/cactus/Hyperledger+Cactus+Home

SatyamGupta1 (Thu, 26 Aug 2021 13:57:00 GMT):
Has joined the channel.

CatarinaPedreira (Thu, 26 Aug 2021 16:01:48 GMT):
Hi all! :) I'm building a cactus connector to Polkadot. Polkadot's consensus type does not correspond to any of the ones listed in ConsensusAlgorithmFamily class (from @hyperledger/cactus-core), so I tried to add it to the class manually, by changing the openApi of the cactus-core-api. I only added the lines with a new enum member Substrate both in "ConsensusAlgorithmFamily" and "ConsensusAlgorithmFamiliesWithTxFinality" in the OpenAPI. However, after running npm run config again, for some reason the open API changed the generated names of the other enum members (Authority -> ProofOfAuthority, Stake -> ProofOfStake and Work -> ProofOfWork), which caused errors on other connectors when trying to access the enum members. Any idea why this is happening? Does it have to do with OpenAPI rules I'm missing? Thanks in advance!

CatarinaPedreira (Thu, 26 Aug 2021 16:03:02 GMT):
Changes in openApi (in ConsensusAlgorithmFamily and ConsensusAlgorithmFamiliesWithTxFinality):

CatarinaPedreira (Thu, 26 Aug 2021 16:03:29 GMT):

Clipboard - August 26, 2021 5:03 PM

CatarinaPedreira (Thu, 26 Aug 2021 16:04:36 GMT):
Generated enums prior to my changes:

CatarinaPedreira (Thu, 26 Aug 2021 16:04:38 GMT):

Clipboard - August 26, 2021 5:04 PM

CatarinaPedreira (Thu, 26 Aug 2021 16:04:49 GMT):
Generated enums post changes:

CatarinaPedreira (Thu, 26 Aug 2021 16:05:14 GMT):

Clipboard - August 26, 2021 5:05 PM

CatarinaPedreira (Thu, 26 Aug 2021 16:05:23 GMT):
Thanks in advance :)

peter_somogyvari (Thu, 26 Aug 2021 16:06:58 GMT):
@CatarinaPedreira It might have something to do with the openapi generator version that you are using. Can you confirm that your branch is based on the latest upstream/main branch? Also, can you send a link here to your Cactus fork and invite me as a collaborator? (GH username of mine is: `petermetz`)

CatarinaPedreira (Thu, 26 Aug 2021 16:09:52 GMT):
Thanks! Actually, I haven't updated my fork in a little while, so that might just be it. Will update it and see if it works, thank you :)

CatarinaPedreira (Thu, 26 Aug 2021 16:09:55 GMT):
Of course, this is the link:

CatarinaPedreira (Thu, 26 Aug 2021 16:11:03 GMT):
https://github.com/CatarinaPedreira/cactus/tree/derbi

CatarinaPedreira (Thu, 26 Aug 2021 16:11:25 GMT):
I'm working on the derbi branch

CatarinaPedreira (Thu, 26 Aug 2021 16:12:02 GMT):
Already sent the invite :) Thank you for your help

peter_somogyvari (Thu, 26 Aug 2021 16:12:50 GMT):
@CatarinaPedreira No worries and my pleasure! :-)

pritam_01 (Thu, 26 Aug 2021 18:01:54 GMT):
Reopened this PR to be reviewed https://github.com/hyperledger/cactus/pull/1243 feat(connector-fabric): add support for vault transit secret engine @peter_somogyvari

CatarinaPedreira (Sun, 29 Aug 2021 11:33:13 GMT):
Hello all, Yesterday I rebased my fork to update it with changes from the upstream. I noticed there was a yarn.lock file, and that package-lock.json was not there. Now when I run npm install, I get some weird warnings and it always ends in an error (invalid version). Do I have to run an additional command? Or it was something wrong with my rebase?

CatarinaPedreira (Sun, 29 Aug 2021 11:33:33 GMT):

warnings.png

CatarinaPedreira (Sun, 29 Aug 2021 11:33:36 GMT):

error.png

VikiAnand (Mon, 30 Aug 2021 08:21:30 GMT):
Has joined the channel.

VikiAnand (Mon, 30 Aug 2021 08:21:31 GMT):
Hello all , What should be the applicationHostInfo.hostName in the default.json file on ubuntu machine inside virtualbox for CARTRADE example implementation ?

pritam_01 (Mon, 30 Aug 2021 17:42:25 GMT):
A read about how vault can be used as platform Enterprise Blockchain . https://www.hashicorp.com/resources/vault-platform-enterprise-blockchain Can provide inspiration for securely keeping client's private key used for interacting with multiple ledgers , supported by cactus

pritam_01 (Mon, 30 Aug 2021 17:42:25 GMT):
A read about how vault can be used as platform for Enterprise Blockchain . https://www.hashicorp.com/resources/vault-platform-enterprise-blockchain Can provide inspiration for securely keeping client's private key used for interacting with multiple ledgers , supported by cactus

peter_somogyvari (Mon, 30 Aug 2021 21:08:57 GMT):
@CatarinaPedreira Yup, we've migrated to yarn meaning that there are no more package-lock.json files in every package (instead now we only have the yarn.lock file in the root for all packages). What you can do is `npm run install-yarn` and then just say `yarn install` and finally any package-lock.json files that are still present on your branch need to be simply deleted. If you have conflicts with yarn.lock you can resolve those in any direction and then just run `yarn install` again which will update the file to match whatever dependencies you have declared in the package.json file which are the true source of truth. Finally, you can say `yarn configure` to run the configure script and build the project (previously this was called via "npm run configure")

peter_somogyvari (Mon, 30 Aug 2021 21:11:14 GMT):
@VikiAnand I'm only guessing here: For local development it's "localhost" or maybe "0.0.0.0" could work. Tagging @takeutak because he's the authoritative source to answer the question not me. Takuma, please do chime in :-)

peter_somogyvari (Mon, 30 Aug 2021 21:13:35 GMT):
@pritam_01 Thanks for the link, I shall read that!

VikiAnand (Tue, 31 Aug 2021 04:49:10 GMT):
Let me check if that works @peter_somogyvari @peter_somogyvari :)

VikiAnand (Tue, 31 Aug 2021 12:22:57 GMT):
Hi All,

VikiAnand (Tue, 31 Aug 2021 12:25:03 GMT):
While implementing car trade example , when i am running the * /script-start-ledger.sh* script , it throws following error .: Failed to enroll admin user "admin": Error: Cannot find module 'fabric-client/lib/impl/CryptoSuite_ECDSA_AES.js' Require stack: - /home/vikas/Documents/cactus/tools/docker/fabric14-fabcar-testnet/fabric-samples/fabcar/javascript/node_modules/fabric-ca-client/lib/utils.js - /home/vikas/Documents/cactus/tools/docker/fabric14-fabcar-testnet/fabric-samples/fabcar/javascript/node_modules/fabric-ca-client/lib/FabricCAServices.js - /home/vikas/Documents/cactus/tools/docker/fabric14-fabcar-testnet/fabric-samples/fabcar/javascript/node_modules/fabric-ca-client/index.js - /home/vikas/Documents/cactus/tools/docker/fabric14-fabcar-testnet/fabric-samples/fabcar/javascript/enrollAdmin.js Wallet path: /home/vikas/Documents/cactus/tools/docker/fabric14-fabcar-testnet/fabric-samples/fabcar/javascript/wallet An identity for the user "user1" already exists in the wallet

VikiAnand (Tue, 31 Aug 2021 12:25:44 GMT):
I tried updating npm

VikiAnand (Tue, 31 Aug 2021 12:26:05 GMT):
but still it has ound 23 vulnerabilities (6 low, 3 moderate, 7 high, 7 critical)

peter_somogyvari (Tue, 31 Aug 2021 16:09:04 GMT):
@VikiAnand Please ping @takeutak for help

VikiAnand (Tue, 31 Aug 2021 16:09:48 GMT):
Sure Thanks :)

VikiAnand (Wed, 01 Sep 2021 04:07:04 GMT):
Hi @takeutak Could you please help me here?

VikiAnand (Wed, 01 Sep 2021 04:07:23 GMT):
seems like some issue with npm

VikiAnand (Wed, 01 Sep 2021 05:52:30 GMT):
Error: Cannot find module 'fabric-client/lib/impl/CryptoSuite_ECDSA_AES.js'

hartm (Thu, 02 Sep 2021 20:01:36 GMT):
Should we cancel next week's meeting due to the US holiday?

VikiAnand (Fri, 03 Sep 2021 02:53:04 GMT):
Hi Wallet path: /home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/wallet 2021-09-02T17:26:13.803Z - error: [Channel.js]: Error: 2 UNKNOWN: identity expired 2021-09-02T17:26:13.806Z - error: [Network]: _initializeInternalChannel: Unable to initialize channel. Attempted to contact 1 Peers. Last error was Error: 2 UNKNOWN: identity expired

VikiAnand (Fri, 03 Sep 2021 02:54:08 GMT):
I am facing this issue while implementing cartrade example

peter_somogyvari (Fri, 03 Sep 2021 17:15:37 GMT):
@hartm I won't be there either, so probably best to cancel it as usual. Unless @takeutak or @sfuji822 would like to keep it.

peter_somogyvari (Fri, 03 Sep 2021 17:16:11 GMT):
cc: @takeutak @sfuji822

VikiAnand (Mon, 06 Sep 2021 08:30:45 GMT):
Hi @takeutak @sfuji822 Could you please help me here ?

VikiAnand (Tue, 07 Sep 2021 05:55:57 GMT):
Hi @takeutak @sfuji822 Please look into the error log I am facing while implementing cartrade example:

VikiAnand (Tue, 07 Sep 2021 05:56:00 GMT):
./script-get-app.sh [process] Execute an app for getting Balance on Ethereum The balance of fromAccount: BigNumber { s: 1, e: 5, c: [ 100000 ] } The balance of toAccount: BigNumber { s: 1, e: 0, c: [ 0 ] } [process] Execute an app for getting ownership on Fabcar Wallet path: /home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/wallet 2021-09-07T05:52:18.625Z - error: [Channel.js]: Error: 2 UNKNOWN: identity expired 2021-09-07T05:52:18.631Z - error: [Network]: _initializeInternalChannel: Unable to initialize channel. Attempted to contact 1 Peers. Last error was Error: 2 UNKNOWN: identity expired at Object.exports.createStatusError (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/common.js:91:15) at Object.onReceiveStatus (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:1209:28) at InterceptingListener._callNext (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:568:42) at InterceptingListener.onReceiveStatus (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:618:8) at callback (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:847:24) { code: 2, metadata: [Metadata], details: 'identity expired' } Failed to evaluate transaction: Error: Unable to initialize channel. Attempted to contact 1 Peers. Last error was Error: 2 UNKNOWN: identity expired at Object.exports.createStatusError (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/common.js:91:15) at Object.onReceiveStatus (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:1209:28) at InterceptingListener._callNext (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:568:42) at InterceptingListener.onReceiveStatus (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:618:8) at callback (/home/vikas/Documents/cactus/examples/cartrade/script-test-getFunctions/fabric/node_modules/grpc/src/client_interceptors.js:847:24) { code: 2, metadata: [Metadata], details: 'identity expired' }

takeutak (Wed, 08 Sep 2021 14:01:24 GMT):
@VikiAnand Thank you for your comments. This problem is reproduced in some of our machines. We already found that the cause is that fabric-samples/fabcar-1.4.1 does not work in some environments at present. I will update the version of fabcar which is used in Cactus-cartrade soon. We are currently in the middle of a major refactoring of some code on another matter, so we would like to resolve this problem later. I will report it on the issue below when it is finished, so could you wait a moment? https://github.com/hyperledger/cactus/issues/1311

takeutak (Wed, 08 Sep 2021 14:01:24 GMT):
@VikiAnand Thank you for your comments and I'm sorry to reply late. This problem is reproduced in some of our machines. We already found that the cause is that fabric-samples/fabcar-1.4.1 does not work in some environments at present. I will update the version of fabcar which is used in Cactus-cartrade soon. We are currently in the middle of a major refactoring of some code on another matter, so we would like to resolve this problem later. I will report it on the issue below when it is finished, so could you wait a moment? https://github.com/hyperledger/cactus/issues/1311

VikiAnand (Wed, 08 Sep 2021 14:22:50 GMT):
Yeah Thanks @takeutak

baziorek (Thu, 09 Sep 2021 08:37:31 GMT):
Hi, Is single Cactus instance enough to connect multiple networks (3 or more), or for each connection another instance should be? And another question - about performance - what is performance of "atomic swap" between two networks?

peter_somogyvari (Thu, 09 Sep 2021 15:16:36 GMT):
@baziorek Hi Greg, you can load any number of connector plugins into a single API server instance and to connect to all those ledger through the connectors. Performance: Unclear, we haven't had time to do the benchmarks yet unfortunately.

robinrob (Thu, 09 Sep 2021 21:39:06 GMT):
Has joined the channel.

baziorek (Fri, 10 Sep 2021 06:39:58 GMT):
Hi Peter, Thanks for Your answer.

JHamilton (Mon, 13 Sep 2021 13:10:53 GMT):
team my apologies, I won't be able to make the maintainers meeting today due to a conflict. @peter_somogyvari @takeutak @sfuji822

VikiAnand (Tue, 14 Sep 2021 04:42:56 GMT):
Hi Can we use cactus as a connector for fabric and ethereum networks in a production ready environment ?

peter_somogyvari (Tue, 14 Sep 2021 19:18:36 GMT):
@VikiAnand Not recommended to use in production until we hit 1.0. Hopefully that's happening this fall.

igorkrupczynski (Thu, 16 Sep 2021 10:06:40 GMT):
Has joined the channel.

Andre_Augusto (Wed, 22 Sep 2021 16:29:48 GMT):
Has joined the channel.

saki.osive (Thu, 23 Sep 2021 04:20:19 GMT):
Has joined the channel.

spandolfi (Fri, 24 Sep 2021 14:33:12 GMT):
Has joined the channel.

spandolfi (Fri, 24 Sep 2021 14:37:36 GMT):
Hi everyone, a pleasure to be here! I need to interoperate besu with fabric and I am having troubles with the cartrade example. I wish to know if it is working in mac also or only in linux. Thank you very much.

spandolfi (Fri, 24 Sep 2021 14:43:35 GMT):
@VikiAnand it seems that you had a lot of trouble with the cartrade example You finally got it working?

CatarinaPedreira (Fri, 24 Sep 2021 15:08:25 GMT):
Hey everyone. I have the following bug when running the substrate ledger environment test: packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> [2021-09-24T14:54:39.301Z] ERROR (containers#tryPullImage()): Could not even start ghcr.io/rafaelapb/cactus-substrate-aio:2021-08-26-first pull: Error: (HTTP code 500) server error - Head https://ghcr.io/v2/rafaelapb/cactus-substrate-aio/manifests/2021-08-26-first: denied packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> at /home/catarina/Documentos/Cactus-current/cactus/node_modules/docker-modem/lib/modem.js:301:17 packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> at IncomingMessage. (/home/catarina/Documentos/Cactus-current/cactus/node_modules/docker-modem/lib/modem.js:328:9) packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> at IncomingMessage.emit (events.js:327:22) packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> at IncomingMessage.EventEmitter.emit (domain.js:467:12) packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> at endReadableNT (internal/streams/readable.js:1327:12) packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> at processTicksAndRejections (internal/process/task_queues.js:80:21) { packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> reason: 'server error', packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> statusCode: 500, packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> json: null packages/cactus-test-tooling/src/test/typescript/integration/substrate/substrate-test-ledger-constructor.test.ts 2> } I double checked that the image ghcr.io/rafaelapb/cactus-substrate-aio:2021-08-26-first exists locally with "docker image ls" and it does. However, it seems that tryPullimage() is trying to pull the image from the docker registry, and the image is not published there, which is probably the reason for this bug. From what I understood, only @peter_somogyvari can publish the images. Peter, is it possible for you to publish this image in the registry? (this image is generated from the dockerfile of PR https://github.com/hyperledger/cactus/pull/1274/files)

RafaelAPB (Fri, 24 Sep 2021 15:13:41 GMT):
That image is outdated. I can push the latest (or @peter_somogyvari could push your image to Hyperledger, so your PR tests pass)

CatarinaPedreira (Fri, 24 Sep 2021 17:44:13 GMT):
Thank you Rafael! The test is now finishing with success (I pushed the image to my github repo and set the visibility to public), but yes if Peter could publish it to the official repo it would be nice too :)

peter_somogyvari (Fri, 24 Sep 2021 18:02:40 GMT):
@RafaelAPB @CatarinaPedreira Built and published the image on the official repo from your branch as it is today. The fully qualified image tag: `ghcr.io/hyperledger/cactus-substrate-all-in-one:2021-09-24---feat-1274`

CatarinaPedreira (Fri, 24 Sep 2021 18:55:32 GMT):
Thank you, Peter!

RafaelAPB (Fri, 24 Sep 2021 19:03:21 GMT):
Congrats for your first image on the official Hyperledger repo @CatarinaPedreira :)

CatarinaPedreira (Fri, 24 Sep 2021 19:06:29 GMT):
Thank you :tyvm:

CatarinaPedreira (Sat, 25 Sep 2021 15:23:33 GMT):
@peter_somogyvari thank you for the comments on the substrate ledger pull request! Will check those today. I had to do another push to fix the PR because the CI failed before (I had an unknown word in the substrate ledger test file which I added to cspell.json). Can you approve the new workflow so that the tests run again? As soon as the tests pass again I will apply the requested changes :) Thanks!

CatarinaPedreira (Sat, 25 Sep 2021 15:23:33 GMT):
@peter_somogyvari thank you for the comments on the substrate ledger pull request! Will check those today. I had to do another push to fix the PR because the CI failed before (I had an unknown word in the substrate ledger test file which I now added to cspell.json). Can you approve the new workflow so that the tests run again? As soon as the tests pass again I will apply the requested changes :) Thanks!

peter_somogyvari (Sun, 26 Sep 2021 20:49:55 GMT):
@CatarinaPedreira My pleasure! Approved the workflow run, fingers crossed that it passes. :-)

CatarinaPedreira (Mon, 27 Sep 2021 10:32:40 GMT):
Thank you @peter_somogyvari :) Unfortunately it didn't pass yet. I downloaded the full logs to understand the error better - on the first two builds (v12.22.3 and v14.15.1) all the tests pass, but later the build fails at: 2021-09-26T20:49:45.5388439Z lerna ERR! yarn run webpack:prod:node stderr: 2021-09-26T20:49:45.5389085Z error Command failed with exit code 1. 2021-09-26T20:49:45.5390943Z lerna ERR! yarn run webpack:prod:node exited 1 in '@hyperledger/cactus-test-tooling' 2021-09-26T20:49:45.5392501Z lerna WARN complete Waiting for 2 child processes to exit. CTRL-C to exit immediately. 2021-09-26T20:49:45.5393374Z error Command failed with exit code 1. 2021-09-26T20:49:45.5394143Z ERROR: "webpack:prod:node" exited with 1. 2021-09-26T20:49:45.5394883Z error Command failed with exit code 1. 2021-09-26T20:49:45.5395504Z ERROR: "build:prod:backend" exited with 1. 2021-09-26T20:49:45.5396438Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 2021-09-26T20:49:45.5397549Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 2021-09-26T20:49:46.4197830Z error Command failed with exit code 1. 2021-09-26T20:49:46.4198978Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 2021-09-26T20:49:46.4201185Z ERROR: "build:prod" exited with 1. 2021-09-26T20:49:46.4202711Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 2021-09-26T20:49:46.4204895Z error Command failed with exit code 1. 2021-09-26T20:49:46.4206555Z 2021-09-26T20:49:45+0000 [CI] FAILURE - runtime=7473 seconds. 2021-09-26T20:49:46.4301383Z ##[error]Process completed with exit code 1. I noticed that the public-api.ts file in the cactus-test-tooling does not contain the SubstrateTestLedger class and options exported, but contains all the other test containers. Could this be the reason for this error? On the third build, the error comes from the substrate-test-ledger-constructor-test (a docker error that occurs sometimes, I'm not yet sure why, will check this problem).

karayel (Mon, 27 Sep 2021 11:22:31 GMT):
Has joined the channel.

karayel (Mon, 27 Sep 2021 11:22:32 GMT):
Hello everyone, In the discounted-cartrade example (in windows 10), while trying to execute indy validator, I got the following response and error: indy@5d5ec21336e5:~/cactus_validator_socketio/validator-python$ TEST_POOL_IP=172.16.0.2 python3.9 -m main socket port: 8000 Server initialized for threading. ##called init_indy() ##called run_coroutine() Open Pool Ledger: pool1 ##called run_coroutine() ##SocketIoValidator set pool_handle. WARNING:werkzeug:WebSocket transport not available. Install simple-websocket for improved performance. * Serving Flask app 'validator_socketio_module.SocketIoValidator' (lazy loading) * Environment: production WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. * Debug mode: off Traceback (most recent call last): File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.9/runpy.py", line 87, in _run_code exec(code, run_globals) File "/home/indy/cactus_validator_socketio/validator-python/main.py", line 6, in validator.run() File "/home/indy/cactus_validator_socketio/validator-python/validator_socketio_module/SocketIoValidator.py", line 100, in run self.socketio.run(self.app, host='0.0.0.0', port=self.settings.validatorSettings.port) File "/home/indy/.local/lib/python3.9/site-packages/flask_socketio/__init__.py", line 596, in run app.run(host=host, port=port, threaded=True, File "/home/indy/.local/lib/python3.9/site-packages/flask/app.py", line 922, in run run_simple(t.cast(str, host), port, self, **options) File "/home/indy/.local/lib/python3.9/site-packages/werkzeug/serving.py", line 1008, in run_simple inner() File "/home/indy/.local/lib/python3.9/site-packages/werkzeug/serving.py", line 948, in inner srv = make_server( File "/home/indy/.local/lib/python3.9/site-packages/werkzeug/serving.py", line 780, in make_server return ThreadedWSGIServer( File "/home/indy/.local/lib/python3.9/site-packages/werkzeug/serving.py", line 686, in __init__ super().__init__(server_address, handler) # type: ignore File "/usr/lib/python3.9/socketserver.py", line 452, in __init__ self.server_bind() File "/usr/lib/python3.9/http/server.py", line 138, in server_bind socketserver.TCPServer.server_bind(self) File "/usr/lib/python3.9/socketserver.py", line 466, in server_bind self.socket.bind(self.server_address) OSError: [Errno 98] Address already in use

peter_somogyvari (Mon, 27 Sep 2021 15:01:31 GMT):
Hi @karayel `OSError: [Errno 98] Address already in use` means that you are already running something on that port. Is there some other app you are running also bound to 8000? cc: @takeutak

peter_somogyvari (Mon, 27 Sep 2021 15:30:39 GMT):
@CatarinaPedreira > Could this be the reason for this error? Could be, but it depends on whether that class is being used outside the package or not. If some of the CI matrix's components succeeded then likely there's some other reason.

peter_somogyvari (Mon, 27 Sep 2021 15:30:47 GMT):
Do you have a link to the logs by any chance?

CatarinaPedreira (Mon, 27 Sep 2021 15:43:26 GMT):
https://pipelines.actions.githubusercontent.com/fj0OuKf7F4TwBPjQUvfmVpS0FfkJleikBwCtaNBd51na56cZD0/_apis/pipelines/1/runs/8748/signedlogcontent/3?urlExpires=2021-09-27T15%3A42%3A41.7844189Z&urlSigningMethod=HMACV1&urlSignature=%2BT1Yd6GeQcCoM9jF474%2BBip%2FKvGJW%2FPoevIYlu9UrHw%3D

CatarinaPedreira (Mon, 27 Sep 2021 15:43:52 GMT):
These are the logs for the first build

CatarinaPedreira (Mon, 27 Sep 2021 15:45:10 GMT):
Thanks for all your help :)

peter_somogyvari (Mon, 27 Sep 2021 16:01:53 GMT):
When I click on that link I get: `{"count":11,"value":"Uri expired"}` Oops. Let's just hope that the new execution I started recently will succeed, but if not, I'll check the logs of that one

peter_somogyvari (Tue, 28 Sep 2021 00:10:04 GMT):
Tonight's (or this morning's) maintainers meeting agenda: https://wiki.hyperledger.org/display/cactus/2021-09-28+Cactus+Maintainers+Agenda

takeutak (Tue, 28 Sep 2021 02:01:29 GMT):
Hi @karayel Thanks for contacting about discounted-cartrade. I'm contacting the developers of discounted-cartrade and they will answer soon. So could you wait for a moment?

takeutak (Tue, 28 Sep 2021 02:01:29 GMT):
Hi @karayel Thanks for contacting about discounted-cartrade. I'm contacting @t-yasushi (the developer of discounted-cartrade) and he will answer soon. So could you wait for a moment?

t-yasushi (Tue, 28 Sep 2021 02:22:06 GMT):
Has joined the channel.

t-yasushi (Tue, 28 Sep 2021 02:22:07 GMT):
Hi @karayel Thank you for contracting about discounted-cartrade. It seems to me that you are running the command “TEST _ POOL _ IP = 172.16.0.2 python -m main” on ~/cactus_validator_socketio/validator-python in local environment. However, this command must be executed on /root/validator in the validator container. So, please run the following commands: ... $docker exec -it validator bash $ cd /root/validator $ TEST_POOL_IP=172.16.0.2 python -m main ... (Reference: Step3 of https://github.com/hyperledger/cactus/blob/9a3d89ae2f5d4862d58a69c56b47d7de3ee7ac3d/examples/discounted-cartrade/README.md#how-to-execute-indy-validator)

karayel (Tue, 28 Sep 2021 06:16:07 GMT):
Thank you for your answer @t-yasushi Actually I ran the python code in the container. However, in the container I couldn't find the /root/validator directory. Then I guessed that I should run the main.py in the /cactus_validator_socketio/validator-python directory of the container. Regarding the problem I noticed the following commit: https://github.com/hyperledger/cactus/commit/35b20ac25df207c5cf329f60541c69375b408ab1 So is it possible that the related python code is actullay ran while container is started and when I try to run again I come accross the "address already used" error?

hammerstrike (Tue, 28 Sep 2021 07:33:31 GMT):
Has joined the channel.

hammerstrike (Tue, 28 Sep 2021 07:33:32 GMT):
What is the purpose of _'cactus-plugin-object-store-ipfs'_ plugin ?

hammerstrike (Tue, 28 Sep 2021 07:33:32 GMT):
What is the purpose of _'cactus-plugin-object-store-ipfs'_ ?

t-yasushi (Tue, 28 Sep 2021 09:46:02 GMT):
@karayel Thank you for telling me the situation. After Step 6 of the link below, can you try the following two operations? https://github.com/hyperledger/cactus/tree/main/examples/discounted-cartrade#how-to-construct-indy_testnet-environment The following operations are required to enter the validator container and launch the sample program to verify indy pool communication. 1. Mount sample programs folder 　 Add the following to the parameters in the validator of doker-compose.yaml: 　 (Change source to the directory containing indy-sdk.) ---------------------------------- validator: 　 volumes: - type: bind source: "/home/user001/workspace/indy-testnet/indy-sdk" 　 target: "/root/indy-sdk" ---------------------------------- 2. Log in to the validator container and run the sample program. ---------------------------------- 　 $ sudo docker exec -it bash 　 root@c09106e72918:/# cd ~/indy-sdk/samples/python/ 　 root@c09106e72918:~/indy-sdk# TEST_POOL_IP=172.16.0.2 python -m src.main ----------------------------------

karayel (Tue, 28 Sep 2021 10:48:01 GMT):
@t-yasushi it worked. thank you very much

t-yasushi (Tue, 28 Sep 2021 11:14:18 GMT):
It was very good to solve it!

t-yasushi (Tue, 28 Sep 2021 11:14:18 GMT):
@karayel It was very good to solve it!

trevoro1 (Tue, 28 Sep 2021 15:14:17 GMT):
Is there a list of the call schedule?

peter_somogyvari (Tue, 28 Sep 2021 23:06:14 GMT):
@trevoro1 Yup, you can access the calendar via our wiki for example (right hand sidebar has the calendar links) https://wiki.hyperledger.org/display/cactus

peter_somogyvari (Tue, 28 Sep 2021 23:08:17 GMT):
@hammerstrike It's an implementation of the object store plugin that uses IPFS for storing arbitrary pieces of data in a key/value store format. There is no specific example use case for it just yet but the idea is to provide an easier mental model to developers who are coming from a centralized cloud provider dev environment for example. E.g., if you used S3 or MinIO before, than this should look familiar but with IPFS being the backing storage.

RafaelAPB (Sun, 03 Oct 2021 17:07:32 GMT):
Hey @peter_somogyvari . What is the processes (if any) to publish npm packages? Is it per release? Cheers :)

takeutak (Mon, 04 Oct 2021 14:10:35 GMT):
Hi @peter_somogyvari cc: @JHamilton @hartm @sfuji822 The release of V1RC is coming soon, so I'd like to merge the following PRs before the V1RC is released. Would you mind if you review and approve these PRs? I'm afraid that I'm asking for a lot of reviews, but I'd like to ask for your cooperation. - https://github.com/hyperledger/cactus/pull/1408 - https://github.com/hyperledger/cactus/pull/1410 - https://github.com/hyperledger/cactus/pull/1411 - https://github.com/hyperledger/cactus/pull/1412 - https://github.com/hyperledger/cactus/pull/1413 - https://github.com/hyperledger/cactus/pull/1417 - https://github.com/hyperledger/cactus/pull/1419 - https://github.com/hyperledger/cactus/pull/1421 - https://github.com/hyperledger/cactus/pull/1423 - https://github.com/hyperledger/cactus/pull/1425 - https://github.com/hyperledger/cactus/pull/1426 - https://github.com/hyperledger/cactus/pull/1427 - https://github.com/hyperledger/cactus/pull/1430

JHamilton (Mon, 04 Oct 2021 14:30:52 GMT):
hey @takeutak will look later today. btw unfortunately i have a client demo session that is over our meeting today; i won't be able to join unless demo finishes early

karayel (Tue, 05 Oct 2021 11:00:40 GMT):
hi @t-yasushi after this step, i get PoolLedgerTimeout error in step 4. And myproof.json is not created. Sending the full response: User@DESKTOP-39BTG3F MINGW64 /c/dev/indy-sdk/samples/python (master) $ TEST_POOL_IP=172.16.0.2 python -m src.req_discounted_cartrade INFO:__main__:Getting started -> started INFO:__main__:Open Pool Ledger: pool1 INFO:indy.libindy.native.command_executor: src\commands\mod.rs:99 | Worker thread started INFO:indy.libindy.native.indy.commands: src\commands\mod.rs:140 | PoolCommand command received INFO:indy.libindy.native.pool_command_executor: src\commands\pool.rs:131 | SetProtocolVersion command received INFO:indy.libindy.native.indy.commands: src\commands\mod.rs:140 | PoolCommand command received INFO:indy.libindy.native.pool_command_executor: src\commands\pool.rs:62 | Create command received WARNING:indy.libindy:_indy_loop_callback: Function returned error INFO:indy.libindy.native.indy.commands: src\commands\mod.rs:140 | PoolCommand command received INFO:indy.libindy.native.pool_command_executor: src\commands\pool.rs:70 | Open command received INFO:indy.libindy.native.indy.commands: src\commands\mod.rs:140 | PoolCommand command received INFO:indy.libindy.native.indy.commands.pool: src\commands\pool.rs:74 | OpenAck handle 2, pool_id 2, result Err(IndyError { inner: Pool timeout Pool timeout }) WARNING:indy.libindy:_indy_loop_callback: Function returned error Traceback (most recent call last): File "C:\Users\User\AppData\Local\Programs\Python\Python36\lib\runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "C:\Users\User\AppData\Local\Programs\Python\Python36\lib\runpy.py", line 85, in _run_code exec(code, run_globals) File "C:\dev\indy-sdk\samples\python\src\req_discounted_cartrade.py", line 663, in run_coroutine(run) File "C:\dev\indy-sdk\samples\python\src\utils.py", line 52, in run_coroutine loop.run_until_complete(coroutine()) File "C:\Users\User\AppData\Local\Programs\Python\Python36\lib\asyncio\base_events.py", line 466, in run_until_complete return future.result() File "C:\dev\indy-sdk\samples\python\src\req_discounted_cartrade.py", line 101, in run pool_['handle'] = await pool.open_pool_ledger(pool_['name'], None) File "C:\Users\User\AppData\Local\Programs\Python\Python36\lib\site-packages\indy\pool.py", line 88, in open_pool_ledger open_pool_ledger.cb) indy.error.PoolLedgerTimeout

luisabrunhosa (Wed, 06 Oct 2021 07:02:15 GMT):
Hello everyone, is it possible to ask for 5 minutes of your time to respond a form to my master thesis? https://docs.google.com/forms/d/e/1FAIpQLSe7FDfcgXd8eUuNNHbyqaO-ZACpLeosa0YaSDQlFVpNc-XGEg/viewform?usp=sf_link Thank you very much for you colaboration

CatarinaPedreira (Thu, 07 Oct 2021 10:31:38 GMT):
Done :)

peter_somogyvari (Thu, 07 Oct 2021 17:22:52 GMT):
Same here @luisabrunhosa

RafaelAPB (Thu, 07 Oct 2021 17:31:42 GMT):
There might be a problem with Cactus commit 6bad29bddfb2a4ef3b98d7c8c4d41efad974bb56; upon running npm run configure, one gets: yarn install v1.18.0 warning Missing version in workspace at "/home/rafael/Projects/Cactus/blockchain-integration-framework/packages/cactus-cmd-socketio-server", ignoring. [1/4] Resolving packages... [2/4] Fetching packages... error An unexpected error occurred: "https://registry.yarnpkg.com/@ethereumjs/ethash/-/ethash-1.1.0.tgz: Request failed \"404 Not Found\""

takeutak (Mon, 11 Oct 2021 13:11:59 GMT):
Hi @peter_somogyvari cc: @JHamilton @hartm @sfuji822 @izuru @t-yasushi I have a favor to you. There was some correction error in the old files in the pevious PR #1411 , so I posted a new PR #1449 to fix the above problem. https://github.com/hyperledger/cactus/pull/1449 Would you mind if you approve the PR 1449 before releasing v1rc1? I'd like to merge this PR before the version V1rc1 is released.

takeutak (Mon, 11 Oct 2021 13:11:59 GMT):
Hi @peter_somogyvari cc: @JHamilton @hartm @sfuji822 @izuru @t-yasushi I have a favor to you. There was some correction error in the old files in the pevious PR #1411 , so I posted a new PR #1449 to fix the above problem. https://github.com/hyperledger/cactus/pull/1449 Would you mind if you approve the PR #1449 before releasing v1rc1? I'd like to merge this PR before the version V1rc1 is released.

takeutak (Mon, 11 Oct 2021 13:11:59 GMT):
Hi @peter_somogyvari cc: @JHamilton @hartm @sfuji822 @izuru @t-yasushi I have a favor for you. There was some correction error in the old files in the pevious PR #1411 , so I posted a new PR #1449 to fix the above problem. https://github.com/hyperledger/cactus/pull/1449 Would you mind if you approve the PR #1449 before releasing v1rc1? I'd like to merge this PR before the version V1rc1 is released.

takeutak (Mon, 11 Oct 2021 13:11:59 GMT):
Hi @peter_somogyvari cc: @JHamilton @hartm @sfuji822 @izuru @t-yasushi I'm afraid that I have an additional favor for you. There was some correction error in the old files in the pevious PR #1411 , so I posted a new PR #1449 to fix the above problem. https://github.com/hyperledger/cactus/pull/1449 Would you mind if you approve the PR #1449 before releasing v1rc1? I'd like to merge this PR before the version V1rc1 is released.

JacquesBikoundou (Thu, 14 Oct 2021 23:35:57 GMT):
Has joined the channel.

peter_somogyvari (Fri, 15 Oct 2021 16:12:45 GMT):
@CatarinaPedreira @RafaelAPB I had some more time to look into the subtrate contract node connectivity issue of the AIO image. Seems like they have additional CLI args that you can pass in to make it listen on all interfaces. It is quite confusing because they have `--ws-external Listen to all Websocket interfaces` but also `--unsafe-ws-external Listen to all Websocket interfaces` and the two appears to be doing the same thing according to the docs but I suspect maybe only the unsafe option works? The way I figured this out is by opening a shell directly into the running container and then saying `/var/www/node-template/.cargo/bin/substrate-contracts-node help` which printed out the documentation of theirs (which I could not otherwise locate in the github repo of the contracts node unfortunately). TLDR: Try passing in the `--unsafe-ws-external` flag and then check out the container logs appear to show that it is binding the WS port to *all* network interfaces not just localhost. One more thing to keep in mind: if you are observing the container logs through the cactus test execution, then this might not show up because the test will only start streaming the logs "as soon as possible" on a best effort basis and so there's a race condition here where I think the initial log messages of the container just don't appear in the test logs so you have to directly inspect the logs via the docker client on your terminal e.g. `docker logs your-container-name-or-id`

peter_somogyvari (Fri, 15 Oct 2021 16:13:13 GMT):

peter_somogyvari - Fri Oct 15 2021 09:12:56 GMT-0700 (Pacific Daylight Time).txt

pranav_kirtani (Fri, 15 Oct 2021 17:26:24 GMT):
Has joined the channel.

pranav_kirtani (Fri, 15 Oct 2021 17:26:25 GMT):
is there a plan to support hyperledger indy in the near future?

peter_somogyvari (Fri, 15 Oct 2021 18:28:12 GMT):
@pranav_kirtani Yup, hopefully rather sooner than later. :-)

RafaelAPB (Sat, 16 Oct 2021 00:31:00 GMT):
@peter_somogyvari That's brilliant! Thanks a lot for your help. @CatarinaPedreira please check if it works now :)

CatarinaPedreira (Sat, 16 Oct 2021 19:28:33 GMT):
Yes, I tested the image and it works now! Thank you so much for your help @peter_somogyvari :smiley:

peter_somogyvari (Mon, 18 Oct 2021 16:29:55 GMT):
@RafaelAPB @CatarinaPedreira My pleasure, glad we figured it out in the end! :-)

izuru (Tue, 19 Oct 2021 05:37:17 GMT):
there's socket.io version for indy [here](https://github.com/hyperledger/cactus/tree/main/packages-python/cactus_validator_socketio)

takeutak (Tue, 19 Oct 2021 06:13:50 GMT):
Hi @pranav_kirtani Thanks for your interest about Indy-support in Cactus! We already released indy connector plugin that is developed with python lang. https://github.com/hyperledger/cactus/tree/main/packages-python/cactus_validator_socketio @izuru and @t-yasushi are developers of this plugin. So, if you want to ask the usage of this plugin, would you contact them on RocketChat?

takeutak (Tue, 19 Oct 2021 06:13:50 GMT):
Hi @pranav_kirtani Thanks for your interest about Indy-support in Cactus! As @izuru mentioned, we already released indy connector plugin that is developed with python lang. https://github.com/hyperledger/cactus/tree/main/packages-python/cactus_validator_socketio @izuru and @t-yasushi are developers of this plugin. So, if you want to ask the usage of this plugin, would you contact them on RocketChat?

t-yasushi (Tue, 19 Oct 2021 08:02:25 GMT):
@karayel I am sorry for the delay in noticing your message, please wait a moment while I investigate the cause.

CatarinaPedreira (Sat, 23 Oct 2021 11:42:14 GMT):
Hey everyone. I wrote tests for the Polkadot Connector (which I still didn't push as a pull request), and all of them (except one) were passing the other day. Today, I ran them again and I get an "Error: Request failed with status code 404". It seems that this problem is internal to Axios, and the promise is not resolving when I call any function through my apiClient (the latter is built similarly to apiClients in the other connectors' tests). Did this happen to anyone? How can I fix this? Thank you.

CatarinaPedreira (Sat, 23 Oct 2021 11:42:14 GMT):
Hey everyone. I wrote tests for the Polkadot Connector (which I still didn't push as a pull request), and all of them (except one) were passing the other day. Today, I ran them again and I get an "Error: Request failed with status code 404". It seems that this problem is internal to Axios; the axios promise is being rejected when I call any function through my apiClient (the latter is built similarly to apiClients in the other connectors' tests). Did this happen to anyone? Does anyone know how I can fix this? Thank you.

CatarinaPedreira (Sat, 23 Oct 2021 11:42:14 GMT):
@peter_somogyvari @RafaelAPB can you help me with something? I wrote tests for the Polkadot Connector (which I still didn't push as a pull request), and all of them (except one) were passing the other day. Today, I ran them again (without changing the code or updating any library) and I get an "Error: Request failed with status code 404". It seems that this problem is internal to Axios; the axios promise is being rejected when I call any function through my apiClient (the latter is built similarly to apiClients in the other connectors' tests). I did some research on the bug and it seems like Axios is not being able to find "/api/v1/plugins/@hyperledger/cactus-plugin-ledger-connector-polkadot/get-transaction-info" although it has found it in the past. The function getTransactionInfo is generated by the OpenAPIGenerator, and it is present in the generated api.ts file. Did this happen to anyone in the past? And do you have an idea of how I can fix it? Thank you.

CatarinaPedreira (Sat, 23 Oct 2021 11:42:14 GMT):
@peter_somogyvari @RafaelAPB can you help me with the following? I wrote tests for the Polkadot Connector (which I still didn't push as a pull request), and all of them (except one) were passing the other day. Today, I ran them again (without changing the code or updating any library) and I get an "Error: Request failed with status code 404". It seems that this problem is internal to Axios; the axios promise is being rejected when I call any function through my apiClient (the latter is built similarly to apiClients in the other connectors' tests). I did some research on the bug and it seems like Axios is not being able to find "/api/v1/plugins/@hyperledger/cactus-plugin-ledger-connector-polkadot/get-transaction-info" although it has found it in the past. The function getTransactionInfo is generated by the OpenAPIGenerator, and it is present in the generated api.ts file. Did this happen to anyone in the past? And do you have an idea of how I can fix it? Thank you.

CatarinaPedreira (Sat, 23 Oct 2021 14:15:23 GMT):

error.txt

peter_somogyvari (Sat, 23 Oct 2021 18:05:28 GMT):
@CatarinaPedreira I'd double check if you are also registering the endpoint instance on the backend (in the plugin's registerWebSErvices function). Usually if that's missing then you get 404 errors. Also, if you can, please make sure your code compiles, then commit it, push it to a branch and send the link here then I can test it on my side and help with debugging if necessary. :-)

CatarinaPedreira (Sat, 23 Oct 2021 18:36:29 GMT):
Thank you Peter. I will double check that, push it to a branch and get back to you !

CatarinaPedreira (Sun, 24 Oct 2021 00:02:36 GMT):
Sorry for the delay, had to work on some other stuff in the meantime. It's solved, thank you :)) For some reason I commented out this particular endpoint instance from the registerWebServices function :person_facepalming_tone1:

peter_somogyvari (Sun, 24 Oct 2021 18:20:41 GMT):
@CatarinaPedreira No worries, the same thing happened to me about 10 times before I stopped making that mistake... :-)

dheerajbudhiraja (Wed, 27 Oct 2021 05:33:04 GMT):
Has joined the channel.

dheerajbudhiraja (Wed, 27 Oct 2021 05:33:05 GMT):
Hi Team, I was exploring corda connector, and wanted to know the format of private key, HostKey that needs to be passed in SSH for deploying jars to node. I passed pem as string but getting following logs on docker container: ``` 2021-10-26 06:50:45.019 INFO 10 --- [io-23000-exec-3] n.s.sshj.transport.random.JCERandom : Creating new SecureRandom. 2021-10-26 06:50:45.042 INFO 10 --- [io-23000-exec-3] n.schmizz.sshj.transport.TransportImpl : Client identity string: SSH-2.0-SSHJ_0.31.0 2021-10-26 06:50:45.056 INFO 10 --- [io-23000-exec-3] n.schmizz.sshj.transport.TransportImpl : Server identity string: SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 2021-10-26 06:50:45.114 INFO 10 --- [io-23000-exec-3] n.schmizz.sshj.transport.TransportImpl : Disconnected - BY_APPLICATION 2021-10-26 06:50:45.118 ERROR 10 --- [io-23000-exec-3] ApiPluginLedgerConnectorCordaServiceImpl : Failed to serve DeployContractJarsV1Request net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods at net.schmizz.sshj.SSHClient.auth(SSHClient.java:227) ~[sshj-0.31.0.jar!/:0.31.0] at net.schmizz.sshj.SSHClient.auth(SSHClient.java:202) ~[sshj-0.31.0.jar!/:0.31.0] ``` And API response as : ``` data: { timestamp: '2021-10-26T12:14:59.670Z', status: 500, error: 'Internal Server Error', message: 'No message available', path: '/api/v1/plugins/@hyperledger/cactus-plugin-ledger-connector-corda/deploy-contract-jars' } ```

peter_somogyvari (Wed, 27 Oct 2021 16:36:34 GMT):
@dheerajbudhiraja Where/how did you obtain the pem from that you are passing in?

dheerajbudhiraja (Thu, 28 Oct 2021 05:41:11 GMT):
pem is private key to connect to ssh.

dheerajbudhiraja (Thu, 28 Oct 2021 05:41:11 GMT):
pem I passed is private key to connect to ssh. And known host entry field is required , what to pass into that field? I tried passing node's public ssh key into that field. But I was getting same error logs in docker container as stated above. Below is sample values which I am using to pass into deployJars:

dheerajbudhiraja (Thu, 28 Oct 2021 05:41:11 GMT):
@peter_somogyvari pem I passed is private key to connect to ssh. And known host entry field is required , what to pass into that field? I tried passing node's public ssh key into that field. But I was getting same error logs in docker container as stated above. Below is sample values which I am using to pass into deployJars:

dheerajbudhiraja (Thu, 28 Oct 2021 05:49:01 GMT):
``` ```

dheerajbudhiraja (Thu, 28 Oct 2021 05:49:01 GMT):
```{ "containerId": "localhost-10006", "jars": [ { "contentBase64": "cordapp jar string", "filename": "cordapp-sample.jar", "hasDbMigrations": false } ], "cordappDeploymentConfigs": [ { "cordappDir": "/home/ubuntu/corda/byfn/PartyA/cordapps", "cordaNodeStartCmd": "/home/ubuntu/corda/byfn/runnodes.sh", "cordaJarPath": "/home/ubuntu/corda/byfn/PartyA/corda.jar", "nodeBaseDirPath": "/home/ubuntu/corda/byfn/PartyA", "rpcCredentials": { "hostname": "localhost", "port": 10006, "username": "user1", "password": "test" }, "sshCredentials": { "hostname": "localhost", "username": "ubuntu", "password": "ubuntu", "port": 22, "hostKeyEntry": "localhost ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEk7LK6UOYfAwaOer9faLfKn1MfAHBSUY3TlYVwe8OtK+3SlPwo6QYJVd60GS9W3ZwoULSG8bywBNd+vXoYsyho=" } } ] } ```

dheerajbudhiraja (Fri, 29 Oct 2021 05:41:56 GMT):
@peter_somogyvari I tried password authentication to node instead of key authentication, I think ssh connection is successful now but there is some Transaport exception during jar files transfer to node. Below are docker connector container logs: ``` [10:16] Karan Kulwal (CTO) 2021-10-28 04:31:56.124 INFO 9 --- [io-23000-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet 'dispatcherServlet' 2021-10-28 04:31:56.124 INFO 9 --- [io-23000-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet' 2021-10-28 04:31:56.189 INFO 9 --- [io-23000-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 65 ms 2021-10-28 04:32:26.942 INFO 9 --- [io-23000-exec-2] n.s.sshj.transport.random.JCERandom : Creating new SecureRandom. 2021-10-28 04:32:27.518 INFO 9 --- [io-23000-exec-2] n.schmizz.sshj.transport.TransportImpl : Client identity string: SSH-2.0-SSHJ_0.31.0 2021-10-28 04:32:27.585 INFO 9 --- [io-23000-exec-2] n.schmizz.sshj.transport.TransportImpl : Server identity string: SSH-2.0-APACHE-SSHD-2.3.0 2021-10-28 04:32:29.277 INFO 9 --- [io-23000-exec-2] o.h.c.p.l.c.c.s.impl.NodeRPCConnection : Trying to connect to RPC numberOfTriesRemaining=4 2021-10-28 04:32:29.277 INFO 9 --- [io-23000-exec-2] n.c.c.r.i.ReconnectingCordaRPCOps : Connecting to: localhost:10006 2021-10-28 04:32:30.209 INFO 9 --- [io-23000-exec-2] net.corda.client.rpc.internal.RPCClient : Startup took 931 msec 2021-10-28 04:32:31.832 INFO 9 --- [io-23000-exec-2] o.h.c.p.l.c.c.s.impl.NodeRPCConnection : ...done shutting down gracefully. 2021-10-28 04:32:34.707 ERROR 9 --- [ reader] n.schmizz.sshj.transport.TransportImpl : Dying because - Broken transport; encountered EOFnet.schmizz.sshj.transport.TransportException: Broken transport; encountered EOF at net.schmizz.sshj.transport.Reader.run(Reader.java:58) ~[sshj-0.31.0.jar!/:0.31.0]2021-10-28 04:32:34.707 INFO 9 --- [ reader] n.schmizz.sshj.transport.TransportImpl : Disconnected - UNKNOWN 2021-10-28 04:32:34.687 WARN 9 --- [eads-712609105)] n.c.c.r.internal.RPCClientProxyHandler : Terminating observables. 2021-10-28 04:32:34.761 ERROR 9 --- [io-23000-exec-2] net.schmizz.concurrent.Promise : <> woke to: net.schmizz.sshj.connection.ConnectionException: Broken transport; encountered EOF 2021-10-28 04:32:34.761 INFO 9 --- [io-23000-exec-2] n.schmizz.sshj.transport.TransportImpl : Disconnected - BY_APPLICATION 2021-10-28 04:32:34.774 ERROR 9 --- [io-23000-exec-2] ApiPluginLedgerConnectorCordaServiceImpl : Failed to serve DeployContractJarsV1Requestjava.lang.RuntimeException: Failed to upload jars to corda node. ```

dheerajbudhiraja (Fri, 29 Oct 2021 05:41:56 GMT):
@peter_somogyvari I tried password authentication to node instead of key authentication, I think ssh connection is successful now but there is some Transaport exception during jar files transfer to node. Below are docker connector container logs: ``` 2021-10-28 04:31:56.124 INFO 9 --- [io-23000-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet 'dispatcherServlet' 2021-10-28 04:31:56.124 INFO 9 --- [io-23000-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet' 2021-10-28 04:31:56.189 INFO 9 --- [io-23000-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 65 ms 2021-10-28 04:32:26.942 INFO 9 --- [io-23000-exec-2] n.s.sshj.transport.random.JCERandom : Creating new SecureRandom. 2021-10-28 04:32:27.518 INFO 9 --- [io-23000-exec-2] n.schmizz.sshj.transport.TransportImpl : Client identity string: SSH-2.0-SSHJ_0.31.0 2021-10-28 04:32:27.585 INFO 9 --- [io-23000-exec-2] n.schmizz.sshj.transport.TransportImpl : Server identity string: SSH-2.0-APACHE-SSHD-2.3.0 2021-10-28 04:32:29.277 INFO 9 --- [io-23000-exec-2] o.h.c.p.l.c.c.s.impl.NodeRPCConnection : Trying to connect to RPC numberOfTriesRemaining=4 2021-10-28 04:32:29.277 INFO 9 --- [io-23000-exec-2] n.c.c.r.i.ReconnectingCordaRPCOps : Connecting to: localhost:10006 2021-10-28 04:32:30.209 INFO 9 --- [io-23000-exec-2] net.corda.client.rpc.internal.RPCClient : Startup took 931 msec 2021-10-28 04:32:31.832 INFO 9 --- [io-23000-exec-2] o.h.c.p.l.c.c.s.impl.NodeRPCConnection : ...done shutting down gracefully. 2021-10-28 04:32:34.707 ERROR 9 --- [ reader] n.schmizz.sshj.transport.TransportImpl : Dying because - Broken transport; encountered EOFnet.schmizz.sshj.transport.TransportException: Broken transport; encountered EOF at net.schmizz.sshj.transport.Reader.run(Reader.java:58) ~[sshj-0.31.0.jar!/:0.31.0]2021-10-28 04:32:34.707 INFO 9 --- [ reader] n.schmizz.sshj.transport.TransportImpl : Disconnected - UNKNOWN 2021-10-28 04:32:34.687 WARN 9 --- [eads-712609105)] n.c.c.r.internal.RPCClientProxyHandler : Terminating observables. 2021-10-28 04:32:34.761 ERROR 9 --- [io-23000-exec-2] net.schmizz.concurrent.Promise : <> woke to: net.schmizz.sshj.connection.ConnectionException: Broken transport; encountered EOF 2021-10-28 04:32:34.761 INFO 9 --- [io-23000-exec-2] n.schmizz.sshj.transport.TransportImpl : Disconnected - BY_APPLICATION 2021-10-28 04:32:34.774 ERROR 9 --- [io-23000-exec-2] ApiPluginLedgerConnectorCordaServiceImpl : Failed to serve DeployContractJarsV1Requestjava.lang.RuntimeException: Failed to upload jars to corda node. ```

dheerajbudhiraja (Fri, 29 Oct 2021 08:09:50 GMT):
Debug logs: ``` 2021-10-29 08:05:43.338 DEBUG 10 --- [io-23000-exec-1] ApiPluginLedgerConnectorCordaServiceImpl : Starting SCP upload cordapp-sample.jar (size=15082) onto localhost:8222:/home/ubuntu/corda/byfn/PartyA/cordapps/ 2021-10-29 08:05:43.870 ERROR 10 --- [ reader] n.schmizz.sshj.transport.TransportImpl : Dying because - Broken transport; encountered EOF net.schmizz.sshj.transport.TransportException: Broken transport; encountered EOF ``` at line 206 of file: ApiPluginLedgerConnectorCordaServiceImpl.kt

peter_somogyvari (Fri, 29 Oct 2021 18:39:37 GMT):
@dheerajbudhiraja > And known host entry field is required , what to pass into that field? For now you can pass any non-blank string in there because that field is not used for now in the backend (the feature behind it is under construction)

peter_somogyvari (Fri, 29 Oct 2021 18:40:47 GMT):
@dheerajbudhiraja Are you using the Cactus Corda All In One container image or are you using a different container to run your Corda network?

peter_somogyvari (Fri, 29 Oct 2021 18:48:56 GMT):
@dheerajbudhiraja Also wanted to mention that we have pair programming sessions available for everyone publicly so if you feel it's easier to help you with screen sharing and talking live then let me know. Our pair prog sessions run 3 days a week on Monday, Wednesday, Friday 7:45 to 8:00 Pacific Time => https://lists.hyperledger.org/g/cactus/viewevent?repeatid=35080&eventid=1304688&calstart=2021-11-01

peter_somogyvari (Fri, 29 Oct 2021 20:49:08 GMT):
@dheerajbudhiraja One last thing: If you want to take a look at a working example that does what you are trying to do then look at this test case: `packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes-v4.8.test.ts` https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes-v4.8.test.ts

dheerajbudhiraja (Mon, 01 Nov 2021 06:18:34 GMT):
@peter_somogyvari Yes followed the same steps in the test file you shared. deployJars is succesfully connecting with node via ssh, shutting down the node, at SCP jar transfer step, it fails. One thing I wanted to clarify is ssh credentials used are for corda node only and not the host machine? I tried scp via terminal to corda node but that also doesn't works. Maybe I am missing something here. Will try to join programming pair session.

vinodhini (Tue, 02 Nov 2021 06:34:21 GMT):
Has joined the channel.

vinodhini (Tue, 02 Nov 2021 06:34:23 GMT):
Hi All How to install Hyperledger Cactus and what are its prerequisites??

RafaelAPB (Tue, 02 Nov 2021 17:41:38 GMT):
Hello @vinodhini , welcome to the community. You can find instructions on how to build the project here: https://github.com/hyperledger/cactus/blob/main/BUILD.md

KaranKulwal (Mon, 08 Nov 2021 11:53:49 GMT):
Has joined the channel.

KaranKulwal (Mon, 08 Nov 2021 11:53:50 GMT):
@peter_somogyvari any updates on the issue we raised on github? https://github.com/hyperledger/cactus/issues/1493

KaranKulwal (Mon, 08 Nov 2021 11:54:42 GMT):
The error for the issue which was missed `2021-11-08 11:53:08.534 INFO 9 --- [io-23000-exec-5] ApiPluginLedgerConnectorCordaServiceImpl : Progress(0)=[] 2021-11-08 11:53:08.534 INFO 9 --- [io-23000-exec-5] ApiPluginLedgerConnectorCordaServiceImpl : ReturnValue=kotlin.Unit 2021-11-08 11:53:08.535 INFO 9 --- [io-23000-exec-5] ApiPluginLedgerConnectorCordaServiceImpl : Id=[ba2d1e6d-8bca-4d17-a6f9-760089a31a40] 2021-11-08 11:53:08.536 ERROR 9 --- [io-23000-exec-5] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.ClassCastException: kotlin.Unit cannot be cast to net.corda.core.transactions.SignedTransaction] with root cause java.lang.ClassCastException: kotlin.Unit cannot be cast to net.corda.core.transactions.SignedTransaction `

peter_somogyvari (Mon, 08 Nov 2021 16:04:44 GMT):
@KaranKulwal Still investigating it. I hoped it would be faster, apologies! That log is very helpful though. Would you mind also sharing the request object (in JSON format) that triggered it? It might be that it could be fixed just by updating the request object but I'd have to see how it looks.

KaranKulwal (Wed, 10 Nov 2021 04:02:52 GMT):
here is the json object being sent to the invoke call ``` { "flowInvocationType": "FLOW_DYNAMIC", "flowFullClassName": "net.corda.samples.flowdb.AddTokenValueFlow", "params": [ { "jvmTypeKind": "PRIMITIVE", "jvmType": { "fqClassName": "java.lang.String" }, "primitiveValue": "Random" }, { "jvmTypeKind": "PRIMITIVE", "jvmType": { "fqClassName": "java.lang.Integer" }, "primitiveValue": 300 } ] } ```

KaranKulwal (Wed, 10 Nov 2021 04:33:29 GMT):
flow is getting executed for this but its returning error due to no return value *Output for flow execution when done in corda shell:* `Flow completed with result: kotlin.Unit`

elenaizaguirre (Mon, 15 Nov 2021 15:54:18 GMT):
Has joined the channel.

t-yasushi (Wed, 17 Nov 2021 05:51:11 GMT):
Hi @peter_somogyvari , I am currently trying to run corda-all-in-one (https://github.com/hyperledger/cactus/tree/main/tools/docker/corda-all-in-one) and when I try to build docker using the Dockerfile as described in line 25 of README, I get an error like the following. It may be because I run it in a proxy environment, but I don't know the cause well, so please tell me if you know anything. ***** Environment: OS: CentOS 7 docker ver: 20.10.5 proxy: on ***** ***** [user002@earth cactus_corda_test]$ cd tools/docker/corda-all-in-one/ [user002@earth corda-all-in-one]$ cd ../../.. [user002@earth cactus_corda_test]$ docker build ./tools/docker/corda-all-in-one/ -f ./tools/docker/corda-all-in-one/corda-v4_8/Dockerfile -t caio48 Sending build context to Docker daemon 29.7kB Step 1/65 : FROM docker:20.10.2-dind ---> 7569a61fe0d5 Step 2/65 : ARG SAMPLES_KOTLIN_SHA=30fd841dd035934bae75ab8910da3b6e3d5d6ee7 ---> Using cache ---> 8299c5a7e16c Step 3/65 : ARG SAMPLES_KOTLIN_CORDAPP_SUB_DIR_PATH="./Advanced/obligation-cordapp/" ---> Using cache ---> 01d23f55ccc1 Step 4/65 : ARG CORDA_TOOLS_SHELL_CLI_VERSION=4.8 ---> Using cache ---> 9520af3d010f Step 5/65 : WORKDIR / ---> Using cache ---> f5fa51da830c Step 6/65 : RUN apk update ---> Running in 239f871c0aa0 ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.12/main: DNS lookup error WARNING: Ignoring APKINDEX.2c4ac24e.tar.gz: No such file or directory fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/community/x86_64/APKINDEX.tar.gz ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.12/community: DNS lookup error WARNING: Ignoring APKINDEX.40a3604f.tar.gz: No such file or directory 2 errors; 48 distinct packages available The command '/bin/sh -c apk update' returned a non-zero code: 2 [user002@earth cactus_corda_test]$ *****

peter_somogyvari (Wed, 17 Nov 2021 14:20:22 GMT):
@t-yasushi Based on the error `ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.12/main: DNS lookup error` I would say it's most likely your proxy again because I haven't seen this error before in either the CI nor my local machines. :-(

peter_somogyvari (Wed, 17 Nov 2021 14:20:52 GMT):
@KaranKulwal Thank you for the info! @elenaizaguirre Is working on coming up with a fix as we speak!

peter_somogyvari (Wed, 17 Nov 2021 20:42:21 GMT):
@elenaizaguirre Please check the commit message on this one: https://github.com/elenaizaguirre/cactus/commit/b92aaf545773b6f470d2ff8d34d78f7c75a77577

deepakwipro (Thu, 18 Nov 2021 10:49:57 GMT):
Has joined the channel.

deepakwipro (Thu, 18 Nov 2021 10:49:58 GMT):
Hi @peter_somogyvari

deepakwipro (Thu, 18 Nov 2021 10:50:37 GMT):
Failed to deploy contract to fabric network: Error: Received exit code 127 while establishing SFTP session

deepakwipro (Thu, 18 Nov 2021 10:50:52 GMT):
facing this issue while deploying chaincode on fabric2.2

KaranKulwal (Thu, 18 Nov 2021 10:57:09 GMT):
ok I will check this out

peter_somogyvari (Mon, 22 Nov 2021 16:00:22 GMT):
@deepakwipro Could you please post the code that you've written to assemble the deploy contract request and the logs of the API server when the 127 exit code is returned?

deepakwipro (Tue, 23 Nov 2021 04:15:46 GMT):

deepakwipro - Tue Nov 23 2021 09:45:35 GMT+0530 (India Standard Time).txt

deepakwipro (Tue, 23 Nov 2021 08:45:04 GMT):
I found some solution regarding this issue:- I made change at line 207 in `node_modules/@hyperledger/cactus-plugin-ledger-connector-fabric/dist/lib/main/typescript/plugin-ledger-connector-fabric.js.` I replaced `await ssh.putDirectory(tmpDirPath, remoteDirPath);` with `await ssh.putDirectory(tmpDirPath, remoteDirPath,{concurrency: 1});`

peter_somogyvari (Tue, 23 Nov 2021 23:40:08 GMT):
@deepakwipro You are the best, thank you so much for coming up with the fix at the same time. :-) I'll commit the fix ASAP and we'll have a release with it hopefully next week in the form of `1.0.0-rc.3` Please keep an eye out for the release and the release notes to know when the fix is published onto npm.

peter_somogyvari (Tue, 23 Nov 2021 23:48:28 GMT):
FYI: https://github.com/hyperledger/cactus/pull/1572

KaranKulwal (Wed, 24 Nov 2021 04:46:39 GMT):
@peter_somogyvari This works with the db-flow, Thanks! Tested with this sample cordapp https://github.com/corda/samples-kotlin/tree/master/Basic/flow-database-access

peter_somogyvari (Wed, 24 Nov 2021 04:47:50 GMT):
Hi @KaranKulwal Yeah the fix is being reviewed as we speak, check this out: https://github.com/hyperledger/cactus/pull/1561

KaranKulwal (Thu, 25 Nov 2021 06:36:30 GMT):
Hi @peter_somogyvari Is private transaction support present in the current release of cactus-plugin in npm?

KaranKulwal (Thu, 25 Nov 2021 06:37:33 GMT):
I can see an open issue in github https://github.com/hyperledger/cactus/issues/951

deetho (Thu, 25 Nov 2021 12:03:57 GMT):
Has joined the channel.

deetho (Thu, 25 Nov 2021 12:03:59 GMT):
I am Deepakwipro. I tried on remoteVM then it again throws same error. Last time, i tried to test it on localhost only so may be for that it started working after adding concurrency:1. Pls look into this issue for remoteVM,

deetho (Thu, 25 Nov 2021 12:04:22 GMT):
@peter_somogyvari

dheerajbudhiraja (Thu, 25 Nov 2021 12:04:54 GMT):
Getting same error: ``` Failed to deploy contract to fabric network: Error: Received exit code 127 while establishing SFTP session at SFTP.onExit (/home/ubuntu/NodePro/node_modules/ssh2/lib/client.js:1500:23) ``` {concurrency: 1 } only works for localhost ssh. We need a solution for remote VMs also.

takeutak (Fri, 26 Nov 2021 10:26:10 GMT):
Hi @peter_somogyvari cc: @izuru I'd like to question about Corda plugin on behalf of one contributor who plans to contribute it (He will get LFID and access this page soon). He said that some error happened when he uses this plugin. Would you mind if you answer to the following question? ---- Question When I execute the following command, the Corda container starts without error, but the Corda-Connector container exits with an error. Would you please give me your thoughts to solve this error? At cactus/packages/cactus-plugin-ledger-connector-corda $ npx tap --ts --timeout=600 src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts Error message of Corda-connector container log org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'apiPluginLedgerConnectorCordaServiceImpl' defined in URL [jar:file:/usr/src/app/kotlin-spring/build/libs/cactus-connector-corda-server-0.3.0.jar!/BOOT-INF/classes!/org/hyperledger/cactus/plugin/ledger/connector/corda/server/impl/ApiPluginLedgerConnectorCordaServiceImpl.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'nodeRPCConnection': Invocation of init method failed; nested exception is net.corda.client.rpc.RPCException: Cannot connect to server(s). Tried with all available servers. Log The log of Corda container (image: ghcr.io/hyperledger/cactus-corda-4-6-all-in-one-obligation:2021-03-19-feat-686) "ghcr.iohyperledgercactus-corda-4-6-all-in-one-obligation2021-03-19-feat-686_log.txt" The log of Corda-connector (image: ghcr.io/hyperledger/cactus-connector-corda-server:2021-03-25-feat-622) "ghcr.iohyperledgercactus-connector-corda-server2021-03-25-feat-622_log.txt"

takeutak (Fri, 26 Nov 2021 10:26:21 GMT):

ghcr.iohyperledgercactus-corda-4-6-all-in-one-obligation2021-03-19-feat-686_log.txt

takeutak (Fri, 26 Nov 2021 10:26:22 GMT):

ghcr.iohyperledgercactus-corda-4-6-all-in-one-obligation2021-03-19-feat-686_log.txt

takeutak (Fri, 26 Nov 2021 10:26:40 GMT):

ghcr.iohyperledgercactus-corda-4-6-all-in-one-obligation2021-03-19-feat-686_log.txt

takeutak (Fri, 26 Nov 2021 10:26:41 GMT):

ghcr.iohyperledgercactus-corda-4-6-all-in-one-obligation2021-03-19-feat-686_log.txt

takeutak (Fri, 26 Nov 2021 10:27:16 GMT):
The related log messages are the above two txt files.

takeutak (Fri, 26 Nov 2021 10:46:07 GMT):

ghcr.iohyperledgercactus-connector-corda-server2021-03-25-feat-622_log.txt

takeutak (Fri, 26 Nov 2021 10:47:04 GMT):
The related log messages are the above two txt files.

FotisMichalopoulos (Mon, 29 Nov 2021 14:00:37 GMT):
Has joined the channel.

haniavis (Mon, 29 Nov 2021 14:09:07 GMT):
Has joined the channel.

haniavis (Mon, 29 Nov 2021 14:09:08 GMT):
Hi @takeutak and @peter_somogyvari we would like to use Cactus in our project for blockchain interoperability and we would like to know which is the best way to start. We have already tried to identify ways to develop our cactus-based solution, and tried the cartrade example but we now need to develop our own use case and business logic. Is there some files/directories that we can use as templates to write our business logic? Is there any documentation for this? And does Cactus support Fabric v2.x? Thanks for your support

takeutak (Tue, 30 Nov 2021 06:43:44 GMT):
HI @haniavis cc: @izuru Thanks for

takeutak (Tue, 30 Nov 2021 06:43:44 GMT):
HI @haniavis cc: @izuru Thanks for your interest about Cactus. (Now I'm writing the answer, please wait for a little...)

takeutak (Tue, 30 Nov 2021 06:43:44 GMT):
HI @haniavis cc: @izuru Thanks for your interest about Cactus! > Is there some files/directories that we can use as templates to write our business logic? Is there any documentation for this? I'm afraid that we are considering to prepare the template and documentation. As you said, the template and docs are useful for Cactus users, so I will notice you again if those are ready. > And does Cactus support Fabric v2.x? I'm afraid that the car-trade app currently supports only Fabric v1.x, but I will contact you if v2.x are supported. BTW, if you don't mind, we might be able to give you some advice if you let me know what use case you want to develop.

peter_somogyvari (Tue, 30 Nov 2021 23:22:17 GMT):
@takeutak That test must be a bit flaky because I just ran it and it worked on my machine (classic, I know). A few questions to help debug on your side: 1. Are you on the latest upstream/main (or a branch that's based on it)? 2. Have you executed `yarn configure` successfully prior to running the test? 3. Does it have the same problem if you try with the other test cases that I mentioned last time on our call, e.g. packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes-v4.8.test.ts ? (you will need to unskip the test in the code)

peter_somogyvari (Tue, 30 Nov 2021 23:23:27 GMT):
@KaranKulwal Sorry for the slow response! Besu has it but Quorum not yet. There's a PR that's being worked on to make it happen: https://github.com/hyperledger/cactus/pull/1337

peter_somogyvari (Tue, 30 Nov 2021 23:26:00 GMT):
@deetho @dheerajbudhiraja Alright, I shall look into that separately then, assuming it could have something to do with the higher latency between machines on account of the VM being remote. Any chance that you could post the output of a ping command here with which you pinged the remote VM just so that I get at least a rough idea of the latency we are talking about?

peter_somogyvari (Tue, 30 Nov 2021 23:29:29 GMT):
@deetho @dheerajbudhiraja Could you also let me know roughly the size of the chaincode that you are trying to deploy? E.g. is it 5 megabytes of 50 or 500?

peter_somogyvari (Tue, 30 Nov 2021 23:29:29 GMT):
@deetho @dheerajbudhiraja Could you also let me know 1. roughly the size of the chaincode that you are trying to deploy? E.g. is it 5 megabytes of 50 or 500? 2. Also the type of chain code that you are deploying (NodeJS, Go, Java?)

peter_somogyvari (Wed, 01 Dec 2021 00:14:05 GMT):
@haniavis Please take a look at the supply chain app example [1] [2] that uses the published ledger connector plugin for Fabric [3] (which does support Fabric 2.x) The seeming disconnect between what @takeutak and I am saying comes from historical reasons where some parts of the codebase are still in the process of getting integrated into the framework and so the car trade app and the relevant parts of it are not yet published on npm in any form just yet and you are better off looking at the packages that already are such as [3]. [1]: https://github.com/hyperledger/cactus/tree/main/examples/supply-chain-app [2]: https://github.com/hyperledger/cactus/blob/main/examples/cactus-example-supply-chain-business-logic-plugin/src/main/typescript/business-logic-plugin/supply-chain-cactus-plugin.ts [3]: https://www.npmjs.com/package/@hyperledger/cactus-plugin-ledger-connector-fabric

Kayaba.Keita (Wed, 01 Dec 2021 10:59:06 GMT):
Has joined the channel.

Kayaba.Keita (Wed, 01 Dec 2021 10:59:10 GMT):
Thank you for your response! (I am the contributor who @takeutak mentioned before.) I solved this error by opening the port for RPC ("32888" in this time). However, I got another error at deploying the smart contract. If you have any ideas to solve the error, I would appreciate your advice. [ghcr.iohyperledgercactus-connector-corda-server2021-03-25-feat-622_log] ********** ︙ ok 8 flowsRes1.data.flowNames truthy OK # apiClient.listFlowsV1() => {"flowNames":["net.corda.core.flows.ContractUpgradeFlow$Authorise","net.corda.core.flows.ContractUpgradeFlow$Deauthorise","net.corda.core.flows.ContractUpgradeFlow$Initiate","net.corda.finance.flows.CashExitFlow","net.corda.finance.flows.CashIssueAndPaymentFlow","net.corda.finance.flows.CashIssueFlow","net.corda.finance.flows.CashPaymentFlow","net.corda.finance.internal.CashConfigDataFlow","net.corda.samples.obligation.flows.IOUIssueFlow","net.corda.samples.obligation.flows.IOUSettleFlow","net.corda.samples.obligation.flows.IOUTransferFlow","net.corda.samples.obligation.flows.SelfIssueCashFlow"]} [2021-12-01T05:26:51.367Z] DEBUG (CordaConnectorContainer): [ghcr.io/hyperledger/cactus-connector-corda-server:2021-03-25-feat-622] '\x1B[2m2021-12-01 05:26:51.355\x1B[0;39m \x1B[32mDEBUG\x1B[0;39m \x1B[35m7\x1B[0;39m \x1B[2m---\x1B[0;39m \x1B[2m[nio-8080-exec-6]\x1B[0;39m \x1B[36mApiPluginLedgerConnectorCordaServiceImpl\x1B[0;39m \x1B[2m:\x1B[0;39m Creating new SSHClient object for CordappDeploymentConfig #0...\r\n' [2021-12-01T05:26:51.436Z] DEBUG (CordaConnectorContainer): [ghcr.io/hyperledger/cactus-connector-corda-server:2021-03-25-feat-622] '\x1B[2m2021-12-01 05:26:51.432\x1B[0;39m \x1B[32m INFO\x1B[0;39m \x1B[35m7\x1B[0;39m \x1B[2m---\x1B[0;39m \x1B[2m[nio-8080-exec-6]\x1B[0;39m \x1B[36mn.s.sshj.transport.random.JCERandom \x1B[0;39m \x1B[2m:\x1B[0;39m Creating new SecureRandom.\r\n' [2021-12-01T05:26:51.509Z] DEBUG (CordaConnectorContainer): [ghcr.io/hyperledger/cactus-connector-corda-server:2021-03-25-feat-622] '\x1B[2m2021-12-01 05:26:51.508\x1B[0;39m \x1B[32mDEBUG\x1B[0;39m \x1B[35m7\x1B[0;39m \x1B[2m---\x1B[0;39m \x1B[2m[nio-8080-exec-6]\x1B[0;39m \x1B[36mApiPluginLedgerConnectorCordaServiceImpl\x1B[0;39m \x1B[2m:\x1B[0;39m Connecting with new SSHClient object for CordappDeploymentConfig #0...\r\n' [2021-12-01T05:26:52.541Z] DEBUG (CordaConnectorContainer): [ghcr.io/hyperledger/cactus-connector-corda-server:2021-03-25-feat-622] '\x1B[2m2021-12-01 05:26:52.539\x1B[0;39m \x1B[31mERROR\x1B[0;39m \x1B[35m7\x1B[0;39m \x1B[2m---\x1B[0;39m \x1B[2m[nio-8080-exec-6]\x1B[0;39m \x1B[36mApiPluginLedgerConnectorCordaServiceImpl\x1B[0;39m \x1B[2m:\x1B[0;39m Failed to serve DeployContractJarsV1Request\r\n' [2021-12-01T05:26:52.541Z] DEBUG (CordaConnectorContainer): [ghcr.io/hyperledger/cactus-connector-corda-server:2021-03-25-feat-622] 'java.net.NoRouteToHostException: No route to host (Host unreachable)\r\n' ︙ **********

K.Keita (Wed, 01 Dec 2021 12:29:56 GMT):
Thank you for your response! (I am the contributor who @takeutak mentioned before.) I solved this error by opening the port for RPC (e.g. "32888" in this time). However, I got another error at "apiClient1.getPrometheusMetricsV1()" in "deploy-cordapp-jars-to-nodes.test.ts". If you have any ideas to solve the error, I would appreciate your advice. (I guess that it may be caused by a port issue, too.) ************************************************ ... ok 25 should be truthy ok 26 should be truthy ok 27 should be strictly equal not ok 28 Total Transaction Count of 1 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11) stack: |- Error: Total Transaction Count of 1 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ok 29 should be truthy ok 30 should be truthy ok 31 should be strictly equal not ok 32 Total Transaction Count of 2 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11) stack: |- Error: Total Transaction Count of 2 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ************************************************

K.Keita (Wed, 01 Dec 2021 12:29:56 GMT):
Thank you for your response! (I am the contributor who @takeutak mentioned before.) I solved this error by opening the port for RPC (e.g. "32888" in this time). However, I got another error at "t.true(promRes.data.includes(promMetricsOutput), "Total Transaction Count of 1 recorded as expected. RESULT OK",)" in "deploy-cordapp-jars-to-nodes.test.ts". If you have any ideas to solve the error, I would appreciate your advice. (I guess that it may be caused by a port issue, too.) ************************************************ ... ok 25 should be truthy ok 26 should be truthy ok 27 should be strictly equal not ok 28 Total Transaction Count of 1 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11) stack: |- Error: Total Transaction Count of 1 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ok 29 should be truthy ok 30 should be truthy ok 31 should be strictly equal not ok 32 Total Transaction Count of 2 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11) stack: |- Error: Total Transaction Count of 2 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ************************************************

K.Keita (Wed, 01 Dec 2021 12:29:56 GMT):
Thank you for your response! (I am the contributor who @takeutak mentioned before.) I solved this error by opening the port for RPC (e.g. "32888" in this time). However, I got another error at "t.true(promRes.data.includes(promMetricsOutput), "Total Transaction Count of 1 recorded as expected. RESULT OK",)" in "deploy-cordapp-jars-to-nodes.test.ts". If you have any ideas to solve the error, I would appreciate your advice. (I guess that it may be caused by some port issues, too.) ************************************************ ... ok 25 should be truthy ok 26 should be truthy ok 27 should be strictly equal not ok 28 Total Transaction Count of 1 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11) stack: |- Error: Total Transaction Count of 1 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ok 29 should be truthy ok 30 should be truthy ok 31 should be strictly equal not ok 32 Total Transaction Count of 2 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11) stack: |- Error: Total Transaction Count of 2 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ************************************************

K.Keita (Wed, 01 Dec 2021 12:29:56 GMT):
Thank you for your response! (I am the contributor who @takeutak mentioned before.) I solved this error by opening the port for RPC (e.g. "32888" in this time). However, I got another error at "t.true(promRes.data.includes(promMetricsOutput), "Total Transaction Count of 1 recorded as expected. RESULT OK",)" in "deploy-cordapp-jars-to-nodes.test.ts". If you have any ideas to solve the error, I would appreciate your advice. (Do we have something to do related to Prometheus before running "deploy-cordapp-jars-to-nodes.test.ts"? Otherwise, I guess that it may be caused by some port issues, too.) ************************************************ ... ok 25 should be truthy ok 26 should be truthy ok 27 should be strictly equal not ok 28 Total Transaction Count of 1 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11) stack: |- Error: Total Transaction Count of 1 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:369:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ok 29 should be truthy ok 30 should be truthy ok 31 should be strictly equal not ok 32 Total Transaction Count of 2 recorded as expected. RESULT OK --- operator: ok expected: true actual: false at: (~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11) stack: |- Error: Total Transaction Count of 2 recorded as expected. RESULT OK at Test.assert [as _assert] (~/cactus/node_modules/tape/lib/test.js:311:54) at Test.bound [as _assert] (~/cactus/node_modules/tape/lib/test.js:96:32) at Test.assert (~/cactus/node_modules/tape/lib/test.js:430:10) at Test.bound [as true] (~/cactus/node_modules/tape/lib/test.js:96:32) at ~/cactus/packages/cactus-plugin-ledger-connector-corda/src/test/typescript/integration/deploy-cordapp-jars-to-nodes.test.ts:392:11 at processTicksAndRejections (node:internal/process/task_queues:96:5) ... ************************************************

peter_somogyvari (Wed, 01 Dec 2021 20:22:17 GMT):
@K.Keita Yeah you do need to have your firewall open for ports that are being used. Looking at the second error with this additional piece of information in mind I would also guess the firewall first.

KaranKulwal (Thu, 02 Dec 2021 03:55:15 GMT):
Great @peter_somogyvari. can you please give a time window for quorum private transaction?

K.Keita (Thu, 02 Dec 2021 12:13:53 GMT):
I solved the error by modifying 'hostname: "0.0.0.0"' in line 334 of the script to 'hostname: "localhost"'. Thank you!

peter_somogyvari (Thu, 02 Dec 2021 17:54:51 GMT):
@K.Keita That's interesting, if the firewall doesn't let you bind to 0.0.0.0 I thought the code would error out because of it, but maybe the firewall doesn't block the OS from binding but then proceeds to black-hole all traffic related to that port anyway (and so the OS happily confirms the port bind which doesn't actually work)

peter_somogyvari (Thu, 02 Dec 2021 17:56:04 GMT):
@KaranKulwal Estimations are hard™, but I'll go ahead and say that the PR with the quorum private tx support should be merged in December.

K.Keita (Fri, 03 Dec 2021 02:01:58 GMT):
I do not exactly understand what happened, but I guess that a http proxy in our environment causes this error somehow. What I had tried is as below. 1. I run the script, and I got the error which said "

Access to this site is blocked by the administrator

". I guessed that something happened on a http connection. *********** ... const listenOptions: IListenOptions = { hostname: "0.0.0.0", port: 33333, server, }; ... t.ok(promRes.data); console.log(promRes.data) t.equal(promRes.status, 200); ... *********** Console outputs of *********** ... ok 26 should be truthy

Access to this site is blocked by the administrator

ok 27 should be strictly equal ... *********** 2. I executed "curl" command to "localhost" and "0.0.0.0", and doing "localhost" is worked. Console *********** $ curl http://localhost:33333/api/v1/plugins/@hyperledger/cactus-plugin-ledger-connector-corda/get-prometheus-exporter-metrics # HELP cactus_corda_total_tx_count Total transactions executed # TYPE cactus_corda_total_tx_count gauge cactus_corda_total_tx_count{type="cactus_corda_total_tx_count"} 2 $ curl http://0.0.0.0:33333/api/v1/plugins/@hyperledger/cactus-plugin-ledger-connector-corda/get-prometheus-exporter-metrics

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it may be by our http proxy.

Access to this site is blocked by the administrator

ok 27 should be strictly equal ... *********** 2. I executed "curl" command to "localhost" and "0.0.0.0", and doing "localhost" only worked. Console *********** $ curl http://localhost:33333/api/v1/plugins/@hyperledger/cactus-plugin-ledger-connector-corda/get-prometheus-exporter-metrics # HELP cactus_corda_total_tx_count Total transactions executed # TYPE cactus_corda_total_tx_count gauge cactus_corda_total_tx_count{type="cactus_corda_total_tx_count"} 2 $ curl http://0.0.0.0:33333/api/v1/plugins/@hyperledger/cactus-plugin-ledger-connector-corda/get-prometheus-exporter-metrics

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it may be by our http proxy.

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it might be by our http proxy.

K.Keita (Fri, 03 Dec 2021 02:01:58 GMT):
I do not exactly understand what happened, but I guess that a http proxy in our environment causes this error somehow. What I tried is as below. 1. I run the script, and I got the error which said "

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it might be by our http proxy.

Access to this site is blocked by the administrator

". I guessed that something happened on a http connection. *********** ... const listenOptions: IListenOptions = { hostname: "0.0.0.0", port: 33333, server, }; ... t.ok(promRes.data); console.log(promRes.data) // I added it. t.equal(promRes.status, 200); ... *********** Console outputs of *********** ... ok 26 should be truthy

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it might be by our http proxy.

K.Keita (Fri, 03 Dec 2021 02:01:58 GMT):
I do not exactly understand what happened, but I guess that a http proxy in my environment causes this error somehow. What I tried is as below. 1. I run the script, and I got the error which said "

Access to this site is blocked by the administrator

". I guessed that something happened on a http connection. *********** ... const listenOptions: IListenOptions = { hostname: "0.0.0.0", port: 33333, server, }; ... t.ok(promRes.data); console.log(promRes.data) // I added it. t.equal(promRes.status, 200); ... *********** Console outputs of *********** ... ok 26 should be truthy

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it might be by my http proxy.

K.Keita (Fri, 03 Dec 2021 02:01:58 GMT):
@peter_somogyvari I do not exactly understand what happened, but I guess that a http proxy in my environment causes this error somehow. What I tried is as below. 1. I run the script, and I got the error which said "

Access to this site is blocked by the administrator

". I guessed that something happened on a http connection. *********** ... const listenOptions: IListenOptions = { hostname: "0.0.0.0", port: 33333, server, }; ... t.ok(promRes.data); console.log(promRes.data) // I added it. t.equal(promRes.status, 200); ... *********** Console outputs of *********** ... ok 26 should be truthy

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it might be by my http proxy.

Access to this site is blocked by the administrator

". I guessed that something happened on a http connection. *********** ... const listenOptions: IListenOptions = { hostname: "0.0.0.0", port: 33333, server, }; ... t.ok(promRes.data); console.log(promRes.data) // I added it. t.equal(promRes.status, 200); ... *********** Console outputs of *********** ... ok 26 should be truthy

Access to this site is blocked by the administrator

*********** 3. I guessed that connecting to "0.0.0.0" which is the destination of "apiClient1.getPrometheusMetricsV1()" (right?) caused the error, and it might be by my http proxy.

KaranKulwal (Fri, 03 Dec 2021 04:33:52 GMT):
ok thanks @peter_somogyvari

haniavis (Fri, 03 Dec 2021 07:50:18 GMT):
Thanks @takeutak and @peter_somogyvari! It would be very helpful if we had these templates and the documentation, so please let us know when ready. Our use case is the interoperability in the supply chain very similar on your example, but mostly synchronisation between existing ledgers

haniavis (Fri, 03 Dec 2021 07:50:18 GMT):
Thanks @takeutak and @peter_somogyvari! It would be very helpful if we had these templates and the documentation, so please let us know when ready. Our use case is the interoperability in the supply chain very similar with your example, but mostly synchronisation between existing ledgers

peter_somogyvari (Fri, 03 Dec 2021 15:51:40 GMT):
@haniavis Absolutely, please stay tuned for the 1.0 release which is hopefully dropping early next year. If you DM me your contact details we could chat more about your use case too, I'd be interested in some more specifics such as whether you need atomic swaps or just eventual consistency between the separate ledgers and what kind of data is being moved and between what type of ledgers (I assume one of them is likely to be Fabric based on your question)

peter_somogyvari (Fri, 03 Dec 2021 15:56:54 GMT):
@K.Keita I agree and thank you for the detailed write-up on the issue and the investigation. I'll open a bug to fix the test cases where we are needlessly binding to all network interfaces instead of just the localhost. (All tests should be able to pass by binding to either localhost or the specific private LAN IP of the interface - for tests where multiple containers need to talk to each other)

peter_somogyvari (Fri, 03 Dec 2021 16:37:19 GMT):
https://github.com/hyperledger/cactus/issues/1624

peter_somogyvari (Sun, 05 Dec 2021 03:51:04 GMT):
@takeutak Do you use the `jade` dependency for anything in `packages/cactus-cmd-socketio-server/package.json` ? I'm asking because of this: https://github.com/advisories/GHSA-4vmm-mhcq-4x9j

izuru (Tue, 07 Dec 2021 08:08:52 GMT):
we will investigate that and try to remove that dependency

peter_somogyvari (Tue, 07 Dec 2021 17:24:47 GMT):
@izuru Thank you. FYI: I also took a quick look as well and it did not appear to be in use (I did free text searches)

pranjay (Thu, 09 Dec 2021 17:23:39 GMT):
Hi everyone , I am new to this dev environment and wanted to know how can I run and test the manual-consortium-plugin ? I have installed all dependencies for development.

pranjay (Thu, 09 Dec 2021 17:23:39 GMT):
Hi everyone, I am new to the cactus dev environment and wanted to know, how can I run or test the manual-consortium-plugin ? I have already installed all dependencies and set up the project for development.

pranjay (Thu, 09 Dec 2021 17:23:42 GMT):
https://github.com/hyperledger/cactus/blob/main/packages/cactus-plugin-consortium-manual/package.json

Princekumar4812 (Thu, 09 Dec 2021 17:53:32 GMT):
Has joined the channel.

Princekumar4812 (Thu, 09 Dec 2021 17:53:33 GMT):
Can anyone please update when the next meeting is?

Princekumar4812 (Thu, 09 Dec 2021 17:54:40 GMT):
Can anyone please update when the next maintainer meeting is??

peter_somogyvari (Thu, 09 Dec 2021 18:20:10 GMT):
@Princekumar4812 The next one is on the 13th of December, 4 PM Pacific Time. Then the next two after that will most likely get cancelled due to most people going on PTO for the last two weeks of the month, but I cannot confirm nor deny that until we discuss it with the rest of the maintainers as per the agenda => https://wiki.hyperledger.org/display/cactus/2021-12-13+Cactus+Maintainers+Agenda+-+Regular+Session

SeanBohan (Fri, 17 Dec 2021 19:58:29 GMT):
Has joined the channel.

deetho (Mon, 20 Dec 2021 08:25:52 GMT):
@peter_somogyvari do cactus have function to get list of committed chaincodes in HLF?

peter_somogyvari (Mon, 20 Dec 2021 21:16:40 GMT):
@deetho You could probably invoke one of the system chaincodes via the Fabric connector to get the information you want. For example the LSCC system chaincode seems to have operations for listing the chain codes installed: https://github.com/hyperledger/fabric/blob/main/core/scc/lscc/lscc.go Also, we have an example of the Fabric connector doing something similar internally where it queries the QSCC system CC to obtain blocks by transaction ID packages/cactus-plugin-ledger-connector-fabric/src/main/typescript/common/get-transaction-receipt-by-tx-id.ts So you could probably take pieces of that code as inspiration or as a helpful example. And please let me know if you could make it work because if not, I would want to know why (and then if it's an issue with the connector then we need to fix that as abug)

RafaelAPB (Thu, 23 Dec 2021 16:49:03 GMT):
Hello All! Sharing an updated version of "A Survey on Blockchain Interoperability: Past, Present, and Future Trends", featuring Cactus. https://dl.acm.org/doi/10.1145/3471140 Happy holidays all!

peter_somogyvari (Tue, 28 Dec 2021 00:41:09 GMT):
@RafaelAPB Thank you for sharing, I shall peruse the updated version ASAP :-) Happy holidays to you as well!

peter_somogyvari (Mon, 03 Jan 2022 19:12:57 GMT):
Happy new year! I've posted the maintainer's agenda for today's meeting: https://wiki.hyperledger.org/display/cactus/2022-01-03+Cactus+Maintainers+Agenda

aldous.arvin.alvarez (Tue, 04 Jan 2022 01:53:18 GMT):
Has joined the channel.

jagpreet (Tue, 11 Jan 2022 07:15:36 GMT):
Today's (8am GMT, January 11th 2022) maintainers meeting agenda: https://wiki.hyperledger.org/display/cactus/2022-01-11+Cactus+Maintainers+Agenda

sbohanlf (Tue, 25 Jan 2022 15:16:55 GMT):
Has joined the channel.

peter_somogyvari (Tue, 01 Feb 2022 06:06:01 GMT):
Hi All, I uploaded the agenda for tonight (it's open for addition of new items as usual) https://wiki.hyperledger.org/display/cactus/2022-02-01+Cactus+Maintainers+Agenda

peter_somogyvari (Tue, 01 Feb 2022 18:37:29 GMT):
Hi All, I'm cross posting this from an earlier TSC meeting where it was announced. Highly recommend to check it out, I also signed up to be an ambassador for the challenge: > The Hyperledger community is launching the Hyperledger Challenge to harness the power of communities to develop & launch innovative solutions using open-source technologies. Submissions for the Ideate challenge will be accepted until March 1. > > https://lnkd.in/gk-8PvWM

peter_somogyvari (Mon, 07 Feb 2022 15:43:07 GMT):
Hi All, The agenda for today's maintainers' meeting is up: https://wiki.hyperledger.org/display/cactus/2022-02-07+Cactus+Maintainers+Agenda Kind regards, Peter

charellesandig (Tue, 08 Feb 2022 10:39:29 GMT):
Has joined the channel.

john.h.o.mantaring (Tue, 08 Feb 2022 10:59:50 GMT):
Has joined the channel.

rjones (Wed, 23 Mar 2022 17:35:06 GMT):