Different Contract Owner Address and Mnemonic file
Hello Guys, I changed the Member Account ethereum address and whenever I deploy a contract, it still uses or sees the old member account address as the owner of the contract that deployed it. Also, how do I get a new mnemonic keyfile when trying to deploy another project but on the same blockchain. Any idea?Sending transaction to Azure Blockchain on Quorom Protocol giving EVM error using web3
Hello guys, please I need help with the right code snippet to send transaction/state change to the blockchain. I can make calls but sending transaction is always giving me an error. Either "unknown account" if I do just web3.eth.sendTransaction or "Error: Transaction has been reverted by the EVM: " when I use web3.eth.sendSignTransaction. Also, how do I send transactions as owner to a contract I deployed since no password was provided for the account that deployed the contract to the blockchain. I was able to get the privateKey from the mnemonic phrase generated when I connected my VSCode to the Azure Blockchain service subscription. I also checked pending transanctions and it is 80. Why is my transactions not being mined. web3.eth.getTransactionCount(account).then(async (txCount) => { try { let newaccount = await web3.eth.personal.newAccount('XXXXX') web3.eth.defaultAccount = newaccount, console.log("newaccount >> ", newaccount) let unlockedAcct = await web3.eth.personal.unlockAccount(newaccount,'XXXXX',10000) console.log("unlockedAcct >> ", unlockedAcct) const txObject = { nonce: txCount, from: web3.eth.defaultAccount, to: address, data: functionABI, gasPrice: web3.utils.toHex('0'), gasLimit: web3.utils.toHex('3000000'), chainid: 1425 } let signedTxn = await web3.eth.personal.signTransaction(txObject,"XXXXX") console.log("signedTxn >> ", signedTxn) let txnHash = await web3.eth.sendTransaction( web3.eth.defaultAccount, signedTxn.raw) console.log("txnHash >> ", txnHash) web3.eth.sendTransaction(txObject,function( transactionHash) { console.log(transactionHash); }); const tx = new EthereumTx(txObject) tx.sign(privateKey1) const serializedTx = tx.serialize() //console.log(tx) const raw = '0x' + serializedTx.toString('hex') console.log(raw) web3.eth.sendSignedTransaction(raw, (err, transactionHash)=>{ console.log('txHash:', transactionHash) console.log('Error:', err);}) } catch (error) { console.log('Error ',error) } });
Multi member consortium - governance of shared resources
Azure's Blockchain Workbench offers "Multi-Member with one member subscription, and Multi-Member System Deployed in One Shared Subscription options" for consortiums. I understand the "application / blockchain protocol" level governance tools available to each party in a multi-member consortium. How does governance of the shared infrastructure services work? What I currently see is one party currently launching the blockchain platform on a specific enterprise plan (with a fixed set of nodes), inviting members, giving invited members no capabilities to manage the shared resources (e.g. they can set up private channels and invite other members, and launch/remove their own nodes/peers). Some questions I have: Does the party who launches the blockchain consortium instance on Azure have more "powers" than invited members? Can an invited member add more peers or remote nodes than the rest of the consortium, and then perform something like a 51% attack? Can fees be split between consortium members?Improved governance experience with Ethereum Proof-of-Authority 1.2
Since launching Ethereum Proof-of-Authority we've received great feedback and have learned more about the ways our customers have leveraged this solution to roll out their Blockchain applications. We’ve rolled out a number of features that improve user-experience, configuration, and deployment reliability. Read about it in the Azure blog.
"The" Blockchain
Hello Community, I am digging through the Azure Blockchain workbench. My question is around the messaging that is being presented. I see "blockchain" used everywhere, but when digging into the samples, there is a https://github.com/Azure-Samples/blockchain/blob/master/blockchain-workbench/application-and-smart-contract-samples/hello-blockchain/HelloBlockchain.sol which --from my rather rudimentary understanding -- is actually the Ethereum blockchain. Is there somewhere that describes this in more detail? Is Ethererum the officially-supported blockchain of MSFT? Or is it a custom blockchain based on Ethereum? Or something different altogether? 🙂 It would seem that if Ethereum is the official backing blockchain that it would be more prevalent in the messaging so that those of us like myself don't have to bother taking up cycles in forums like these by getting more clarity on this. Thank you for any clarification you can offer, MichaelImproved multi-member Blockchain networks now available on Azure
We see strong customer interest in the Blockchain solutions that are available on the Azure Marketplace. As customers build production Blockchain scenarios, we understand that network reliability and health monitoring become increasingly important. Today, we are excited to announce significant enhancements to our Ethereum on Azure offering. These improvements are the first of a series of releases designed to enable production-ready consortium Blockchain networks suited for enterprise scenarios. Read more about it in the Azure blog.
Announcing Support for Multi-member Consortium Blockchain Networks on Azure
We are excited to announce expansion of our blockchain support on Azure to be the first public cloud that enables multi-member consortium blockchain networks addressing enterprise scenarios that require a deployment of a private network across Azure regions, subscriptions, and Azure Active Directory (Azure AD) tenants! For more details, check out the blog post that came out today.Need IP range for RPC end point Ethereum Consortium Network
Hi, I am trying to explore the Ethereum Consortium Network to try out few sample contracts. I had followed the instructions given in the site https://github.com/Azure/azure-quickstart-templates/tree/master/ethereum-consortium-blockchain-network and created a resource group. It returned an RPC end point http://ethtesf2h.southindia.cloudapp.azure.com:8545 My firewall is blocking the this particular URL and hence I am not able to connect to the network. Can you let me know the IP ranges that I need to whitelist? I found a list of public IPs (https://www.microsoft.com/en-in/download/details.aspx?id=41653) which microsoft azure uses but my RPC end point returned me an IP 52.172.10.254, which was not in the list given. Also they had also mentioned that the public IPs ranges change ever week. So does it mean that I will have to update the IP ranges every week for whitelisting?
