New answers tagged

0

I'm under the impression that the owner of the contract is simply referred to as accounts[0] in Truffle's testing environment... Unless you explicitly specify {from: someAccount}, the default is indeed {from: accounts[0]}. And I'm calling the functions from contract A: function authorizeCaller(address addr) public { B._authorizeCaller(addr); } Here,...


1

Because your DannyTest instance does not have enough funds to pass that 1 wei.


0

In contract FlightSuretyApp, you should set variable flightSuretyData to the address of a FlightSuretyData instance. Here are a few ways to do it (depending on your use-case): constructor(FlightSuretyData _flightSuretyData) public { flightSuretyData = _flightSuretyData; } constructor(arg1, arg2, ...) public { flightSuretyData = ...


0

For truffle v5 it("...",async ()=>{ const result = await contractInst.messages({from: user1}); const events = await contractInst.getPastEvents('Message'); // iterate over the events // and do the necessary assertions });


0

ECDSA is the only natively supported signature verification algorithm. It should be possible to program other algorithms in the ethereum virtual machine. Although they might not be as performant as ECDSA or feasible to execute on-chain. While ECDSA can be used to verify signatures it doesn't deal with message tampering. There are other algorithm used to ...


Top 50 recent answers are included