rjones (Tue, 07 May 2019 17:20:37 GMT):
User User_1 added by rjones.

rjones (Tue, 07 May 2019 17:20:44 GMT):
amundson

rjones (Tue, 07 May 2019 17:20:54 GMT):
Has left the channel.

amundson (Tue, 07 May 2019 19:31:37 GMT):
@rjones thanks!

rjones (Tue, 07 May 2019 19:31:38 GMT):
Has joined the channel.

mfford (Tue, 07 May 2019 19:38:24 GMT):
Has joined the channel.

rbuysse (Tue, 07 May 2019 19:54:12 GMT):
Has joined the channel.

amundson (Tue, 07 May 2019 19:55:04 GMT):
First topic is project name...

danoprey (Tue, 07 May 2019 19:55:15 GMT):
Has joined the channel.

amundson (Tue, 07 May 2019 19:56:11 GMT):
Some ideas I've received:

amundson (Tue, 07 May 2019 19:56:13 GMT):
Hyperledger Delta - Transforms the state from the smart contracts above to framework below Hyperledger Transmission - Transmits the power from the smart contract “engine” to the ledger Hyperledger Torque - Bit catchier on the car/engine theme Hyperledger Shift - Transition from one state to another Hyperledger Turing - Because Hyperledger Edge - Represent transitions from one state to another as caused by the input (feels a bit IoT/edge computing to me though)

danoprey (Tue, 07 May 2019 19:56:19 GMT):
they're all brilliant

amundson (Tue, 07 May 2019 19:56:29 GMT):
^ from @danoprey

amundson (Tue, 07 May 2019 19:56:31 GMT):
LOL

amundson (Tue, 07 May 2019 19:57:18 GMT):
Hyperledger Mill - processes inputs into outputs, mill city, etc. from @jsmitchell

jsmitchell (Tue, 07 May 2019 19:57:19 GMT):
Has joined the channel.

amundson (Tue, 07 May 2019 19:57:45 GMT):
Hyperledger Morpheus - from @mfford

ltseeley (Tue, 07 May 2019 19:57:56 GMT):
Has joined the channel.

amundson (Tue, 07 May 2019 19:59:06 GMT):
we liked 'Hyperledger Particle' but there is another OSS particle project already

pschwarz (Tue, 07 May 2019 19:59:10 GMT):
Has joined the channel.

amundson (Tue, 07 May 2019 19:59:56 GMT):
I've heard some generally good responses to Mill, Morpheus, and Torque

amundson (Tue, 07 May 2019 20:00:36 GMT):
Many still like 'Hyperledger Transact'

amundson (Tue, 07 May 2019 20:02:26 GMT):
Please give opinions and suggest other options!

cecchi (Tue, 07 May 2019 20:53:54 GMT):
Has joined the channel.

cecchi (Tue, 07 May 2019 20:53:55 GMT):
i like Transact

cecchi (Tue, 07 May 2019 20:55:23 GMT):
Transact is an implementation of an abstraction, so maybe *Hyperledger Dali* or *Hyperledger Rothko*?

cecchi (Tue, 07 May 2019 20:58:11 GMT):
it's also kind of a "one thing to rule them all" - so maybe *Hyperledger Asha* which is a deep cut reference to the largely agreed upon name of the 'ring' in LOTR: _Ash Nazg_

cecchi (Tue, 07 May 2019 21:08:25 GMT):
lastly, a plug for *Hyperledger Cornholio*, someone who always needed TP (transaction processing)

jsmitchell (Tue, 07 May 2019 21:08:30 GMT):

Clipboard - May 7, 2019 4:08 PM

cecchi (Tue, 07 May 2019 21:09:05 GMT):
well it's clear we have a winner

rjones (Tue, 07 May 2019 21:10:11 GMT):
Find me a good clean gif of that and I'll add it as a custom reaction, like :cries:

amundson (Tue, 07 May 2019 21:53:50 GMT):
@cecchi what a corny suggestion

danoprey (Tue, 07 May 2019 21:57:11 GMT):

troll.png

amundson (Tue, 07 May 2019 22:02:22 GMT):
unfortunately, we will be dropping the TP name. mostly because of the cornholio joke.

amundson (Tue, 07 May 2019 22:02:33 GMT):
smart contract engines forever

amundson (Tue, 07 May 2019 22:03:07 GMT):
I think it substantially raises the bar if we have to submit a graphic with our name suggestions :)

danoprey (Tue, 07 May 2019 22:04:11 GMT):
We will need an icon at some point, under this format. but the LF creative team can assist with that

danoprey (Tue, 07 May 2019 22:05:02 GMT):
"Hyperledger Transact" is far too generic, unfortunately. I'm not sure there's a blockchain project that couldn't qualify for that name

danoprey (Tue, 07 May 2019 22:05:19 GMT):
Mill isn't bad

amundson (Tue, 07 May 2019 22:06:05 GMT):
too generic? do you mean too literal?

danoprey (Tue, 07 May 2019 22:06:32 GMT):
too literal and too widely applicable

amundson (Tue, 07 May 2019 22:09:57 GMT):
much less than "composer" or "explorer" though, if we are using current names as a guide

danoprey (Tue, 07 May 2019 22:12:43 GMT):
those were mistakes... to be frank

amolk (Wed, 08 May 2019 02:19:05 GMT):
Has joined the channel.

amolk (Wed, 08 May 2019 02:21:34 GMT):
[ ](https://chat.hyperledger.org/channel/transact?msg=cM76WAbgJzZKP8PrZ) 'Asha' means 'Hope' in most Indian languages.

RealDeanZhao (Wed, 08 May 2019 03:22:29 GMT):
Has joined the channel.

arsulegai (Wed, 08 May 2019 06:41:40 GMT):
Has joined the channel.

mastersingh24 (Wed, 08 May 2019 08:06:54 GMT):
Has joined the channel.

mastersingh24 (Wed, 08 May 2019 08:33:19 GMT):
I like the "engine" theme ... so just because, I'll throw out two idea: Hyperledger Dynamo Hyperledger Turbine ;)

mastersingh24 (Wed, 08 May 2019 08:33:19 GMT):
I like the "engine" theme ... so just because, I'll toss two into the mix: Hyperledger Dynamo Hyperledger Turbine ;)

agunde (Wed, 08 May 2019 12:59:27 GMT):
Has joined the channel.

arsulegai (Wed, 08 May 2019 14:46:51 GMT):
More simpler "Hyperledger Bind"

arsulegai (Wed, 08 May 2019 14:50:37 GMT):
Another - "Hyperledger Evolve"

kodonnel (Wed, 08 May 2019 16:49:31 GMT):
Has joined the channel.

achenette (Wed, 08 May 2019 18:30:25 GMT):
Has joined the channel.

DavidAEdwards (Thu, 09 May 2019 07:18:57 GMT):
Has joined the channel.

cbf (Thu, 09 May 2019 14:17:04 GMT):
Has joined the channel.

cbf (Thu, 09 May 2019 14:26:41 GMT):
Hyperledger käntrakt

cbf (Thu, 09 May 2019 14:27:16 GMT):
(phonetically)

amundson (Thu, 09 May 2019 17:43:10 GMT):
my thoughts on a few of the suggestions:

amundson (Thu, 09 May 2019 17:43:12 GMT):
Hyperledger Delta - Great from the perspective of state transition functions producing receipts. However, existing database project exists - https://github.com/delta-io/delta. Hyperledger Transmission - Meh Hyperledger Torque - Not bad, but there is an existing open source project related to queueing - https://github.com/adaptivecomputing/torque Hyperledger Shift - Too close to OpenShift Hyperledger Turing - There is a programming language called 'Turing'. Hyperledger Edge - Nice, but network layer connotations and 'Microsoft Edge'

amundson (Thu, 09 May 2019 17:50:29 GMT):
Hyperledger Cornholio - too corny Hyperledger käntrakt - non-ASCII characters Hyperledger Bind - Too close to the DNS server project - https://www.isc.org/downloads/bind/ Hyperledger Dynamo - Another project - https://dynamobim.org/ Hyperledger Morpheus - Associations with https://en.wikipedia.org/wiki/Morpheus_(software)

amundson (Thu, 09 May 2019 17:55:00 GMT):
Hyperledger Dali - Another open source project - https://developer.nvidia.com/DALI Hyperledger Rothko - small open source effort using the name - https://github.com/Haacked/Rothko Hyperledger Turbine - existing (defunct?) crate - https://crates.io/crates/turbine

amundson (Thu, 09 May 2019 17:55:31 GMT):
these didn't have any substantial disqualifications I could find:

amundson (Thu, 09 May 2019 17:55:40 GMT):
Hyperledger Transact Hyperledger Mill Hyperledger Asha Hypereldger Evolve

arsulegai (Thu, 09 May 2019 18:07:34 GMT):
Hyperledger Transact sounds good Or inspired by @cbf idea, "Hyperledger Tract" is another name I can think of

arsulegai (Thu, 09 May 2019 18:08:54 GMT):
:neutral_face: there's already a open source project by that name https://github.com/snipsco/tract

amundson (Thu, 09 May 2019 18:25:44 GMT):
@danoprey is opposed to "Hyperledger Transact" and is our rep from HL Marketing

amundson (Thu, 09 May 2019 18:26:43 GMT):
I'll post these one per-line so we can get some opinions on them:

amundson (Thu, 09 May 2019 18:26:50 GMT):
Hyperledger Transact

amundson (Thu, 09 May 2019 18:26:56 GMT):
Hyperledger Mill

amundson (Thu, 09 May 2019 18:27:02 GMT):
Hyperledger Asha

amundson (Thu, 09 May 2019 18:27:07 GMT):
Hypereldger Evolve

eloafran (Thu, 09 May 2019 18:29:26 GMT):
Has joined the channel.

satelander (Thu, 09 May 2019 18:30:44 GMT):
Has joined the channel.

dplumb (Thu, 09 May 2019 19:02:29 GMT):
Has joined the channel.

cecchi (Thu, 09 May 2019 19:10:23 GMT):
wait just so i'm clear is transact good or not good?

cecchi (Thu, 09 May 2019 19:10:38 GMT):
also how many votes do we get?

achenette (Thu, 09 May 2019 19:12:29 GMT):
How many different emojis can be interpreted as a vote? That's how many.

achenette (Thu, 09 May 2019 19:12:29 GMT):
How many different emojis can be interpreted as a vote? That's how many. :-)

amundson (Thu, 09 May 2019 19:18:05 GMT):
@cecchi vote on as many things as you want

Dan (Fri, 10 May 2019 15:01:52 GMT):
Has joined the channel.

Dan (Fri, 10 May 2019 15:01:53 GMT):
Hyperledger Execution <-- just think of the logo possibilities!

Dan (Fri, 10 May 2019 15:06:50 GMT):
_(there will be consequences for anyone who votes against this ^ name)_

mastersingh24 (Sat, 11 May 2019 09:09:13 GMT):
Hmm ... I feel a bit bullied here LOL

Dan (Sat, 11 May 2019 14:20:45 GMT):
They could be good consequences. I wouldn't suggest finding out tho.

amundson (Mon, 13 May 2019 15:30:58 GMT):
@danoprey "Hyperledger Transact" seems universally popular compared to the other names. How strong is HL marketing's position against it? Could we proceed with it?

danoprey (Mon, 13 May 2019 16:15:29 GMT):
@amundson would like to get @bbehlendorf 's thoughts on this too. Have send a follow up email to the marketing leadership

bbehlendorf (Mon, 13 May 2019 16:15:30 GMT):
Has joined the channel.

danoprey (Mon, 13 May 2019 16:18:15 GMT):
personally, I still feel this is a less than ideal name from a marketing perspective as it is not unique, gives little sense of what the project does, will be hard to defend if we ever wanted to register as an individual trademark, and will do poorly on SEO. I'd really encourage the team to come up with something they love which has a better back story too it and has more charm. Aries, Burrow, Sawtooth, Ursa are good examples of these.

mattp (Mon, 13 May 2019 16:59:29 GMT):
Has joined the channel.

danoprey (Mon, 13 May 2019 17:23:23 GMT):
However, it is pretty unanimous to go for transact with a pretty big dropoff. So if that's what the community want to go for then no objection to proceeding with Hyperledger Transact

cecchi (Tue, 14 May 2019 01:29:50 GMT):
i voted for Mill and Transact and abstained with my additional unlimited votes due to outrage over lack of Cornholio option

cecchi (Tue, 14 May 2019 01:30:21 GMT):
and to be clear that outrage is deep and legit like the mighty mississip

mastersingh24 (Tue, 14 May 2019 08:27:10 GMT):
@cecchi - I think you missed your calling ... I feel some mad rhymes coming in your future

amundson (Tue, 14 May 2019 20:06:21 GMT):
Ok, I think we have a couple choices - 1) move forward with 'Hyperledger Transact'; or 2) take another week and try and come up with more options. @mastersingh24 @Dan @cecchi @agunde @jsmitchell @pschwarz - As project sponsors, we should all agree on how to proceed. While I acknowledge some of the points made against it, I think 'Hyperledger Transact' will be a solid name for a library project. I suggest we move forward with 'Hyperledger Transact'. Please vote.

