[telegram] <Stepan> The bug was fixed by updating the nearest parent package.json file with the following entry:
{
"type": "module",
...} (re @Stepan: #gRPC #nodeJS
Hi. JS script when executed gives an error on import grpc from ('grpc'); "SyntaxError: Cannot use import statement outside a module". how to fix? ...example for the client side is not the most successful and simple, where is the kaizen concept)
it's simple: https://t.me/hyperledgeriroha/23128
and it's not easy anymore:
import grpc from 'grpc'
import {
QueryService_v1Client,
CommandService_v1Client
} from '../iroha-helpers/lib/proto/endpoint_grpc_pb'
import { commands, queries } from 'iroha-helpers'
const IROHA_ADDRESS = 'localhost:50051' ...)
[telegram] <Stepan> do you think such an example of a client script in JS will take off? )
...
var PROTO_PATH = __dirname + '/../../shared_model/endpoint.proto';
var grpc = require('@grpc/grpc-js');
var protoLoader = require('@grpc/proto-loader');
var packageDefinition = protoLoader.loadSync(
PROTO_PATH,
{keepCase: true,
longs: String,
enums: String,
defaults: true,
oneofs: true
});
var CommandService_v1= grpc.loadPackageDefinition(packageDefinition).grpc.CommandService_v1;
var commandService = new CommandService_v1(
IROHA_ADDRESS,
grpc.credentials.createInsecure()
) (re @Alexander: shared_model/endpoint.proto)
- Solana smart contract development (Unit test, solana-program-library, Solana-web3, Raydium swap and orca) by using Rust and Anchor framework
2.Cardano smart contract by using Haskell and CosmWasm smart contract by using Rust CosmWasm. - Smart contract development in networks (Ethereum, BSC, Matic/Polygon) by using Solidity.
- Front-end development interactive with smart contract by using Web3, truffle, React(Redux / Thunk / Saga), Angular and Vue.
- ICO, IDO, Defi Swap, Reward system for staking, AOM(Olympus DAO Fork), Hyperledger Fabric
- NFT minting and NFT marketplace development(Create listing by admin, flat & Crypto payment, Bundle Sale/ Bulk Transfers, Drops, Rating, Bidding & Auction)
-Minter in Candy machine and 10% royalty moved to burn and other wallets
-Burn mechanism with kind of sharing rewards back to the holders
-Minting by user randomly NFTs, Upload the NFT arts and Traits(metadata) to IPFS
7.Bot development for sale monitoring bot OS and Niftygateway - Cryto game development with crypto payment gateway
Let's discuss your project together.
Thanks.)
[telegram] <♌︎ Leo> Makes sense if u only need a few of the iroha APIs and don’t wish to add the iroha-helpers as a dependency. But, if u need a lot more APIs, then you run the of risk reinventing the whole iroha-helpers. (re @Stepan: do you think such an example of a client script in JS will take off? )
...
var PROTO_PATH = __dirname + '/../../shared_model/endpoint.proto';
var grpc = require('@grpc/grpc-js');
var protoLoader = require('@grpc/proto-loader');
var packageDefinition = protoLoader.loadSync(
PROTO_PATH,
{keepCase: true,
longs: String,
enums: String,
defaults: true,
oneofs: true
});
var CommandService_v1= grpc.loadPackageDefinition(packageDefinition).grpc.CommandService_v1;
var commandService = new CommandService_v1(
IROHA_ADDRESS,
grpc.credentials.createInsecure()
))
[telegram] <Grouvie> Is Hyperledger Burrow still supported by Iroha or is it suggested to use other solutions to implement smart contract functionality?
The Hyperledger Burrow Github states:
"Hyperledger Burrow has been moved to End of Life status by the original project maintainers."
[telegram] <Sara> Hi So, we discussed this with the team and decided to not remove the code that allows to work with Burrow as for now I do not think there is an alternative (unless @baziorek has something that could help in one of his mentorship projects?). So, you can use the last version of the Burrow but we cannot guarantee it will work well because the project is being closed. (re @Grouvie: Is Hyperledger Burrow still supported by Iroha or is it suggested to use other solutions to implement smart contract functionality?
The Hyperledger Burrow Github states:
"Hyperledger Burrow has been moved to End of Life status by the original project maintainers.")
[telegram] <baziorek> No I don't have:).
THere is iroha+burrow in iroha's official docker image. It can be used and it is working:). (re @Sara: Hi So, we discussed this with the team and decided to not remove the code that allows to work with Burrow as for now I do not think there is an alternative (unless @baziorek has something that could help in one of his mentorship projects?). So, you can use the last version of the Burrow but we cannot guarantee it will work well because the project is being closed.)
Latest stable release is Iroha 1.5:
https://github.com/hyperledger/iroha/releases
EDIT: About the bug - please describe some details, maybe somebody would be able to fix its (if the bug still exists in newest versions) (re @Yasir: Hi, I am planning to upgrade iroha nodes that I have for our company. I've seen a bug in it for some reason asset balances are slightly different on different nodes. +-1 difference. Wanted to ask which is the latest stable release?)
[telegram] <Sara> I think we'd need to ask Alexander on Monday to be sure. Please remind me about that if I forget, ok (re @Yasir: Thank you for the response. Before I talk more about the bug, could you clear one thing for me please?
Can I upgrade to 1.5.0 from 1.2.1 without overwritting the ledger? As I tried it on one node and it says that schema is not compatibile... @baziorek @liralemur)
There is tool to migrate DB scheema: https://github.com/hyperledger/iroha-state-migration-tool/tree/main/migration_data
but it is not updated to version 1.5.
So probably to migrate version You need to override database by migrating nodes one by one. But lets wait for Monday to ask Alexander:). (re @Yasir: Gensis block in example of both 1.2.1 and 1.5.0 are exactly the same. Is postgres schema changed?)
There is tool to migrate DB scheema: https://github.com/hyperledger/iroha-state-migration-tool/tree/main/migration_data
but it is not updated to version 1.5.
So probably to migrate version You need to override database by migrating nodes one by one. But lets wait for Monday to ask Alexander:).)
👉 https://t.me/+Oo1mEYs6tjcwMzky
docker run --name iroha \
-d \
-p 50051:50051 \
-v $(pwd)/iroha/example:/opt/iroha_data \
-v blockstore:/tmp/block_store \
--network=iroha-network \
-e KEY='node0' \
hyperledger/iroha:latest
my iroha container exits with the following logs:
key=node0
/opt/iroha_data
WARNING: IROHA_POSTGRES_HOST is not defined.
Do not wait for Postgres to become ready. Iroha may fail to start up
[2022-06-02 18:36:58.173776200][E][Init]: Failed reading the configuration: File 'config.docker' could not be read.
How can I fix this?
[telegram] <Sara> Forwarded from Hyperledger Iroha news: Let's meet for our community call in an hour!
Updates from both Irohas, opportunity to ask questions if you have any or simply meet the maintainers :)
Just jump in at noon CET: https://zoom.us/my/hyperledger.community.3
Password: 475869