zvezda
9 months ago  Karma: 166
How does DelegateCall work?
  • Is there an equivalent of gas in the DC dAppChain? What token is it paid in?
  • Users can log in with Google or GitHub. Where are private key stored? Are transactions signed by the web app?
  • What is the process for redeeming Karma for DelegateCall tokens on the Ethereum mainnet?
#DelegateCall
zvezda
9 months ago  Karma: 166
How does DelegateCall work?
  • Is there an equivalent of gas in the DC dAppChain? What token is it paid in?
  • Users can log in with Google or GitHub. Where are private key stored? Are transactions signed by the web app?
  • What is the process for redeeming Karma for DelegateCall tokens on the Ethereum mainnet?
#DelegateCall

2 ANSWERS
luke2
9 months ago Karma: 1864
  1. DelegateCall runs on DAppChain tech, which is our own blockchain that has its own custom ruleset. It's pair to a smart contract on Mainnet but doesn't run on the EVM. So there's no concept of gas. Validators earn block rewards (paid in delegatecall tokens).

  2. The github/google oAuth is separate from the Blockchain and is used to make UX friendly and remove spam. You are signing transactions in your browser everytime you do something.

  3. Transfer Gateway will be announced later.

  1. DelegateCall runs on DAppChain tech, which is our own blockchain that has its own custom ruleset. It's pair to a smart contract on Mainnet but doesn't run on the EVM. So there's no concept of gas. Validators earn block rewards (paid in delegatecall tokens).

  2. The github/google oAuth is separate from the Blockchain and is used to make UX friendly and remove spam. You are signing transactions in your browser everytime you do something.

  3. Transfer Gateway will be announced later.

flyq951

Can I be the one of node of loom dapp blockchain?

Mar 15 '18 at 4:01 pm
dtaparelli

"2. You are signing transactions in your browser ..." just to be more precise, the actual signed transactions are sent to the blockchain by delegatecall server, triggered by your actions in the browser. You are not really signing them in your browser

Mar 16 '18 at 1:34 am
luke2

That's totally false. Loom.js is running on every page load and behaves like metamask. Your transactions are reaching the blockchain directly. Just inspect the out going requests on your browser.

Mar 16 '18 at 5:33 am
liu.liuwei.wei

Is the content stored on blockchain?

Mar 16 '18 at 8:12 am
crzndx

Yes, this website is nothing more than a block explorer @liu.liuwei.wei

Mar 17 '18 at 2:44 pm
aleksandr.siman

@luke2 you said that transactions get signed right in a browser, so where is private key stored in order to sign txs?

Apr 28 '18 at 9:45 am
hieuhc58

I don't have metamask extension on my browser, so how can I post answer and also receive karma, if I don't have account on chain?

Sep 28 '18 at 9:31 am
bro29

@hieuhc58: DelegateCall works like it has a mini-metamask application embedded in the website itself, so no user needs the Metamask extension to interact with the DelegateCall site. This means that DelegateCall knows the private key that is assigned to your user; usually that's a big no-no (a key point of Metamask being a separate extension is that it does not let the websites you visit see your private key directly), but in this case it's okay since the private key is only being used on a Loom sidechain, not the main Ethereum blockchain. However, there is a link to the main Ethereum blockchain (you can convert your DelegateCall karma into real Ethereum tokens), which if you want to do that option, you DO need Metamask installed.

@aleksandr.siman: Your private key on DelegateCall is generated when you first visit and stored in the localStorage cache in your browser. If you use the "Login" functionality on DelegateCall, they save your private key on their central server, to be able to restore it when you log into another browser with your same username. That's not as secure as your private key never leaving your possession, but since it's a separate private key used only by the DelegateCall site, none of your "real" funds on the main Ethereum blockchain are at risk.

Nov 30 '18 at 1:00 pm
zayds
7 months ago Karma: 1607

You are signing transactions in your browser ..." just to be more precise, the actual signed transactions are sent to the blockchain by delegatecall server, triggered by your actions in the browser. You are not really signing them in your browser.

You are signing transactions in your browser ..." just to be more precise, the actual signed transactions are sent to the blockchain by delegatecall server, triggered by your actions in the browser. You are not really signing them in your browser.

Earn tokens by posting and answering questions about blockchain!
Karma to eth
YOUR ANSWER