amundson (Tue, 14 May 2019 20:06:26 GMT):
1) move forward

amundson (Tue, 14 May 2019 20:06:28 GMT):
2) delay

amundson (Tue, 14 May 2019 20:09:21 GMT):
@cecchi please only vote for one this time :)

Dan (Tue, 14 May 2019 20:44:26 GMT):
3) Execute

Dan (Tue, 14 May 2019 20:44:41 GMT):
j/k

rjones (Tue, 14 May 2019 20:45:54 GMT):
4) ABUSE _FORCE MAJEURE_ AND CALL IT CORNHOLIO

Dan (Tue, 14 May 2019 20:47:48 GMT):
I think you mean "The Great ..."

rjones (Tue, 14 May 2019 20:48:11 GMT):
AS YOU WISH

Dan (Tue, 14 May 2019 20:48:30 GMT):
Hyperledger TGC

rjones (Tue, 14 May 2019 20:48:39 GMT):
TOTALLY NOT A CHANNEL ABOUT BEAVIS AND BUTTHEAD

Dan (Tue, 14 May 2019 20:48:46 GMT):
lol

rjones (Tue, 14 May 2019 20:49:38 GMT):
Dan

danoprey (Tue, 14 May 2019 23:00:41 GMT):
Don't make me take "Hyperledger the Great Cornholio" to a marketing committee vote... I'll do it

amundson (Tue, 14 May 2019 23:10:44 GMT):
That name is reserved for @Dan’s next project.

pschwarz (Wed, 15 May 2019 15:01:45 GMT):
Looks like full votes on 1)

amundson (Wed, 15 May 2019 16:32:58 GMT):
@danoprey the sponsors want to move forward with the name Hyperledger Transact

amundson (Wed, 15 May 2019 17:53:39 GMT):
@rjones can you create a TRANSACT board in JIRA with the same perms as grid?

rjones (Wed, 15 May 2019 18:12:01 GMT):
@amundson done

rjones (Wed, 15 May 2019 18:12:52 GMT):
@amundson I set @Dan as the project lead so he can get some spam :)

amundson (Wed, 15 May 2019 18:13:01 GMT):
LOL

amundson (Wed, 15 May 2019 18:16:16 GMT):
we have the "transact" crate now - https://crates.io/crates/transact

amundson (Wed, 15 May 2019 18:19:22 GMT):
@rjones what's the next step for the rest of the infrastructure (git repo, mailing list, etc.) - should I send an email to community architects, or will it be put in motion automagically?

rjones (Wed, 15 May 2019 18:26:05 GMT):
@amundson send email to c-a please

rjones (Wed, 15 May 2019 18:27:45 GMT):
@amundson we will work through https://wiki.hyperledger.org/display/tools/Transact

amundson (Wed, 15 May 2019 18:33:55 GMT):
awesome

danoprey (Wed, 15 May 2019 22:09:42 GMT):
Any thoughts on an icon representing "Transact"?

amundson (Thu, 16 May 2019 14:23:46 GMT):
not yet, but I think it should be pink

amundson (Thu, 16 May 2019 14:23:56 GMT):
did anyone notice Aries and Ursa have the same logo?

rjones (Thu, 16 May 2019 14:50:34 GMT):
Aries logo is changing

jsmitchell (Thu, 16 May 2019 15:23:33 GMT):
It got announced at Consensus with a temporary logo?

jsmitchell (Thu, 16 May 2019 15:23:39 GMT):
weird

amundson (Thu, 16 May 2019 15:33:59 GMT):
now that the naming discussion is done and we are moving along...

amundson (Thu, 16 May 2019 15:40:40 GMT):
we have a bunch of in-progress work going on currently: 1) finishing the serial scheduler (multiple txn per batch); 2) writing the parallel scheduler in Rust; 3) putting together an RFC for a "command" transaction family; 4) design related to documentation (what we need in the docs); 5) reworking the context manager's threading approach; 6) adding an Xo execution test (this is a demo of sawtooth-compatibility); 7) work towards a ZMQ execution adapter (for sawtooth compatibility); 8) work towards a SSL (and raw TCP) execution adapter

amundson (Thu, 16 May 2019 15:40:40 GMT):
we have a bunch of in-progress work going on currently: 1) finishing the serial scheduler (multiple txn per batch); 2) writing the parallel scheduler in Rust; 3) putting together an RFC for a "command" transaction family; 4) design related to documentation (what we need in the docs); 5) reworking the context manager's threading approach; 6) adding an Xo execution test (this is a demo of sawtooth-compatibility); 7) work towards a ZMQ execution adapter (for sawtooth compatibility); 8 ) work towards a SSL (and raw TCP) execution adapter

amundson (Thu, 16 May 2019 15:41:50 GMT):
we should get this and more into JIRA soon...

amundson (Thu, 16 May 2019 15:52:39 GMT):
@mastersingh24 where should I look to understand the format of read/write sets? (like, the encoding, if that makes sense)

rjones (Thu, 16 May 2019 16:19:45 GMT):
It hit trademark issues

manojgop (Mon, 20 May 2019 06:34:35 GMT):
Has joined the channel.

amundson (Tue, 21 May 2019 14:42:44 GMT):
So, I propose we setup three git repos: "transact", "transact-rfcs", and "transact-contrib". The "transact" repo will contain the library. The "transact-rfcs" repo will contain RFCs (similar to sawtooth, grid, ursa, etc.). The "transact-contrib" repo will contain examples or early-stage work/integrations that aren't yet officially supported.

VishalBatra (Tue, 21 May 2019 14:56:54 GMT):
Has joined the channel.

Dan (Tue, 21 May 2019 14:59:15 GMT):
docs will go in "transact" ?

amundson (Tue, 21 May 2019 15:13:37 GMT):
currently, I'm poposing the only docs we have are rust api docs. no sphinx-doc, no website.

amundson (Tue, 21 May 2019 15:14:39 GMT):
(so yes, in the .rs files in "transact" repo)

artem.frantsiian (Wed, 22 May 2019 06:40:43 GMT):
Has joined the channel.

knagware9 (Wed, 22 May 2019 11:00:37 GMT):
Has joined the channel.

rjones (Thu, 23 May 2019 01:52:20 GMT):
https://lists.hyperledger.org/g/transact

rjones (Thu, 23 May 2019 01:54:05 GMT):
https://wiki.hyperledger.org/display/TRAN/Transact

rjones (Thu, 23 May 2019 01:54:05 GMT):
https://wiki.hyperledger.org/display/transact

Dan (Thu, 30 May 2019 13:34:56 GMT):
can i get `owner` (here so I can update the topic ;) )

Dan (Thu, 30 May 2019 13:34:56 GMT):
can i get `owner` (here so I can update the topic ;) )?

rjones (Thu, 30 May 2019 17:38:59 GMT):

rjones (Thu, 30 May 2019 17:39:28 GMT):
Dan

rjones (Thu, 30 May 2019 17:39:31 GMT):
Dan

rjones (Thu, 30 May 2019 17:40:16 GMT):
I'm pretty sure @amundson has the power to grant ownership. I'm not sure

rjones (Thu, 30 May 2019 17:41:10 GMT):
I think it's like IRC +o and +mM

amundson (Thu, 30 May 2019 17:41:19 GMT):
I was trying to figure out the rocketchat interface to do that but couldn't

amundson (Thu, 30 May 2019 17:41:50 GMT):
oh, that had not occurred to me - was looking for a menu

