CRYPTO NEWS

Bakkt: Nearly 50% of gig workers open to getting paid in crypto

Bakkt’s study carried out in June and July found that 38% of gig workers are open to being paid in crypto, and the number jumps to nearly 50% for those willing to receive part of their gig pay in crypto.

Bakkt Holdings, Inc. (NYSE: BKKT), a leading digital asset platform offering a range of cryptocurrency services including buying and selling of Bitcoin and Ethereum among others, has released the findings of a new study showing almost half of people working in the gig economy are okay with getting a portion of their wages paid in crypto.

The US-based company announced this on Friday, with the findings part of a study dubbed “Gig Workers & Crypto Study.” This study happened at a time when crypto volatility was at its peak between mid-June and early July.

Crypto appeal among gig workers growing

In its assessment, and from the responses received regarding cryptocurrency payments in the gig industry, 38% of the respondents said they would accept all their pay in crypto. Narrowing this question to whether they would accept a portion of the pay in cryptocurrencies, nearly 50% said they would.

20% of the gig workers involved in the survey said they have been paid in crypto before.

The increasing appeal and the existing usage of cryptocurrency among gig workers came through clearly in our study,” Nicolas Cabrera, Bakkt’s chief product officer of payments said in the press release.

Crypto has seen increased acceptance as a salary payment mode among most sectors within the gig economy. Most of the workers in the various industries, including freelancers, social influencers, and rideshare drivers, are increasingly tech savvy and thus more willing to accept crypto.

While this group could benefit from increased understanding of how crypto can be used, rideshare drivers, food delivery drivers and other gig workers cite crypto as the next generation of currency and are drawn to the potential increase in the value of their pay,” Cabrera noted.

The post Bakkt: Nearly 50% of gig workers open to getting paid in crypto appeared first on CoinJournal.

Calling a function with multiple arguments in ethers returns Error: missing argument

I’m changing a part of front-end for my dApp from using Moralis to using ethers.js. For some reason I cannot get my head around on how to provide multiple arguments for the function call in a correct manner. Consider this contract function that does on-chain conversion, using an oracle: function getUniversalConversionRate(uint256 coinAmount,address priceFeedAddress) public view::Listen

I’m changing a part of front-end for my dApp from using Moralis to using ethers.js. For some reason I cannot get my head around on how to provide multiple arguments for the function call in a correct manner.

Consider this contract function that does on-chain conversion, using an oracle:

    function getUniversalConversionRate(uint256 coinAmount,address priceFeedAddress)      public view returns (uint256) {         uint256 coinPrice = getUniversalPrice(priceFeedAddress);         uint256 coinAmountInUsdCents = (coinPrice * coinAmount) /10000000000000000;         return coinAmountInUsdCents;} 

This is its ABI:

    {         "inputs": [             {"internalType": "uint256","name": "coinAmount","type": "uint256"},             {"internalType": "address","name": "priceFeedAddress","type": "address"}],         "name": "getUniversalConversionRate",         "outputs": [{"internalType": "uint256","name": "","type": "uint256"}],         "stateMutability": "view",         "type": "function"}, 

And this is how I interact with it:

  const provider = new ethers.providers.JsonRpcProvider("https://rpc...", 80001);   const signer = new ethers.Wallet("0x...", provider); //saving space   const administrativeSidechainContract = new ethers.Contract(mainContractAddress, abi, signer)      async function updateUI() {   const ethPriceData = await administrativeSidechainContract.getUniversalConversionRate({        coinAmount: "1", priceFeedAddress: "0x...." })   console.log(ethPriceData)}   updateUI() 

I provide both arguments which are correct and work in another framework with the same inputs but with ethers i get Error: missing argument: passed to contract (count=1, expectedCount=2, code=MISSING_ARGUMENT, version=contracts/5.6.0) What do I do wrong?

Bakkt: Nearly 50% of gig workers open to getting paid in crypto

Shopping cart
There are no products in the cart!
Continue shopping
0