|
Why is minifab channelquery changing the channel data?
When the user or context specified organization does not exist in the channel being queried via command 'minifab channelquery -c [the channel] ' minifab will add the organization to the channel. This
When the user or context specified organization does not exist in the channel being queried via command 'minifab channelquery -c [the channel] ' minifab will add the organization to the channel. This
|
By
Brett Tiller
·
#11462
·
|
|
Now: Private Chaincode Lab - 09/13/2022
#cal-notice
Private Chaincode Lab
When:
09/13/2022
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Where:
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09
Organizer: Marcus
Private Chaincode Lab
When:
09/13/2022
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Where:
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09
Organizer: Marcus
|
By
Group Notification <noreply@...>
·
#11461
·
|
|
Re: Transaction / Assets
#database
As a application owner and contract developer, you have the flexibility to define the structure of ledger data.
You can handle it based on application needs in the contract/chaincode method which is
As a application owner and contract developer, you have the flexibility to define the structure of ledger data.
You can handle it based on application needs in the contract/chaincode method which is
|
By
satheesh
·
#11460
·
|
|
Re: two channels with the same chaincode
Or to package only if a new chaincode name/label is created. Thus, to keep the same package when I just update a chaincode (i.e only increase the sequence number, and sync with the new docker image
Or to package only if a new chaincode name/label is created. Thus, to keep the same package when I just update a chaincode (i.e only increase the sequence number, and sync with the new docker image
|
By
Nikos Karamolegkos
·
#11458
·
|
|
Re: two channels with the same chaincode
Thank you. It is a bit confusing with the chaincode name and chaincode label. Nevertheless, is it bad to package each time the chaincode before the deployment? Even the chaincode name is the same?
Thank you. It is a bit confusing with the chaincode name and chaincode label. Nevertheless, is it bad to package each time the chaincode before the deployment? Even the chaincode name is the same?
|
By
Nikos Karamolegkos
·
#11457
·
|
|
Re: unregister user ID in HyperledgerFabric.
#fabric-ca-client
Hi ,
You can check the Identity section of the documentation: https://hyperledger-fabric.readthedocs.io/en/latest/identity/identity.html and in particular the section Certificate Revocation Lists.
How
Hi ,
You can check the Identity section of the documentation: https://hyperledger-fabric.readthedocs.io/en/latest/identity/identity.html and in particular the section Certificate Revocation Lists.
How
|
By
Tsvetan Georgiev
·
#11456
·
|
|
unregister user ID in HyperledgerFabric.
#fabric-ca-client
Hi, all.
I was just wondering the HLF blockchain network able to "un-registering that already registered to CA" or can't.
anyone have an idea about that?
If so, please let me know and I will be really
Hi, all.
I was just wondering the HLF blockchain network able to "un-registering that already registered to CA" or can't.
anyone have an idea about that?
If so, please let me know and I will be really
|
By
SANGWOO PARK
·
#11455
·
|
|
Re: two channels with the same chaincode
Hello,
The label is packaged with the chaincode, and is used to prefix a sha hash of the packaged file this makes the “packageid” (aka “chaincodeid”).
The chaincode name isn’t in
Hello,
The label is packaged with the chaincode, and is used to prefix a sha hash of the packaged file this makes the “packageid” (aka “chaincodeid”).
The chaincode name isn’t in
|
By
Matthew White
·
#11454
·
|
|
Re: two channels with the same chaincode
Also, If I have already packaged my chaincode to tar.gz file with PACKAGE_ID= abcdf and I would like to use the same chaincode to a new channel (same chaincode functionality but different chaincode
Also, If I have already packaged my chaincode to tar.gz file with PACKAGE_ID= abcdf and I would like to use the same chaincode to a new channel (same chaincode functionality but different chaincode
|
By
Nikos Karamolegkos
·
#11453
·
|
|
Now: Private Chaincode Lab - 09/06/2022
#cal-notice
Private Chaincode Lab
When:
09/06/2022
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Where:
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09
Organizer: Marcus
Private Chaincode Lab
When:
09/06/2022
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Where:
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09
Organizer: Marcus
|
By
Group Notification <noreply@...>
·
#11452
·
|
|
Re: two channels with the same chaincode
I think it is better to get the second option. I don't know which builder I am using. I deploy the chaincode as a service
I think it is better to get the second option. I don't know which builder I am using. I deploy the chaincode as a service
|
By
Nikos Karamolegkos
·
#11451
·
|
|
Re: two channels with the same chaincode
Hello;
Could you just confirm which chaincode builder you are using? There are a few different ones😊
Essentially I think you’ve two options
Use the same chaincode docker image, but
Hello;
Could you just confirm which chaincode builder you are using? There are a few different ones😊
Essentially I think you’ve two options
Use the same chaincode docker image, but
|
By
Matthew White
·
#11450
·
|
|
Re: two channels with the same chaincode
function or parameter? Can you give me an example?
function or parameter? Can you give me an example?
|
By
Nikos Karamolegkos
·
#11449
·
|
|
Re: two channels with the same chaincode
why not just pass the parameter as a function into the same chaincode?
From: fabric@... <fabric@...> on behalf of Nikos Karamolegkos <nkaram@...>
Sent: Monday, September 5, 2022 11:42 AM
To:
why not just pass the parameter as a function into the same chaincode?
From: fabric@... <fabric@...> on behalf of Nikos Karamolegkos <nkaram@...>
Sent: Monday, September 5, 2022 11:42 AM
To:
|
By
Yacov
·
#11448
·
|
|
Re: two channels with the same chaincode
I am using hlf-operator with the chaincode builder. Thank you for your proposals. So I have to keep one chaincode pod per channel although the functionality of the chaincodes are the same. Correct?
I am using hlf-operator with the chaincode builder. Thank you for your proposals. So I have to keep one chaincode pod per channel although the functionality of the chaincodes are the same. Correct?
|
By
Nikos Karamolegkos
·
#11447
·
|
|
Hyperledger Fabric Offline Private Key Transaction Signing Flow
#fabric
#fabric-sdk-node
#fabric-offline-tx-signing
#hyperledger-fabric
Hi Fabric Community,
I'm exploring the offline transaction signing flow in hyperledger fabric by using Fabric Node SDK.
I came across the following official tutorial.
Hi Fabric Community,
I'm exploring the offline transaction signing flow in hyperledger fabric by using Fabric Node SDK.
I came across the following official tutorial.
|
By
Kavin Arumugam
·
#11446
·
|
|
Re: Archival solution in hyperledger fabric
#fabric-peer
#fabric
Hi Shweta,
Yes, The solution works with fabric 2.4+, be careful, There should be at least one peer who has access to the full ledger. Also, go through the limitation. The major limitation is that you
Hi Shweta,
Yes, The solution works with fabric 2.4+, be careful, There should be at least one peer who has access to the full ledger. Also, go through the limitation. The major limitation is that you
|
By
Chandramohan Jagtap
·
#11445
·
|
|
Event: Documentation Workgroup monthly call - 09/02/2022
#cal-reminder
Reminder: Documentation Workgroup monthly call
When:
09/02/2022
11:00am to 12:00pm
(UTC-04:00) America/New
Reminder: Documentation Workgroup monthly call
When:
09/02/2022
11:00am to 12:00pm
(UTC-04:00) America/New
|
By
Group Notification <noreply@...>
·
#11444
·
|
|
Re: two channels with the same chaincode
Hi Nikos,
Sharing the CCaaS endpoint across multiple channels is asking for trouble. It _may_ work, but it seems like it's an invitation for unexpected problems if and when the states collide across
Hi Nikos,
Sharing the CCaaS endpoint across multiple channels is asking for trouble. It _may_ work, but it seems like it's an invitation for unexpected problems if and when the states collide across
|
By
jkneubuh@...
·
#11443
·
|
|
Archival solution in hyperledger fabric
#fabric-peer
#fabric
Pls confirm if below solution works for hlf 2.4 as i have gone throgh
https://hyperledger-fabric.readthedocs.io/en/release-2.3/peer_ledger_snapshot.html
Assumption: Lets we have 20000 blocks in
Pls confirm if below solution works for hlf 2.4 as i have gone throgh
https://hyperledger-fabric.readthedocs.io/en/release-2.3/peer_ledger_snapshot.html
Assumption: Lets we have 20000 blocks in
|
By
Kumari Shweta
·
#11442
·
|