rjones (Thu, 30 May 2019 17:42:20 GMT):
nothing is easy (╯°□°）╯︵ ┻━┻

rjones (Thu, 30 May 2019 17:43:12 GMT):
click the three person icon up top, pick a user, you should have buttons to "set as owner" and "set as moderator"

amundson (Thu, 30 May 2019 17:48:15 GMT):
agunde

amundson (Thu, 30 May 2019 17:48:44 GMT):
mastersingh24

rjones (Thu, 30 May 2019 17:53:53 GMT):
so yes, owners can grant ownership, awesome.

amundson (Thu, 30 May 2019 17:54:35 GMT):
Dan

amundson (Thu, 30 May 2019 17:54:41 GMT):
oh, this is perfect now

amundson (Thu, 30 May 2019 17:54:46 GMT):
jk

amundson (Thu, 30 May 2019 17:54:51 GMT):
Dan

Dan (Thu, 30 May 2019 17:54:52 GMT):
:O

Dan (Thu, 30 May 2019 17:57:55 GMT):
cecchi

Dan (Thu, 30 May 2019 17:58:53 GMT):
jsmitchell

Dan (Thu, 30 May 2019 17:59:27 GMT):
pschwarz

Dan (Thu, 30 May 2019 18:00:05 GMT):
@JonathanLevi Are you in this room?

JonathanLevi (Thu, 30 May 2019 18:00:08 GMT):
Has joined the channel.

Dan (Thu, 30 May 2019 18:00:28 GMT):
JonathanLevi

Dan (Thu, 30 May 2019 18:00:34 GMT):
you are now

Dan (Thu, 30 May 2019 18:00:48 GMT):
I believe that's all the sponsors now.

jsmitchell (Thu, 30 May 2019 18:10:31 GMT):
test

jsmitchell (Thu, 30 May 2019 18:10:48 GMT):
owner test

mfford (Fri, 31 May 2019 15:16:13 GMT):
Reminder that our first Hyperledger Transact Contributor Meeting will be held Monday, June 3rd at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar located here: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings Here is the link to the agenda for this meeting: https://wiki.hyperledger.org/pages/viewpage.action?pageId=13862603

mfford (Mon, 03 Jun 2019 13:44:38 GMT):
Reminder that our first Hyperledger Transact Contributor Meeting will be held today, June 3rd at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar located here: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings Here is the link to the agenda for this meeting: https://wiki.hyperledger.org/pages/viewpage.action?pageId=13862603

mfford (Mon, 03 Jun 2019 16:52:16 GMT):
Notes for the Hyperledger Transact Contributor Meeting held today at 10am CDT: https://wiki.hyperledger.org/pages/viewpage.action?pageId=13862773

Dan (Mon, 03 Jun 2019 17:22:50 GMT):
thanks @mfford

nhrishi (Thu, 06 Jun 2019 17:01:59 GMT):
Has joined the channel.

arsulegai (Wed, 12 Jun 2019 12:10:36 GMT):
I've a question on Transact, state is made part of it and Blockchain implementation would use the state implementation provided by it. Does it mean in future, there's plan for making Transact pluggable interface for underlying Blockchain frameworks? I am unable to realise if there's other specific reason behind it.

Dan (Wed, 12 Jun 2019 12:14:08 GMT):
The idea is that Fabric, Sawtooth, etc would use transact as a library. The choice of persistence is up to each blockchain, and transact is going to provide interfaces compatible with those choices.

pschwarz (Wed, 12 Jun 2019 14:21:01 GMT):
There is a trait for State, where it operates on some state id (for example, in Sawtooth, this would be the merkle state root hash), and key/value pairs. Transact provides an implementation using a Merkle trie, backed by LMDB or an in-memory btree database. This may be optional, based on a Rust feature, but we're still considering what things are there by default and what are optional.

arsulegai (Wed, 12 Jun 2019 14:58:06 GMT):
Thanks that clarifies

amundson (Thu, 13 Jun 2019 17:05:09 GMT):
Some potential logos:

amundson (Thu, 13 Jun 2019 17:05:20 GMT):

Clipboard - June 13, 2019 12:05 PM

amundson (Thu, 13 Jun 2019 17:05:35 GMT):

Clipboard - June 13, 2019 12:05 PM

amundson (Thu, 13 Jun 2019 17:05:51 GMT):

Clipboard - June 13, 2019 12:05 PM

amundson (Thu, 13 Jun 2019 17:06:08 GMT):
Thoughts?

jsmitchell (Thu, 13 Jun 2019 17:06:18 GMT):
i think the prism is problematic for a bunch of reasons

jsmitchell (Thu, 13 Jun 2019 17:06:42 GMT):
i like both of the others, but I like the 'beaker'/delta thing a bit more

rjones (Thu, 13 Jun 2019 17:06:57 GMT):
+1 on the beaker

jsmitchell (Thu, 13 Jun 2019 17:07:12 GMT):
i preferred the slightly less complex version of the beaker thingy (the one with fewer lines)

amundson (Thu, 13 Jun 2019 17:08:10 GMT):

Clipboard - June 13, 2019 12:08 PM

amundson (Thu, 13 Jun 2019 17:10:06 GMT):
Of these, I probably do like the simple beaker the best

rjones (Thu, 13 Jun 2019 17:11:34 GMT):
think of a sticker with only the glyph on it - needs to be distinct enough for a sticker, easy to put on a hat, etc. We have some logos right now that are not easy to use.

rjones (Thu, 13 Jun 2019 17:18:15 GMT):
for instance: https://www.hyperledger.org/wp-content/uploads/2016/09/logo_hl_new.png

benoit.razet (Fri, 14 Jun 2019 14:54:47 GMT):
Has joined the channel.

MicBowman (Wed, 19 Jun 2019 16:12:09 GMT):
Has joined the channel.

amundson (Thu, 20 Jun 2019 19:43:22 GMT):
^ shall we consider that an official vote on the logo?

pschwarz (Thu, 20 Jun 2019 19:44:07 GMT):
:thumbsup:

Dan (Thu, 20 Jun 2019 20:02:24 GMT):

Clipboard - June 20, 2019 3:02 PM

Dan (Thu, 20 Jun 2019 20:02:34 GMT):
I'm still in favor of one of the original concepts

Dan (Thu, 20 Jun 2019 20:02:34 GMT):
I'm still in favor of one of the original concepts ^

amundson (Thu, 20 Jun 2019 20:22:47 GMT):
That would be a good "Hyperledger Dan" logo

huxiangdong (Fri, 21 Jun 2019 09:19:46 GMT):
Has joined the channel.

Dan (Fri, 21 Jun 2019 16:04:19 GMT):
Pfff if you can't agree to my logo preference, I don't know if I can collaborate with any of you. :rage:

Dan (Fri, 21 Jun 2019 16:04:19 GMT):
Pfff if you can't agree to my logo preference, I don't know if I can collaborate with any of you.

Dan (Fri, 21 Jun 2019 16:06:36 GMT):
`Hyperledger Dan` will be way better than `Hyperledger Transact`. It's going to be 100% Pascal.

jsmitchell (Fri, 21 Jun 2019 16:18:30 GMT):
Big talk. Without looking it up, what’s the difference between a function and a procedure?

Dan (Fri, 21 Jun 2019 16:37:54 GMT):
I think one returns a value. But that's not important right now. All that's important is everyone agreeing with my preferences.

amundson (Thu, 27 Jun 2019 14:10:21 GMT):
the announcement blog entry is up - https://www.hyperledger.org/blog/2019/06/27/introducing-hyperledger-transact

nicolapaoli (Thu, 27 Jun 2019 14:33:58 GMT):
Has joined the channel.

mbennett (Thu, 27 Jun 2019 14:43:27 GMT):
Has joined the channel.

mbennett (Thu, 27 Jun 2019 14:43:28 GMT):
Shared on LI, Facebook, Twitter and the Hyperledger mailing lists!

mfford (Sat, 29 Jun 2019 11:36:02 GMT):
Reminder that the Hyperledger Transact Contributor Meeting will be held Monday, July 1st at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar. We are finalizing the agenda for this meeting. If you have a topic that you would like to facilitate, please add it to the agenda. Looking forward to seeing everyone there! -Mark Ford

mfford (Sat, 29 Jun 2019 11:36:02 GMT):
Reminder that the Hyperledger Transact Contributor Meeting will be held Monday, July 1st at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings We are finalizing the agenda for this meeting. If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=16318947

jadhavajay (Sat, 29 Jun 2019 18:09:17 GMT):
Has joined the channel.

Dan (Mon, 01 Jul 2019 15:02:20 GMT):
https://zoom.us/j/761947873

walmon (Mon, 01 Jul 2019 15:43:34 GMT):
Has joined the channel.

mfford (Mon, 01 Jul 2019 16:50:21 GMT):
Notes from the Hyperledger Transact Contributor Meeting this morning: https://wiki.hyperledger.org/pages/viewpage.action?pageId=16320010

Khaled.MH (Tue, 02 Jul 2019 08:49:27 GMT):
Has joined the channel.

MHBauer (Tue, 02 Jul 2019 20:40:22 GMT):
Has joined the channel.

fz (Fri, 05 Jul 2019 03:16:58 GMT):
Has joined the channel.

HLFPOC (Mon, 08 Jul 2019 08:21:45 GMT):
Has joined the channel.

rjones (Mon, 08 Jul 2019 17:58:11 GMT):
Has left the channel.

pankajgoyal (Wed, 10 Jul 2019 09:47:24 GMT):
Has joined the channel.

bur (Thu, 11 Jul 2019 12:51:21 GMT):
Has joined the channel.

ra_w (Mon, 15 Jul 2019 19:31:32 GMT):
Has joined the channel.

swetha (Thu, 18 Jul 2019 01:13:48 GMT):
Has joined the channel.

mwklein (Thu, 25 Jul 2019 14:51:43 GMT):
Has joined the channel.

mfford (Thu, 01 Aug 2019 17:09:42 GMT):
Reminder that our next Hyperledger Transact Contributor Meeting will be held Monday, August 5th at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings You can also join the zoom link here: https://zoom.us/j/761947873 We are looking for additional agenda items for this meeting. If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=16323258

huxd (Fri, 02 Aug 2019 01:34:31 GMT):
Has joined the channel.

jamesbarry (Fri, 02 Aug 2019 15:09:39 GMT):
Has joined the channel.

amundson (Fri, 02 Aug 2019 16:00:24 GMT):
As we start working on Go bindings for transact and Go transaction/batch building code, we will need a place to put it. I propose we place it in a new repository called "transact-sdk-go".

amundson (Fri, 02 Aug 2019 16:02:08 GMT):
And that, moving forward, would translate into a general transact-sdk-[lang] pattern for any new langauge binding and/or transaction/batch building code we add

wkatsak (Fri, 02 Aug 2019 16:27:21 GMT):
Has joined the channel.

mfford (Mon, 05 Aug 2019 12:26:25 GMT):
Reminder that the Hyperledger Transact Contributor Meeting is today at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings You can also join the zoom link here: https://zoom.us/j/761947873 It's not too late to add an agenda topic for this meeting. If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=16323258

Dan (Mon, 05 Aug 2019 15:02:36 GMT):
@mastersingh24 FYI if you are online ^

Dan (Mon, 05 Aug 2019 15:16:21 GMT):
you were too slow. All I know is there were what sounded like police sirens and then @mfford seemed to think he needed to end the call right away.

mfford (Mon, 05 Aug 2019 15:17:23 GMT):
I'm on the run. They will never catch me. I always have a plan.

mfford (Mon, 05 Aug 2019 20:27:40 GMT):
Notes from today's Hyperledger Transact Contributor Meeting: https://wiki.hyperledger.org/pages/viewpage.action?pageId=13862597

mfford (Mon, 05 Aug 2019 20:27:40 GMT):
Notes from today's Hyperledger Transact Contributor Meeting: https://wiki.hyperledger.org/pages/viewpage.action?pageId=16323805

jeffgarratt (Tue, 06 Aug 2019 15:41:43 GMT):
Has joined the channel.

rberg2 (Tue, 06 Aug 2019 20:08:19 GMT):
Has joined the channel.

rberg2 (Tue, 06 Aug 2019 20:08:58 GMT):
Hello all, transact 0.1.5 has been released to crates.io

richzhao (Fri, 09 Aug 2019 11:51:13 GMT):
Has joined the channel.

rbuysse (Wed, 21 Aug 2019 15:29:31 GMT):
@mastersingh24 Can you take a peek at this pull request when you have a sec? https://github.com/hyperledger/transact-rfcs/pull/3

RedKnight13 (Thu, 22 Aug 2019 08:46:42 GMT):
Has joined the channel.

silasdavis (Thu, 22 Aug 2019 15:03:14 GMT):
Has joined the channel.

silasdavis (Thu, 22 Aug 2019 15:03:15 GMT):
Hi Transact... I was having a look at the transact code with a view to seeing what it would take to expose a sabre-compatible WASM backend in Burrow

silasdavis (Thu, 22 Aug 2019 15:03:18 GMT):
any pointers?

amundson (Thu, 22 Aug 2019 15:08:58 GMT):
@silasdavis so, we have started on a 0mq network transport for transact that will allow you to run seth

amundson (Thu, 22 Aug 2019 15:09:26 GMT):
oh, opposite question :)

