[BUG] Error when calling a contract using contract package hash

[devendran-m]

Bug reported by David Hernando from MAKE

Bug Description:

The reportee's question and error he faced;

With AddressableEntities off, is it possible to call a contract by its contract package hash? I get an error with rc5:

Error in request. [Code: -32016] Invalid transaction.
Data: "the transaction was invalid: no such package at hash"

This is how the transaction was built;

            "entry_point": {
              "Custom": "unstake"
            },
            "target": {
              "Stored": {
                "id": {
                  "ByPackageHash": {
                    "addr": "601d407c7f1e339f4afd8ab6fcc4edc53619b3986c1ae84a6b3791b2ae394f8c",
                    "version": null
                  }
                },
                "runtime": "VmCasperV1"
              }
            }

The user faced a similar error with account_put_deploy, however, according to him, calling the contract by package name works normally.

The user also reported;

I'm using an SDK, but also tried with casper-client to send the transaction.
This is when I realized the node may be expecting a Package, because casper client only accepts a package-0123...def style key.

casper-client put-transaction package -v -k /home/casper/casper-nctl/assets/net-1/users/user-1/secret_key.pem \
    -n http://127.0.0.1:11101/rpc \
    --package-address package-9761df244f22aa4538cc844d29892086330e37cf157b213a8991d648fde34b48 \
    --session-entry-point unstake \
    --pricing-mode classic \
    --standard-payment true \
    --chain-name casper-net-1 \
    -p 5000000000 \
    -g 1

[devendran-m]

It is included in RC6

[davidatwhiletrue]

Tested on RC6, and working as expected.