Uploaded image for project: 'Fabric'
  1. Fabric
  2. FAB-6959

As a developer, I want to be able to implement a read-only chaincode function without having to grant write access to the channel

    Details

    • Type: Story
    • Status: To Do (View Workflow)
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Future
    • Component/s: fabric-peer
    • Labels:
      None
    • SDK Impact:
      Unset
    • System Test Impact:
      Unset
    • Documentation Impact:
      Unset

      Description

      In the current implementation, in order to invoke chaincode, a client must also have write access to the channel on which the chaincode is deployed. This is problematic because even if the chaincode function simply returns data (i.e. is a query), one still needs to call the Invoke function and since Invoke could be a read or a write, as mentioned the client must have write access to the channel. It would be preferable to be able to require read-only permission in order to access chaincode. While you can of course provide access control with chaincode, this still would not prevent a client from submitting transactions to the orderer on that channel.

      The most common use case is a common channel used to provide reference information where only a limited set of parties should be able to write to the channel with the majority of parties will simply be querying the reference data.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mastersingh24 Gari Singh
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Git Source Code