silasdavis (Thu, 22 Aug 2019 15:09:32 GMT):
ha I think so

silasdavis (Thu, 22 Aug 2019 15:09:44 GMT):
what I am thinking is - can I compile transact and deploy it as a contract on Burrow

silasdavis (Thu, 22 Aug 2019 15:10:02 GMT):
thoughts are vague

amundson (Thu, 22 Aug 2019 15:10:03 GMT):
ok, so the barrier initially is going to be Go->Rust; we created a Go repo but haven't started on the bindings yet

silasdavis (Thu, 22 Aug 2019 15:10:30 GMT):
does transact run sabre, or does transact run on sabre

silasdavis (Thu, 22 Aug 2019 15:10:30 GMT):
does transact run sabre, or does transact run on sabre?

silasdavis (Thu, 22 Aug 2019 15:10:37 GMT):
that might be mistunderstanding number 0

silasdavis (Thu, 22 Aug 2019 15:10:37 GMT):
that might be misunderstanding number 0

amundson (Thu, 22 Aug 2019 15:11:24 GMT):
think of transact as an API to run transactions through various smart contracts engines, like sabre and seth

amundson (Thu, 22 Aug 2019 15:11:47 GMT):
(though, it is also the implementation, but from a user perspective, the API is the relevant bit)

silasdavis (Thu, 22 Aug 2019 15:14:33 GMT):
So say I have a grid smart contract will that rely on Transact (and transitively sabre, say) or is it more directly dependent on sabre?

silasdavis (Thu, 22 Aug 2019 15:15:17 GMT):
It's the smart contracts/objects that work with transact/sabre that I am interested in running directly on Burrow, compiling what I need from rust to WASM

silasdavis (Thu, 22 Aug 2019 15:16:13 GMT):
(also I'll take the time to actually run transact which might make more of this clear...)

amundson (Thu, 22 Aug 2019 15:16:23 GMT):
so, for example: say you have some initial state S0 (maybe represented as a merkle radix tree or maybe a key/value store). you can create a transact scheduler and feed transactions into it. you then give part of the scheduler to transact's executor, which will use sabre/seth to run the contracts in the context of S0. the results flow back to the application(DLT) in the form of transaction receipts, which are the state transitions necessary. the application(DLT) takes the results and uses them to update state to create a new state S1

amundson (Thu, 22 Aug 2019 15:20:05 GMT):
Grid smart contracts are compiled against the Sabre SDK. That SDK is currently API-compatible with Sawtooth's transaction processor API. So there is some precedent for multiple compile targets.

amundson (Thu, 22 Aug 2019 15:20:54 GMT):
When compiled in "wasm" mode, we are compiling against a FFI (C) interface to do get/set state, etc.

amundson (Thu, 22 Aug 2019 15:21:45 GMT):
and then sabre implements the other side as well (the container) that marshalls those calls to sawtooth or transact's state (depending the context)

silasdavis (Thu, 22 Aug 2019 15:21:56 GMT):
okay thanks, it sounds like for this particular idea I am interested in exposing state to a sabre contract

silasdavis (Thu, 22 Aug 2019 15:22:14 GMT):
I noticed the c dependency - so are you just using the C FFI as a calling convention here

silasdavis (Thu, 22 Aug 2019 15:22:40 GMT):
you are not calling C code, or rust code via a C binding or anything?

amundson (Thu, 22 Aug 2019 15:24:07 GMT):
right, for the calling convention. basically, it's the interface that allows the sandboxed wasm code to call outside the sandbox. the code is all rust.

amundson (Thu, 22 Aug 2019 15:25:43 GMT):
we are using the parity wasmi interpreter, so the code outside of the interpreter is basically wasmi->transact(or sawtooth) code

amundson (Thu, 22 Aug 2019 15:26:22 GMT):
(I keep referring to sawtooth only because Sabre can be compiled against transact or sawtooth.)

silasdavis (Thu, 22 Aug 2019 15:27:40 GMT):
ah okay, so sounds like there isn't a direct extern wasm -- https://github.com/rustwasm/team/issues/29

silasdavis (Thu, 22 Aug 2019 15:27:49 GMT):
so I guess that's why the parity wasm works that way

silasdavis (Thu, 22 Aug 2019 15:28:09 GMT):
we are using https://github.com/perlin-network/life FWIW

amundson (Thu, 22 Aug 2019 15:29:20 GMT):
so, for example, one thing you could do integration-wise is implement a new State definition (it is a trait in Transact) which is backed by something other than the merkle tree implementation, and then use sabre to run the grid smart contracts, and then take the receipts and apply them to your version of state. because your state implementation can have whatever rules for accessing state you want, you have a lot of control.

amundson (Thu, 22 Aug 2019 15:31:26 GMT):
I wouldn't necessarily suggest replacing Sabre's implementation. we can always modify it if needed, and likely you just want to figure out the challenging state-mapping piece first anyway.

amundson (Thu, 22 Aug 2019 15:33:12 GMT):
currently Grid is assuming the merkle-radix addresses when creating keys (as do all Sabre contracts currently), and the question becomes, what does that mean if what you want to use a different state design.

amundson (Thu, 22 Aug 2019 15:34:53 GMT):
I would suggest starting with sawtooth xo if you want to get something working as a proof of concept. it is easy to deploy to wasm and then works like all the grid smart contracts but has easier business logic to reason about.

amundson (Thu, 22 Aug 2019 15:35:50 GMT):
(you can deploy sawtooth xo into sabre and not use the rest of sawtooth)

silasdavis (Thu, 22 Aug 2019 15:36:11 GMT):
to explain the constraint I'm trying to thing through - I'd like to be able to run some of these contracts without introducing another process - run it all in Burrow - ideally in pure go...

silasdavis (Thu, 22 Aug 2019 15:36:17 GMT):
I'm not sure how feasible that is

amundson (Thu, 22 Aug 2019 15:38:43 GMT):
well, Transact is written in Rust. But the ideas is that we create a good Go wrapper so that from the DLT perspective (burrow, fabric), Transact looks like a Go library (which just happens to be implemented in Rust lower down the stack). Running all in the same process should be fine--today, you compile sabre directly in so it's not a separate process.

silasdavis (Thu, 22 Aug 2019 15:39:41 GMT):
yeah but then we become CGO not Go

silasdavis (Thu, 22 Aug 2019 15:40:04 GMT):
not the end of the world for sure (we are CGO if you compile us with sqlite support for Vent so there is precedent)

amundson (Thu, 22 Aug 2019 15:40:37 GMT):
sure, same basic idea as Ursa

silasdavis (Thu, 22 Aug 2019 15:41:03 GMT):
We have machinery in Burrow that is a bit like transact, but it sounds like what you are advancing is the point of transact is to reuse that actual code, not implement something parallel

silasdavis (Thu, 22 Aug 2019 15:41:44 GMT):
but i was wondering if doing that would still provide us something worthwhile in terms of interop lower down the stack with sabre

silasdavis (Thu, 22 Aug 2019 15:41:59 GMT):
but perhaps once you take that out it really is just get/set FFI in C

silasdavis (Thu, 22 Aug 2019 15:41:59 GMT):
but perhaps once you take that out it really is just get/set C FFI

silasdavis (Thu, 22 Aug 2019 15:42:12 GMT):
which isn't much of an interop

silasdavis (Thu, 22 Aug 2019 15:42:30 GMT):
so maybe compiling in transact as an option that writes to our merkle state is the more interesting thing to do

amundson (Thu, 22 Aug 2019 15:47:35 GMT):
yes, the idea of transact is a library, not a specification. we could do a sabre-related spec. but I see more collaboration happening with library sharing and using transact. in part, because then you not only get sabre support, but every smart contract engine that ever gets implemented is likely to work (daml for free, for example, and chaincode if we add support for it).

amundson (Thu, 22 Aug 2019 15:53:20 GMT):
if pure-go is important, we can make transact another system process (which violates the other constraint you mentioned), in which case, it just provides a service that can be used. that approach is why I have referred to transact as a "library or component" because it depends on whether you encapsulate it in a process. but if we want to go down that path, we will want to build a transact daemon 'transactd' process that can optionally be used (approach up to the DLT).

amundson (Thu, 22 Aug 2019 15:55:13 GMT):
what are the disadvantages of cgo?

silasdavis (Thu, 22 Aug 2019 16:00:31 GMT):
It's not ruinous, but pure-go is enough of a positive that we try and hang on to it for our standard builds, see: https://dave.cheney.net/2016/01/18/cgo-is-not-go

silasdavis (Thu, 22 Aug 2019 16:01:13 GMT):
https://about.sourcegraph.com/go/gophercon-2018-adventures-in-cgo-performance

silasdavis (Thu, 22 Aug 2019 16:01:51 GMT):
It also breaks Go's pprof pretty badly which I use a lot

silasdavis (Thu, 22 Aug 2019 16:02:09 GMT):
See: https://rakyll.org/pprof-ui/

silasdavis (Thu, 22 Aug 2019 16:02:42 GMT):
If we wanted to go nuts I suppose I could compile transact to WASM...

amundson (Thu, 22 Aug 2019 16:25:15 GMT):
compiling transact to wasm isn't going to work, because transact is heavily threaded

amundson (Thu, 22 Aug 2019 16:25:42 GMT):
I assume the dependency list also wouldn't compile with a wasm target

DennisM330 (Fri, 23 Aug 2019 11:43:58 GMT):
Has joined the channel.

rjones (Mon, 26 Aug 2019 21:36:29 GMT):
Has joined the channel.

rjones (Mon, 26 Aug 2019 21:37:00 GMT):
Hi - I broadly updated the CODEOWNERS files in the four Transact repos to reflect the actual permissions. Please review the changes carefully.

rjones (Mon, 26 Aug 2019 21:40:28 GMT):
https://github.com/hyperledger/transact-sdk-go/pull/2 https://github.com/hyperledger/transact-contrib/pull/3 https://github.com/hyperledger/transact-rfcs/pull/4 https://github.com/hyperledger/transact/pull/13

AlexanderZhovnuvaty (Tue, 27 Aug 2019 10:08:05 GMT):
Has joined the channel.

AlexanderZhovnuvaty (Tue, 27 Aug 2019 10:08:06 GMT):
hi guys! Need advise on 2 questions: 1) Does this framework support ERCXXX smart contracts? 2) Can it be used as gateway between Fabric and Sawooth networks? I have a task where two communities (one work with Fabric, another with Sawtooth) should have subset of common data handled by certain rules. Assume it should be some kind of smart contract which can be used between multiple networks. Hope Transact can cover such requirement. Thanks in advance

