|
Re: [External] : [Hyperledger Fabric] IoT with frequent data and possibly incorrect data sometimes
Yes, an aggregator running the client SDK would be needed. In Oracle Blockchain Platform we provide a built in aggregator with REST APIs. If the IOT devices can make REST calls, that’s all
Yes, an aggregator running the client SDK would be needed. In Oracle Blockchain Platform we provide a built in aggregator with REST APIs. If the IOT devices can make REST calls, that’s all
|
By
Mark Rakhmilevich
·
#9933
·
|
|
Re: [External] : [Hyperledger Fabric] IoT with frequent data and possibly incorrect data sometimes
If you are using client SDK for Fabric, use register() and enroll() APIs to register client orgs and issue their enrollment cert.
Mark
If you are using client SDK for Fabric, use register() and enroll() APIs to register client orgs and issue their enrollment cert.
Mark
|
By
Mark Rakhmilevich
·
#9932
·
|
|
Re: Fabric CA server with customized CSR details.
As Yacov said, it is not recommended although it is possible. There are details that explain the deployment steps in this
As Yacov said, it is not recommended although it is possible. There are details that explain the deployment steps in this
|
By
Chris Gabriel <alaskadd@...>
·
#9931
·
|
|
Re: Fabric CA server with customized CSR details.
You can, but it's not recommended
From: "Pechimuthu T"<tpmuthu@...>
To: alaskadd@...,fabric@...
Date: 04/29/2021 02:40 PM
Subject: [EXTERNAL] Re:[Hyperledger Fabric] Fabric CA
You can, but it's not recommended
From: "Pechimuthu T"<tpmuthu@...>
To: alaskadd@...,fabric@...
Date: 04/29/2021 02:40 PM
Subject: [EXTERNAL] Re:[Hyperledger Fabric] Fabric CA
|
By
Yacov
·
#9930
·
|
|
Re: Fabric CA server with customized CSR details.
Hi,
For an Organization let say Org1, if we setup a CA server, do We have to setup of TLSCA separately ?
Can't we use the same CA which can function as CA and TLSCA as well ?
Thanks and
Hi,
For an Organization let say Org1, if we setup a CA server, do We have to setup of TLSCA separately ?
Can't we use the same CA which can function as CA and TLSCA as well ?
Thanks and
|
By
Pechimuthu T
·
#9929
·
|
|
Re: [External] : [Hyperledger Fabric] IoT with frequent data and possibly incorrect data sometimes
So you propose each IoT end device (ED) to be an organization? The EDs can not support fabric to run the a fabric client application and start a transaction, somehow a proxy (or a IoT) should
So you propose each IoT end device (ED) to be an organization? The EDs can not support fabric to run the a fabric client application and start a transaction, somehow a proxy (or a IoT) should
|
By
Nikos Karamolegkos
·
#9928
·
|
|
Re: [External] : [Hyperledger Fabric] IoT with frequent data and possibly incorrect data sometimes
Thanks for your reply.
You mean, like we register users in an org?
These users are defined in crypto-config.yaml and cryptogen assigns IDs to all. New users are added via the client API.
When devices
Thanks for your reply.
You mean, like we register users in an org?
These users are defined in crypto-config.yaml and cryptogen assigns IDs to all. New users are added via the client API.
When devices
|
By
Mahwish Anwar
·
#9927
·
|
|
Re: [External] : [Hyperledger Fabric] IoT with frequent data and possibly incorrect data sometimes
You can register the IoT devices as client orgs of the trusted node with their own signing certs. Instead of sending an avg, send the actual data and let the chaincode maintain a running average and
You can register the IoT devices as client orgs of the trusted node with their own signing certs. Instead of sending an avg, send the actual data and let the chaincode maintain a running average and
|
By
Mark Rakhmilevich
·
#9926
·
|
|
Re: ORDERER_ADMIN env variables
#fabric-orderer
It seems it should work, but it is possibly using the generic orderer.yaml file and not your env variables. So, you may want to double-check that you are working from the correct directory and you
It seems it should work, but it is possibly using the generic orderer.yaml file and not your env variables. So, you may want to double-check that you are working from the correct directory and you
|
By
Chris Gabriel <alaskadd@...>
·
#9925
·
|
|
Re: Deprecation of Docker Runtime in Kubernetes - No access to local docker socket
#docker
#hyperledger-fabric
#fabric
From what I have found so far in a limited bit of looking into the effects of the deprecation when it actually happens is that it will cause a breaking change to the Dind container. Although there is
From what I have found so far in a limited bit of looking into the effects of the deprecation when it actually happens is that it will cause a breaking change to the Dind container. Although there is
|
By
Chris Gabriel <alaskadd@...>
·
#9924
·
|
|
Difference chaincode (smart contracts) in private collection
I am wondering if in a private Hyperledger Fabric 2.2 network with N organizations in one channel can have different private smart contracts? Specifically, I would like to build a network with N orgs
I am wondering if in a private Hyperledger Fabric 2.2 network with N organizations in one channel can have different private smart contracts? Specifically, I would like to build a network with N orgs
|
By
Nikos Karamolegkos
·
#9923
·
|
|
Fabric Contributor Meeting - Wed, 04/28/2021
#cal-notice
Fabric Contributor Meeting
When:
Wednesday, 28 April 2021
9:00am to 10:00am
(GMT-04:00) America/New
Fabric Contributor Meeting
When:
Wednesday, 28 April 2021
9:00am to 10:00am
(GMT-04:00) America/New
|
By
fabric@lists.hyperledger.org Calendar <noreply@...>
·
#9922
·
|
|
Re: Compromised endorsement peers scenario
The fundamental assumption of a blockchain is that with enough peers it is extremely unlikely for the majority of them to get hacked.
Translated to Fabric - you need multiple organizations, each with
The fundamental assumption of a blockchain is that with enough peers it is extremely unlikely for the majority of them to get hacked.
Translated to Fabric - you need multiple organizations, each with
|
By
David Enyeart
·
#9921
·
|
|
Compromised endorsement peers scenario
Hello,
I have a question in the following scenario. We have 2 organizations with 5 endorsing (&commiting) peers each one and X orderers. If all the peers of the network are hacked and always approve
Hello,
I have a question in the following scenario. We have 2 organizations with 5 endorsing (&commiting) peers each one and X orderers. If all the peers of the network are hacked and always approve
|
By
Nikos Karamolegkos
·
#9920
·
|
|
IoT with frequent data and possibly incorrect data sometimes
In an IoT scenario, multiple nodes are sending frequent data. It is not feasible to create a fabric network with all devices.
Instead, a fabric node acts as an aggregator, that takes all values from
In an IoT scenario, multiple nodes are sending frequent data. It is not feasible to create a fabric network with all devices.
Instead, a fabric node acts as an aggregator, that takes all values from
|
By
Mahwish Anwar
·
#9919
·
|
|
Detecting hacked Fabric Node
#administrator-organiization
#fabric
If a Fabric peer node is hacked, is there a way to figure it out?
For example, N1 (org1), N2 (org2), N3 (org3) and N4(org4) are in network. Each N is a peer.
Breaking down the fabric flow:
1)The
If a Fabric peer node is hacked, is there a way to figure it out?
For example, N1 (org1), N2 (org2), N3 (org3) and N4(org4) are in network. Each N is a peer.
Breaking down the fabric flow:
1)The
|
By
Mahwish Anwar
·
#9918
·
|
|
Re: Deprecation of Docker Runtime in Kubernetes - No access to local docker socket
#docker
#hyperledger-fabric
#fabric
Using DinD in the short term should work ok, but be aware that you will need to run the Dind container with elevated privileges which can be problematic in many environments. The best course of
Using DinD in the short term should work ok, but be aware that you will need to run the Dind container with elevated privileges which can be problematic in many environments. The best course of
|
By
Gari Singh
·
#9917
·
|
|
Re: ORDERER_ADMIN env variables
#fabric-orderer
Sure, here it is,
##############
image: hyperledger/fabric-orderer:2.3
environment:
- FABRIC_LOGGING_SPEC=INFO
- ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
-
Sure, here it is,
##############
image: hyperledger/fabric-orderer:2.3
environment:
- FABRIC_LOGGING_SPEC=INFO
- ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
-
|
By
Kumar Shantanu
·
#9916
·
|
|
Fabric contributor meeting - April 28, 2021
Hyperledger Fabric Contributor Meeting
When: Every other Wednesday 9am US Eastern, 13:00 UTC
Where: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09
Agendas and Recordings:
Hyperledger Fabric Contributor Meeting
When: Every other Wednesday 9am US Eastern, 13:00 UTC
Where: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09
Agendas and Recordings:
|
By
David Enyeart
·
#9915
·
|
|
Re: ORDERER_ADMIN env variables
#fabric-orderer
Hi Shantanu,
Can you please share all of your orderer env variables? That may assist in helping.
Thanks
Hi Shantanu,
Can you please share all of your orderer env variables? That may assist in helping.
Thanks
|
By
Chris Gabriel <alaskadd@...>
·
#9914
·
|