amundson (Wed, 28 Aug 2019 14:19:55 GMT):
@rjones I left comments on the https://github.com/hyperledger/transact/pull/13 one

amundson (Wed, 28 Aug 2019 14:30:25 GMT):
@AlexanderZhovnuvaty 1) after we add a 0mq network execution adapter, it will be possible to use transact to run Sawtooth Seth, which in turn uses Burrow

amundson (Wed, 28 Aug 2019 14:36:33 GMT):
2) neither Sawtooth or Fabric support Transact yet, it is in-progress; Transact can be used to execute Sawtooth smart contracts today if they are written in Rust, but the use-case would be running them in a separate process (like, if you were implementing another DLT or a tool); when Sawtooth and Fabric do support Transact, it will be possible to write a smart contract and then deploy it to either network (for example, deploying Sabre wasm smart contracts); if what you need to to coordinate between multiple networks, you may want an oracle process instead

AlexanderZhovnuvaty (Wed, 28 Aug 2019 15:25:31 GMT):
[ ](https://chat.hyperledger.org/channel/transact?msg=9YwtvqE22hBndA4qc) Thanks! Pls point me to some documentation about what does "you may want an oracle process instead" mean?

swetha (Thu, 29 Aug 2019 17:26:14 GMT):
Hi! I am looking to get more familiar with Transact and possibly start contributing. I have seen the API docs. Are there any examples/tutorials I can try out?

amundson (Thu, 29 Aug 2019 18:48:29 GMT):
@swetha the best "examples" in the repo are the test code. the sawtooth.rs code has a couple xo tests (it shows how to run the xo sawtooth transaction processor without modification). in particular, execute_create_xo_game() test has the basic flow.

amundson (Thu, 29 Aug 2019 18:49:36 GMT):
we should perhaps add some standalone example though, because the tests are not necessarily super accessible.

swetha (Thu, 29 Aug 2019 18:51:31 GMT):
I will start there then. Are issues generally tracked in JIRA on the Transact board?

amundson (Thu, 29 Aug 2019 18:52:16 GMT):
that sawtooth.rs module is behind a feature that is off by default, because we don't always want the sawtooth dependency. but if you ignore the compatibility stuff, the rest of it is the same.

swetha (Thu, 29 Aug 2019 18:57:13 GMT):
Okay, ill play around with that

swetha (Thu, 29 Aug 2019 18:57:23 GMT):
Thanks for that starting point!

amundson (Thu, 29 Aug 2019 18:57:31 GMT):
there is also the Command family - in workload::command.rs that is an implementation of a TransactionHandler. we started on an RFC for that which will explain it, I'll see if we can get it submitted to the RFC repo

amundson (Thu, 29 Aug 2019 18:59:19 GMT):
for JIRA, this is the kanban board we use - https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=232&quickFilter=621

amundson (Thu, 29 Aug 2019 18:59:54 GMT):
this is the backlog view: https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=232&view=planning.nodetail&quickFilter=621&epics=visible

amundson (Thu, 29 Aug 2019 19:05:30 GMT):
these sawtooth docs apply to transact, and potentially we could move over the content: https://sawtooth.hyperledger.org/docs/core/releases/latest/architecture/global_state.html, https://sawtooth.hyperledger.org/docs/core/releases/latest/architecture/transactions_and_batches.html

amundson (Thu, 29 Aug 2019 19:06:28 GMT):
some, but not all of this applies: https://sawtooth.hyperledger.org/docs/core/releases/latest/architecture/scheduling.html - the chain controller / block publisher stuff doesn't apply and the exact relationships between the components are better in Transact

amundson (Thu, 29 Aug 2019 19:07:26 GMT):
this has some content related to the receipts: https://sawtooth.hyperledger.org/docs/core/releases/latest/architecture/events_and_transactions_receipts.html

mattp (Thu, 29 Aug 2019 19:09:09 GMT):
Has left the channel.

amundson (Thu, 29 Aug 2019 19:10:29 GMT):
when we start pulling together a tutorial, we can use these source sections out of the sawtooth app dev guide, but modify them to match the Transact TransactionHandler API - https://sawtooth.hyperledger.org/docs/core/releases/latest/app_developers_guide/rust_sdk.html, https://sawtooth.hyperledger.org/docs/core/releases/latest/app_developers_guide/address_and_namespace.html, and some select portions of https://sawtooth.hyperledger.org/docs/core/releases/latest/app_developers_guide/event_subscriptions.html

amundson (Thu, 29 Aug 2019 19:11:54 GMT):
of course, none of that is geared toward the DLT developer, so doesn't cover how to actually use Transact itself, only how to write TransactionHandlers and some client code

swetha (Thu, 29 Aug 2019 19:24:34 GMT):
Okay, thanks for the resources. I don't see issues marked Help Wanted currently. What is the best way to start contributing to the project?

amundson (Thu, 29 Aug 2019 19:39:14 GMT):
a couple ideas: create some examples (so the next person doesn't have to dive into testing code), pull some of those docs over into the transact repo, do some performance testing and enhancements, write a state backend that works like Fabric's, start working on go bindings and/or go client code (@wkatsak has a start on Go transaction/batch building code)

amundson (Thu, 29 Aug 2019 19:45:55 GMT):
then there are several core things we need to reconcile for Fabric support, such as transaction differences and receipt<->rw set/events, which might be more RFCs ("how to modify the API to support X") or even a fabric.rs compatibility module for data structure conversation

swetha (Thu, 29 Aug 2019 20:14:58 GMT):
Thanks Shawn!

cbf (Thu, 29 Aug 2019 20:17:36 GMT):
+1! Thanks!

huxd (Fri, 30 Aug 2019 03:26:17 GMT):
where is the "Go transaction/batch building code" (or any other material describing this)? seems the transact-sdk-go repo is basically empty? I'm also interested in how transact might work with fabric...

mfford (Tue, 03 Sep 2019 12:48:52 GMT):
REMINDER: The Hyperledger Transact Contributor Meeting is tomorrow, Wednesday September 4th at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings You can also join the zoom link here: https://zoom.us/j/162904513 There is still time to add items to the agenda for this meeting. If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=16326231

st (Wed, 04 Sep 2019 12:23:45 GMT):
Has joined the channel.

rjones (Wed, 04 Sep 2019 22:29:17 GMT):
:transact:

MHBauer (Thu, 05 Sep 2019 02:05:44 GMT):
is that the logo? what is it?

rjones (Thu, 05 Sep 2019 02:07:50 GMT):
yes, it's the Transact logo

rjones (Thu, 05 Sep 2019 02:08:31 GMT):
I added :fabric: :sawtooth: :transact: :iroha: :besu: :hyperledger: and more

AlbertCL (Thu, 05 Sep 2019 12:18:46 GMT):
Has joined the channel.

AlbertCL (Thu, 05 Sep 2019 12:18:46 GMT):
Hi! I've just discovered this project. What is the state of it? Or where I can check the functionalities and the todo list? thanks!

amundson (Thu, 05 Sep 2019 12:54:49 GMT):
@AlbertCL check out the chat history above (Aug 29), I cover a lot of that

swetha (Mon, 09 Sep 2019 21:27:27 GMT):
Hi, I am having issues importing the SawtoothToTransactHandlerAdapter. When I add this line: https://github.com/hyperledger/transact/blob/master/libtransact/src/sawtooth.rs#L51 minus the comments, I am getting an ``` unresolved import `transact::sawtooth` ``` I am new to rust, so I am assuming I am making a mistake in terms of the module structure. Any ideas? I get the same issue if I try importing it internally such as using it in the src/lib.rs in libtransact. But there I try `use sawtooth`.

swetha (Mon, 09 Sep 2019 22:39:50 GMT):
*Update* Looks like I was missing the the feature enabling.

rbuysse (Thu, 12 Sep 2019 16:32:17 GMT):
Transact 0.1.6 has been released! https://crates.io/crates/transact/0.1.6

pschwarz (Thu, 12 Sep 2019 16:36:21 GMT):
This includes a fix to the sawtooth compat layer, and some better debug output from the protocol objects (no more giant byte vecs)

rjones (Mon, 16 Sep 2019 15:34:41 GMT):
Has left the channel.

swetha (Wed, 18 Sep 2019 22:45:51 GMT):
Hi, I am trying to extend the sawtooth xo create example to work with multiple transactions. I am having a little difficulty in understanding how the state changes should/are applied to the database. I have been applying the update to the database and though I am able to verify the changes are in the database, the root hash that is generated stays the same. Any ideas/tips? The essential steps I am doing: ``` let merkle_db = MerkleRadixTree::new(db.clone_box(), None).expect("Cannot initialize merkle database"); let initial_state_root = merkle_db.get_merkle_root(); let mut writer = db.get_writer().unwrap(); writer.put(game_address.as_bytes(), &value).unwrap(); assert_eq!( writer.as_reader().get(game_address.as_bytes()).unwrap(), value ); writer.commit().unwrap(); let merkle_db = MerkleRadixTree::new(db.clone_box(), None).expect("Cannot initialize merkle database"); let state_root = merkle_db.get_merkle_root(); assert_ne!(initial_state_root, state_root); ```

swetha (Wed, 18 Sep 2019 22:45:51 GMT):
Hi, I am trying to extend the sawtooth xo create example to work with multiple transactions. I am having a little difficulty in understanding how the state changes should/are applied to the database. I have been applying the update to the database and though I am able to verify the changes are in the database, the root hash that is generated stays the same. Any ideas/tips? The essential steps I am doing: ``` let db = Box::new(BTreeDatabase::new(&merkle::INDEXES)); let merkle_db = MerkleRadixTree::new(db.clone_box(), None).expect("Cannot initialize merkle database"); let initial_state_root = merkle_db.get_merkle_root(); let mut writer = db.get_writer().unwrap(); writer.put(game_address.as_bytes(), &value).unwrap(); assert_eq!( writer.as_reader().get(game_address.as_bytes()).unwrap(), value ); writer.commit().unwrap(); let merkle_db = MerkleRadixTree::new(db.clone_box(), None).expect("Cannot initialize merkle database"); let state_root = merkle_db.get_merkle_root(); assert_ne!(initial_state_root, state_root); ```

jsmitchell (Thu, 19 Sep 2019 00:48:01 GMT):
Looks like you might need to get_merkle_root() before the second ‘let merkle_db’

swetha (Thu, 19 Sep 2019 01:05:35 GMT):
Wouldn't that give me the merkle_root of the original tree? Since it was made from a clone of the db? I might also be misunderstanding what db.clone_box() does.

swetha (Thu, 19 Sep 2019 01:07:31 GMT):
Also in my code these line are actually a helper functions that take in a db. I just copied the one in sawtooth.rs https://github.com/hyperledger/transact/blob/master/libtransact/src/sawtooth.rs#L488-L492

jsmitchell (Thu, 19 Sep 2019 01:54:35 GMT):
That write commit should mutate the trie instance

jsmitchell (Thu, 19 Sep 2019 01:55:18 GMT):
If you create a new instance off of the db, that instance won’t have a root set

swetha (Thu, 19 Sep 2019 03:38:09 GMT):
What is the process of getting the new root? Because merkle_db cloned an earlier version of the tree so it doesn't have the update

jsmitchell (Thu, 19 Sep 2019 05:10:35 GMT):
@pschwarz should be able to answer this in the morning

pschwarz (Thu, 19 Sep 2019 13:27:02 GMT):
@swetha Take a look at the unit tests: https://github.com/hyperledger/transact/blob/master/libtransact/src/state/merkle.rs#L960 TL;DR: the `commit` function on `MerkleRadixTree` returns the new root. You should be writing your values via the merkle tree, not to the backing database directly.

josephnicholas (Thu, 19 Sep 2019 15:51:30 GMT):
Has joined the channel.

swetha (Thu, 19 Sep 2019 16:11:08 GMT):
@pschwarz Thanks! I will try that out. Why does the context manager take in the backing database instead of the MerkleRadixTree? I am following /expanding the example laid out in sawtooth.rs as I try to understand the end to end

pschwarz (Thu, 19 Sep 2019 16:34:00 GMT):
It creates MerkleRadixTree instances based on a base state root povided at the beginning of schedule. It can also be operating on multiple state-roots, backed by the same database. Since it's copy-on-write, this is safe.

swetha (Thu, 19 Sep 2019 17:09:05 GMT):
ahh, thanks!

swetha (Thu, 19 Sep 2019 17:40:36 GMT):
Is there a way to easily convert between the `receipt::StateChange` enum and the `state::StateChange` enum? I was also wondering why there are two enums for StateChange that are essentially the same. I see they have different methods implemented but don't understand why they could not be on the same enum.

swetha (Thu, 19 Sep 2019 18:14:44 GMT):
I took a look at the test you mentioned above. How does that work outside of that module? Isn't commit not public? I might be missing something simple, I am new to rust. Thanks for your help!

swetha (Thu, 19 Sep 2019 18:42:04 GMT):
I worked around it by using the MerkleRadixTree. I am not sure that was the right way to update the merkle tree.

pschwarz (Thu, 19 Sep 2019 19:06:50 GMT):
It's public via the `transact::state::Write` trait

pschwarz (Thu, 19 Sep 2019 19:07:39 GMT):
There should be a `From` implementation for those, somewhere. If not, we should probably add one

pschwarz (Thu, 19 Sep 2019 19:07:39 GMT):
There should be a `From` implementation for ~those~ the various StateChange structs, somewhere. If not, we should probably add one

amundson (Thu, 19 Sep 2019 19:49:49 GMT):
@swetha the reason there are multiple StateChange is that the modules are otherwise independent, IIRC--the two APIs don't fundamentally depend upon each other, even if they are working with (essentially) the same data within their respective APIs; trying to keep the interdependencies clean. receipt is basically a data class that is often serialized/deserialized (similar to transaction, batch, etc.) and so emphasis on that code is backward compatibility including the serialized formats; the state code doesn't necessarily have that restriction

swetha (Thu, 19 Sep 2019 19:55:03 GMT):
Thanks @pschwarz, I didn't realize you need to import the trait specifically. @amundson Is the `From` implementation that @pschwarz mentioned something that should be added to the implementation ? I understand trying to keep the modules independent, but I see that one would need to convert between the two often? Manually building the struct is not difficult, just seems a little weird if that is the expected process

amundson (Thu, 19 Sep 2019 20:40:33 GMT):
looking at some code which uses Transact, looks like it is doing the conversion manually. not great. we should add the From for sure, the question is were to put it (receipt or state). @pschwarz and I were discussing this briefly and we think it should probably go in the receipt module.

amundson (Thu, 19 Sep 2019 20:42:28 GMT):
reasoning is basically: receipt module is already concerned with conversions (to/from protobuf), so it seems more natural that it would support the conversion to state::StateChange. this is probably better (maybe) than introducing a third module.

amundson (Thu, 19 Sep 2019 20:44:43 GMT):
and, we probably only need receipt->state and not state->receipt

swetha (Thu, 19 Sep 2019 20:49:11 GMT):
Okay, I would love to send a pr in for that!

swetha (Thu, 19 Sep 2019 20:51:36 GMT):
I have been working on expanding and extracting the test you pointed me towards earlier : https://github.com/swetharepakula/transact/blob/examples/examples/src/main.rs. I know we discussed adding examples to the repo or the contrib repo when I started looking into this, I was wondering if the example was close to what you were thinking? Any feedback would be great

amundson (Fri, 20 Sep 2019 15:09:25 GMT):
@swetha yes, though I just took a quick look. I'll try and look deeper later and see if I have any feedback.

adineshreddy1 (Thu, 26 Sep 2019 15:04:42 GMT):
Has joined the channel.

swetha (Thu, 26 Sep 2019 19:14:17 GMT):
@amundson Have you had a chance to look at the example? Would it be easier if I opened a PR with that?

amundson (Thu, 26 Sep 2019 20:45:08 GMT):
@swetha I've only glanced at it, haven't had time yet to look over it in detail. opening a PR sounds good. some initial thoughts: a) needs copyright headers; b) not sure examples should be part of the workspace (need more opinions on this); c) we probably want to leave room for multiple examples, so sticking this under examples/simple_xo/ probably makes sense. (where "simple_xo" is whatever makes sense to call this one)

swetha (Thu, 26 Sep 2019 20:50:45 GMT):
@amundson I think where this should exist was what stopped me from making it into a PR initially cause I wasn't sure it should be in the workspace as well. I will rework the directory structure and submit a PR. Thanks! Also wasn't sure what is the typical way Transact tracks issues/PRs. For the other change I made I created a JIRA and put the jira number in the commit title, but I see that other commits don't follow that pattern

amundson (Thu, 26 Sep 2019 20:51:32 GMT):
ok, just looked at another repo we have w/examples and we do include it in the workspace

amundson (Thu, 26 Sep 2019 20:57:21 GMT):
@swetha we've generally followed https://chris.beams.io/posts/git-commit/

swetha (Thu, 26 Sep 2019 20:57:23 GMT):
Okay I will keep the examples in the workspace then and just create the simple_xo folder

amundson (Thu, 26 Sep 2019 20:58:34 GMT):
we don't generally link the commit to a bug/feature ticket, but is you want to you should use the format it suggests there

amundson (Thu, 26 Sep 2019 20:59:35 GMT):
the expectation is, basically, that the commit message should be good enough in isolation

swetha (Thu, 26 Sep 2019 21:00:19 GMT):
Thanks! I don't have a strong preference on adding the ticket number. I am used to Fabric and Cloud Foundry where the ticket was always in the title, so just learning what the process is here

amundson (Thu, 26 Sep 2019 21:01:57 GMT):
for #17, if you update the commit message, likely it will get merged tomorrow

swetha (Thu, 26 Sep 2019 21:38:21 GMT):
Oh great, will do that now

mfford (Mon, 30 Sep 2019 18:14:09 GMT):
The Hyperledger Transact Contributor Meeting is tomorrow, Monday October 7th at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar. You can also join the zoom link here: https://zoom.us/j/761947873 If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=22380624

mfford (Mon, 30 Sep 2019 18:14:09 GMT):
The Hyperledger Transact Contributor Meeting is, Monday October 7th at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar. You can also join the zoom link here: https://zoom.us/j/761947873 If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=22380624

mfford (Mon, 30 Sep 2019 18:14:09 GMT):
The Hyperledger Transact Contributor Meeting is Monday October 7th at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar. You can also join the zoom link here: https://zoom.us/j/761947873 If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=22380624

achenette (Mon, 07 Oct 2019 15:26:25 GMT):
At today's Transact contributor meeting, @amundson mentioned his earlier suggestions for Transact projects. Here's a link to that info: https://chat.hyperledger.org/channel/transact?msg=WfEjFtntwX962MEij ^ @arsulegai

achenette (Mon, 07 Oct 2019 15:28:53 GMT):
He listed "those docs" in this post: https://chat.hyperledger.org/channel/transact?msg=fWWaH4mHp2kevmqTb

achenette (Mon, 07 Oct 2019 15:28:53 GMT):
He listed "those docs" in this post: https://chat.hyperledger.org/channel/transact?msg=fWWaH4mHp2kevmqTb (See the original post for the full list.)

pschwarz (Mon, 07 Oct 2019 15:29:26 GMT):
Command Family RFC PR: https://github.com/hyperledger/transact-rfcs/pull/6

arsulegai (Mon, 07 Oct 2019 15:35:17 GMT):
Thanks @achenette @amundson . I will start with an example as well.

mfford (Mon, 07 Oct 2019 17:57:25 GMT):
Notes from Today's HL Transact Contributor Meeting: https://wiki.hyperledger.org/pages/viewpage.action?pageId=22381806

lehors (Tue, 08 Oct 2019 16:16:55 GMT):
Has joined the channel.

jsmitchell (Wed, 09 Oct 2019 17:41:37 GMT):
https://docs.google.com/document/d/12ce5XjmNdMF647mk2IyWdyz1mYPEA7MtCrfpKQw0t3c/edit#heading=h.2y5gwh60nerk

jsmitchell (Wed, 09 Oct 2019 17:41:49 GMT):
working doc for options of aries DID/VCs as an identity source for sawtooth/transact ^

Dan (Thu, 10 Oct 2019 15:29:54 GMT):
@nage ^ in case you didn't already see this

nage (Thu, 10 Oct 2019 15:29:54 GMT):
Has joined the channel.

mfford (Thu, 31 Oct 2019 13:42:55 GMT):
The Hyperledger Transact Contributor Meeting is Monday, November 4th at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings You can also join the zoom link here: https://zoom.us/j/761947873 If you have a topic that you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=24773672

johnfranklin (Mon, 04 Nov 2019 05:01:38 GMT):
Has joined the channel.

mfford (Mon, 04 Nov 2019 13:44:38 GMT):
REMINDER: The Hyperledger Transact Contributor Meeting is today at 10am CDT. This meeting can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings You can also join the zoom link here: https://zoom.us/j/761947873 The agenda for this meeting is located here: https://wiki.hyperledger.org/pages/viewpage.action?pageId=24773672

saanvijay (Tue, 05 Nov 2019 10:03:52 GMT):
Has joined the channel.

arsulegai (Tue, 05 Nov 2019 13:45:21 GMT):
Few questions here https://github.com/hyperledger/transact-rfcs/pull/6

arsulegai (Tue, 05 Nov 2019 13:45:35 GMT):
Is the work already started on this?

pschwarz (Tue, 05 Nov 2019 16:16:04 GMT):
You can find the protocols for this here: https://github.com/hyperledger/transact/blob/master/libtransact/src/protocol/command.rs

arsulegai (Tue, 05 Nov 2019 18:04:01 GMT):
Awesome

pschwarz (Tue, 05 Nov 2019 19:50:51 GMT):
The handler for it is here: https://github.com/hyperledger/transact/blob/master/libtransact/src/workload/command.rs

pschwarz (Tue, 05 Nov 2019 19:51:01 GMT):
(I had to take another look for it)

pschwarz (Tue, 05 Nov 2019 19:51:10 GMT):
Not where I thought it would be

arsulegai (Wed, 06 Nov 2019 03:53:58 GMT):
Thanks, is there a pending task in that or shall I dig into it to see if there's a need for anything?

amundson (Wed, 06 Nov 2019 16:19:51 GMT):
@arsulegai digging into it would be great

arsulegai (Tue, 12 Nov 2019 14:57:08 GMT):
I get this error `the trait `sawtooth_sdk::processor::handler::TransactionHandler` is not implemented for `handler::XYZHandler`` Trying to figure out what could be wrong with it.. Any help?

arsulegai (Tue, 12 Nov 2019 14:57:08 GMT):
I get this error ```the trait `sawtooth_sdk::processor::handler::TransactionHandler` is not implemented for `handler::XYZHandler```` Trying to figure out what could be wrong with it.. Any help?

arsulegai (Tue, 12 Nov 2019 14:57:08 GMT):
I get this error ```the trait `sawtooth_sdk::processor::handler::TransactionHandler` is not implemented for `handler::XYZHandler``` ` Trying to figure out what could be wrong with it.. Any help?

arsulegai (Tue, 12 Nov 2019 14:57:08 GMT):
I get this error ``` the trait `sawtooth_sdk::processor::handler::TransactionHandler` is not implemented for `handler::XYZHandler``` ` Trying to figure out what could be wrong with it.. Any help?

arsulegai (Tue, 12 Nov 2019 14:58:17 GMT):
The same Handler works well when run on the HL Sawtooth

arsulegai (Tue, 12 Nov 2019 15:05:27 GMT):
note: required by `transact::sawtooth::SawtoothToTransactHandlerAdapter`

pschwarz (Tue, 12 Nov 2019 15:24:36 GMT):
Do you have the `sawtooth-compat` feature turned on?

arsulegai (Tue, 12 Nov 2019 15:39:34 GMT):
In the Cargo.toml file?

pschwarz (Tue, 12 Nov 2019 17:20:01 GMT):
Yes

pschwarz (Tue, 12 Nov 2019 17:20:59 GMT):
There may be some compilation discrepancies due to the differing versions of the sawtooth sdk that the transact compat layer uses and your handler.

arsulegai (Tue, 12 Nov 2019 17:26:06 GMT):
Bingo!

arsulegai (Tue, 12 Nov 2019 17:26:39 GMT):
0.3.0 version of sawtooth-sdk worked for me

arsulegai (Tue, 12 Nov 2019 17:28:51 GMT):
I went into an open PR and looked at the splinter code, it's interesting to see how it works in those cases. I'm blank on that

AthilGafoor (Thu, 14 Nov 2019 05:15:48 GMT):
Has joined the channel.

arsulegai (Thu, 14 Nov 2019 09:44:36 GMT):
Is there a document/place I can look for to learn how to run Sabre on Transact?

AmimKnabben (Fri, 29 Nov 2019 01:10:52 GMT):
Has joined the channel.

arsulegai (Mon, 02 Dec 2019 16:03:40 GMT):
Will we have these calls rescheduled?

amundson (Mon, 02 Dec 2019 16:10:24 GMT):
@arsulegai we should switch to an as-needed meeting model, and try and discuss more items here

arsulegai (Mon, 02 Dec 2019 16:12:48 GMT):
No second thoughts on that, agree with you.

arsulegai (Mon, 02 Dec 2019 16:14:34 GMT):
New feature implementations, planned design changes are the interesting topics to discuss (here/need basis calls). It will align the thoughts on where the community is moving towards.. Just my opinion.

slavitch (Mon, 02 Dec 2019 17:27:00 GMT):
Has joined the channel.

amundson (Mon, 02 Dec 2019 19:03:43 GMT):
@arsulegai based on your previous feedback, we are adding the ability to store invalid results in the receipt store - https://github.com/hyperledger/transact/pull/26

arsulegai (Tue, 03 Dec 2019 04:44:15 GMT):
Storing the invalid results can be optional.. Storing the invalid transaction result becomes underlying blockchain/distributed platform implementation dependent. The end result of this could be a bloated invalid transactions in transaction receipt store.

arsulegai (Tue, 03 Dec 2019 04:44:44 GMT):
The other alternative could be to time the storage of invalid transactions in the receipt store.

slavitch (Tue, 03 Dec 2019 21:32:01 GMT):
Storing the invalid results is an error message that can be used to determine if there is s

slavitch (Tue, 03 Dec 2019 21:32:01 GMT):
Storing the invalid results is an error message that can be used to determine if there is some kind of attack or error in logic. A big problem with Hyperledger in particular is the opaque nature of the system. An audit trail should have failures as well as successes.

amundson (Thu, 05 Dec 2019 16:24:53 GMT):
storing invalid transaction results opens the network up to more DoS attacks that have to be mitigated, which is why Sawtooth's architecture doesn't store them. however, future Sawtooth or Scabbard can make different architectural decisions at that level, so from a Transact perspective, we just want to enable making that decision at the higher level.

amundson (Thu, 05 Dec 2019 16:26:19 GMT):
@slavitch not sure what you mean by "Hyperledger" - did you mean a specific project?

amundson (Thu, 05 Dec 2019 16:28:23 GMT):
We are planning on starting a transact javascript SDK, waiting on repo creation. initial code is in a splinter PR now, but planning on pushing it down to the Transact layer instead as its useful generally for anyone using Transact.

slavitch (Thu, 05 Dec 2019 17:51:13 GMT):
Is there any documentation on authentication and access control for Transact? My use case would have to interoperate with an external CA that provides X.509 certificates for humans signed using RSA.

amundson (Thu, 05 Dec 2019 18:33:35 GMT):
@slavitch Transact operates at a lower level than those concerns (it handles transaction processing, not not decisions about whether to process the transactions).

slavitch (Thu, 05 Dec 2019 18:46:26 GMT):
So that's done in the Smart Contract Engines? Can you recommend one that supports RSA signature verification, and support existing RSA-based x.509 certificates without requiring changes to PKI infrastructure?

Dipspaw (Thu, 12 Dec 2019 05:41:27 GMT):
Has joined the channel.

amundson (Fri, 13 Dec 2019 17:53:44 GMT):
The new experimental addresser feature just went into master - https://github.com/hyperledger/transact/pull/27

harrywright (Wed, 18 Dec 2019 18:13:14 GMT):
Has joined the channel.

amundson (Fri, 03 Jan 2020 17:39:03 GMT):
new addressing example - https://github.com/hyperledger/transact/tree/master/examples/address_generator

amundson (Fri, 03 Jan 2020 17:41:38 GMT):
we should be able to simplify a lot of existing sawtooth smart contracts by updating them to use addressers to handle address calculations instead of doing it manually as done today

Silona (Fri, 03 Jan 2020 21:48:26 GMT):
Has joined the channel.

raccoonrat (Tue, 07 Jan 2020 03:34:16 GMT):
Has joined the channel.

Silona (Tue, 14 Jan 2020 16:50:59 GMT):
Help Us Help you! Attend the Developer Relationship Meeting with Myself and our Marketing Dept. tomorrow at 9:00am Pacific Time. For the agenda and Dial in info https://wiki.hyperledger.org/display/Marketing/2020-01-15+Meeting+notes

Silona (Tue, 14 Jan 2020 17:01:53 GMT):
Calling all Projects! We will have a special Kiosk setup at Hyperledger Global Forum for Projects. We are asking that all projects sign up to do 10 minute presentations. https://wiki.hyperledger.org/display/HGF/Projects+Kiosk We will close this page on Feb 28 for printing reasons.

Silona (Tue, 14 Jan 2020 17:06:32 GMT):
Calling all Projects, SIG, and WG!!! We will have a Video recording Studio setup at HGF (Hyperledger Global Forum). We are asking that all projects and groups help us create a 5 minute video about your group so that we can promote it afterward. Sign up Here! https://wiki.hyperledger.org/display/HGF/Video+Recording+Schedule

rbuysse (Mon, 27 Jan 2020 15:48:23 GMT):
Version 0.1.7 of Transact has been released!

rbuysse (Mon, 27 Jan 2020 15:48:39 GMT):
You can view the release notes at https://github.com/hyperledger/transact/blob/v0.1.7/RELEASE_NOTES.md

Dan (Mon, 27 Jan 2020 20:46:14 GMT):
Hi Everyone, We are hoping to hear from everyone as we assess the health of our open source community. Please take 2 minutes to respond here: https://www.surveymonkey.com/r/DCIWGsurvey

amundson (Mon, 27 Jan 2020 21:50:43 GMT):
we are considering pulling pieces of sabre directly into libtransact as an optional feature, then making sawtooth-sabre depend upon transact for the pieces we move into transact

Silona (Mon, 27 Jan 2020 22:27:56 GMT):
The Linux Foundation’s CommunityBridge engineers are working on a tool to measure the health of critical open source projects and one of the key areas identified is QA Testing. They request that our communities provide honest and detailed information on testing tools and methodologies you use in your projects for us to come up with a detailed analysis, which they will share with all respondents and projects. https://www.surveymonkey.com/r/9H5G2GV. It’s only 5 questions long.

Patrick-Erichsen (Fri, 31 Jan 2020 16:47:49 GMT):
Has joined the channel.

ltseeley (Tue, 04 Feb 2020 15:02:39 GMT):
I'd like to request a release for transact. There are number of breaking changes, so this should be v0.2.

ltseeley (Tue, 04 Feb 2020 15:02:39 GMT):
I'd like to request a release for transact. There are a number of breaking changes, so this should be v0.2.

pschwarz (Tue, 04 Feb 2020 18:56:09 GMT):
@rbuysse

pschwarz (Tue, 04 Feb 2020 18:56:15 GMT):
:point_up:

rbuysse (Tue, 04 Feb 2020 19:32:25 GMT):
sounds good.

rbuysse (Tue, 04 Feb 2020 22:16:22 GMT):
A new version (0.2.0) of Transact has been released. You can view the release notes at https://github.com/hyperledger/transact/blob/v0.2.0/RELEASE_NOTES.md

ltseeley (Mon, 10 Feb 2020 15:44:36 GMT):
I'd like to request a new release for transact (v0.2.1) to make the changes in https://github.com/hyperledger/transact/pull/43 available

amundson (Mon, 10 Feb 2020 15:59:39 GMT):
@rbuysse ^

rbuysse (Wed, 12 Feb 2020 20:37:16 GMT):
A new version (0.2.1) of Transact has been released. You can view the release notes at https://github.com/hyperledger/transact/blob/v0.2.1/RELEASE_NOTES.md

Silona (Thu, 13 Feb 2020 18:26:20 GMT):
Howdy Contributors and Maintainers! Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend our Contributor/marketing meeting! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes

Silona (Mon, 17 Feb 2020 22:19:27 GMT):
Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend TOMORROW! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes

mslavitch (Mon, 17 Feb 2020 22:22:39 GMT):
Has joined the channel.

ltseeley (Tue, 18 Feb 2020 18:15:12 GMT):
Requesting a new release of transact (v0.2.2) due to https://github.com/hyperledger/transact/pull/47

rbuysse (Tue, 18 Feb 2020 20:47:12 GMT):
:thumbsup:

rbuysse (Tue, 18 Feb 2020 21:31:28 GMT):
A new version (0.2.2) of Transact has been released. You can view the release notes at https://github.com/hyperledger/transact/blob/v0.2.2/RELEASE_NOTES.md

ltseeley (Thu, 20 Feb 2020 20:00:45 GMT):
Requesting a v0.2.3 transact release

rbuysse (Thu, 20 Feb 2020 21:16:56 GMT):
A new version (0.2.3) of Transact has been released. You can view the release notes at https://github.com/hyperledger/transact/blob/v0.2.3/RELEASE_NOTES.md

Patrick-Erichsen (Thu, 20 Feb 2020 21:17:35 GMT):
Has left the channel.

kumar89 (Tue, 07 Apr 2020 16:04:49 GMT):
Has joined the channel.

MHBauer (Thu, 16 Apr 2020 21:18:37 GMT):
Has left the channel.

amundson (Wed, 22 Apr 2020 14:54:16 GMT):
we are planning to move the contract-archive feature from experimental to stable. if you want to participate in feature review, now is the time to go look at the code and comment here with suggestions.

arsulegai (Thu, 23 Apr 2020 10:59:41 GMT):
How is that planned to be used? Is it a store for blockchain implementation to load and remember contracts uploaded?

ltseeley (Thu, 23 Apr 2020 13:33:20 GMT):
@arsulegai it's intended as a standard way to package/archive smart contracts. `scar` files will be accepted by tools for uploading smart contracts to Transact.

arsulegai (Thu, 23 Apr 2020 14:26:41 GMT):
Got it! Thanks..

ltseeley (Tue, 28 Apr 2020 18:38:58 GMT):
I'd like to request a new patch release for transact

sawtooth (Wed, 13 May 2020 05:26:23 GMT):
Has joined the channel.

jmbarry (Mon, 18 May 2020 15:01:05 GMT):
Has joined the channel.

pschwarz (Wed, 20 May 2020 19:31:16 GMT):
I'd like to request a new patch release of transact, to include the stabilized contract-archive feature.

shadab14meb346 (Thu, 09 Jul 2020 04:38:58 GMT):
Has joined the channel.

kodonnel (Fri, 10 Jul 2020 16:30:24 GMT):
Is there a quickstart or tour guide or something for transact? The rust library docs are mostly a pile of facts. What I am interested in looking at is the feasibility/effort of implementing the 0MQ (IPC based in generally really) based engine

amundson (Fri, 10 Jul 2020 17:21:25 GMT):
not anything that eases you into it, no. a lot of the Sawtooth TEP doc applies at a high-level, and there is some high-level stuff in the project proposal

amundson (Fri, 10 Jul 2020 17:23:00 GMT):
Swetha contributed the simple_xo example which is fairly simple but also needs some cleaning up in terms of thread handling

amundson (Fri, 10 Jul 2020 17:24:50 GMT):
this static adapter code is the most relevant piece of the code - https://github.com/hyperledger/transact/blob/master/libtransact/src/execution/adapter/static_adapter.rs

amundson (Fri, 10 Jul 2020 17:25:28 GMT):
Basically, we would want a ZmqAdapter in addition to that StaticAdapter

amundson (Fri, 10 Jul 2020 17:25:28 GMT):
Basically, we would want a ZmqExecutionAdapter in addition to that StaticExecutionAdapter

amundson (Fri, 10 Jul 2020 17:27:49 GMT):
My previous plan was to use libsplinter's Transport code to do this - https://github.com/Cargill/splinter/tree/master/libsplinter/src/transport -- still probably makes sense

amundson (Fri, 10 Jul 2020 17:28:19 GMT):
there is ZMQ code there already, though it doesn't pass all the tests. I guess that would make it a TransportExecutionAdapter

spore-engineering (Fri, 10 Jul 2020 18:08:18 GMT):
Has joined the channel.

spore-engineering (Fri, 10 Jul 2020 18:10:50 GMT):
what happened to your beard man

kodonnel (Sat, 11 Jul 2020 01:50:31 GMT):
Cheers, That's sort of along the lines I was thinking.

amundson (Fri, 24 Jul 2020 19:41:01 GMT):
@kodonnel daml has a rust sdk now right?

kodonnel (Fri, 24 Jul 2020 20:11:49 GMT):
There's a prototype rust based engine, but it's nowhere near prime time. Main line is Scala/jvm based. There may be some client sdks out there but that's most likely just the grpc side of things

duncanjw (Sat, 25 Jul 2020 15:42:30 GMT):
Has joined the channel.

lebdron (Fri, 31 Jul 2020 09:16:15 GMT):
Has joined the channel.

cbf (Thu, 20 Aug 2020 14:27:25 GMT):
Has left the channel.

newhall (Thu, 20 Aug 2020 18:46:45 GMT):
Has joined the channel.

jcldnatv (Sat, 22 Aug 2020 17:30:25 GMT):
Has joined the channel.

supriya2385 (Thu, 27 Aug 2020 07:53:52 GMT):
Has joined the channel.

supriya2385 (Thu, 27 Aug 2020 07:53:52 GMT):
is there any sdks apart from rust?

supriya2385 (Thu, 27 Aug 2020 10:50:45 GMT):
is any java sdk available for transact?

arsulegai (Thu, 27 Aug 2020 11:20:19 GMT):
@supriya2385 no, but there's go client SDK

ashlinSajan (Thu, 27 Aug 2020 12:01:48 GMT):
Has joined the channel.

ashlinSajan (Thu, 27 Aug 2020 12:06:25 GMT):
@amundson I have seen in the transact repo the following lines "The transact-contrib repository contains examples and reference implementations" But I haven't seen any commands to run or proper code in the transact-contrib repo Could you please suggest where the sample implementation is how can I run the same?

supriya2385 (Thu, 27 Aug 2020 14:27:09 GMT):
ok

amundson (Thu, 27 Aug 2020 15:22:56 GMT):
@supriya2385 there is also a client sdk for javascript. roadmap-wise, it depends what you want the sdk for. currently there are no SDKs planning for wrapping the core execution code, but there are plans to expand the sdk support for clients and smart contracts

amundson (Thu, 27 Aug 2020 15:26:20 GMT):
@ashlinSajan it should probably read "Future home of" there, but the general idea is that contrib is a space for things that aren't technically part of the transact releases. There are some examples in the main transact repo; if you share a little about your use case I can try and point you in the right direction.

ashlinSajan (Fri, 28 Aug 2020 04:35:31 GMT):
Hi Shawn Thanks for your reply I wanted to explore the transact functionality.If there is a demo example it will be more easily understandable Is there a demo example to run and see in the main transact repo

amundson (Fri, 28 Aug 2020 14:26:51 GMT):
@ashlinSajan There is an example here, though its handling of threads isn't necessarily the best - https://github.com/hyperledger/transact/tree/master/examples/simple_xo ; if you want a fully working distributed ledger example, you could look at Scabbard, which is a simple DLT written using Transact - https://github.com/Cargill/splinter/tree/master/services/scabbard; there is also a lot of effort/code going in Sawtooth right now to support Transact, though that isn't example-level code as Sawtooth itself is fairly complex.

manoranjith (Fri, 02 Oct 2020 06:23:54 GMT):
Has joined the channel.

Sandeepk40 (Wed, 07 Oct 2020 04:25:52 GMT):
Has joined the channel.

jaromil (Fri, 09 Oct 2020 00:02:33 GMT):
Has joined the channel.

jaromil (Fri, 09 Oct 2020 00:05:29 GMT):
hi! is there any documentation on using transact with sawtooth, fabric or any other hyperledger blockchain?

amundson (Fri, 09 Oct 2020 17:13:06 GMT):
Not as such, as Transact isn't selected at runtime by a user. Sawtooth's master branch uses Transact and Splinter's Scabbard services uses Transact. In both cases, Transact isn't optional. Both are good examples of how to use Transact, with Scabbard being the simpler of the two.

piyushmaheshwari65 (Wed, 25 Nov 2020 04:20:54 GMT):
Has joined the channel.

Tmermer1 (Mon, 11 Jan 2021 10:14:10 GMT):
Has joined the channel.

rjones (Mon, 25 Jan 2021 18:28:16 GMT):
Has joined the channel.

rjones (Mon, 25 Jan 2021 18:28:16 GMT):
Hi, the following repos still use `master` as the default branch: `transact, transact-sdk-go, transact-sdk-javascript`. `main` [is the current guidance for naming](https://github.com/github/renaming).

arsulegai (Mon, 25 Jan 2021 18:30:37 GMT):
@rberg2 ^

amundson (Wed, 27 Jan 2021 14:53:53 GMT):
@rjones thanks, we are putting together a plan to roll out that change for Transact. We plan to start with Transact before we do Grid and then Sawtooth.

charith1994 (Sat, 15 May 2021 17:05:34 GMT):
Has joined the channel.

sukrutsathaye (Mon, 26 Jul 2021 16:25:26 GMT):
Has joined the channel.

sukrutsathaye (Fri, 06 Aug 2021 08:31:37 GMT):
are there any examples of using Transact with besu?

isabeltomb (Tue, 31 Aug 2021 20:51:33 GMT):
Has joined the channel.

leebradley (Fri, 03 Sep 2021 15:48:05 GMT):
Has joined the channel.

igorkrupczynski (Thu, 16 Sep 2021 10:15:38 GMT):
Has joined the channel.

BigmoneyJoe (Wed, 01 Dec 2021 15:57:19 GMT):
Has joined the channel.

BigmoneyJoe (Wed, 01 Dec 2021 15:57:22 GMT):
Hello, is the project Quarterly Update available by any chance. Contributors, when can we expect the updates?

agunde (Wed, 01 Dec 2021 16:49:27 GMT):
The update is going up today. It was delayed due to Thanksgiving.

BigmoneyJoe (Thu, 02 Dec 2021 14:25:20 GMT):
@agunde. Thanks for posting the project updates.

rjones (Wed, 23 Mar 2022 17:36:05 GMT):