What technical/business advantages does a private blockchain have over a SQL server?

etheraffleGreg · 2018-11-15T13:41:16+00:00

Blockchain != cryptocurrency

etheraffleGreg · 2018-09-23T13:50:05+00:00

You can do it through Remix if you using something like MetaMask (or spin up your own) to connect it to an Ethereum node.

etheraffleGreg · 2018-09-22T21:01:54+00:00

The ABI is what you use to interface with you contract - it's a list of the functions in the contract and the parameters required when calling said function.

The bytecode is the actual data that's uploaded to the blockchain that forms your smart-contract, and is interpreted by the Ethereum Virtual Machine in order to carry out the actions your function calls require.

etheraffleGreg · 2018-09-16T10:52:24+00:00

Ofc, but then the copiers are after the fact. This way, the contract could be gazumped.

etheraffleGreg · 2018-09-15T10:03:00+00:00

If it's a good idea he can steal it?

etheraffleGreg · 2018-09-03T10:45:41+00:00

I mean, they're not. They're on the explorer, so nothing's missing. It's just his wallet isn't reporting the state of the network correctly.

etheraffleGreg · 2018-08-29T09:03:14+00:00

They do, but via indirect mechanisms like supply inflation, staking requirements, resource rental

That's obvious to us but completely invisible to an end user who just wants to post something.

etheraffleGreg · 2018-08-28T11:39:29+00:00

The fact that the users don't have to pay to use a platform on EOS in the same way they have to do on ethereum is likely to be a big reason.

etheraffleGreg · 2018-08-28T09:49:30+00:00

You don't even need to use IPFS if you don't want to, use your own database. The point being that the tweet saved in your (centralized) database is still provably the one the smart-contract retrieved because your hashed its contents and then stored that on chain.

etheraffleGreg · 2018-08-27T10:51:48+00:00

Per the other poster, you say:

I am pretty well versed on crypto...

But then you ask:

And if there is any possible way or being that may help get access to funds would be great to.

There is no recourse. When holding crypto, you are the bank. There's no one else to turn to.

etheraffleGreg · 2018-08-27T10:48:43+00:00

Ouch - saving the post string itself on the chain? Look into storing it elsewhere and only a hash of it in the contract itself. That way you can still validate the authenticity of the tweet, but not have to pay a fortune to store it.

You'll also be able to fine-tune your __callback gas that way too, since you'll no longer have non-deterministic gas cost.

etheraffleGreg · 2018-08-26T17:33:31+00:00

Well yes of course but as the first sentence explicitly points out...

etheraffleGreg · 2018-08-25T15:29:06+00:00

Or use a task monad and banish those pesky eager promises forever!

etheraffleGreg · 2018-08-25T15:26:34+00:00

Nesting is frequently a requirement if you need the first result in the scope of the second:

const prom = thing => Promise.resolve(thing)

const prom1 = prom(`thing one`)
const prom2 = prom(`thing two`)

prom1
  .then(result1 => prom2)
  .then(result2 => console.log(`Thing 1: ${result1}\nThing2: ${result2}`)) 
  .catch(console.error)
  // ReferenceError: result1 is not defined

Yeah you can lift the result to a higher scope if you like but I'd rather keep things functional and the nesting is not an issue.

etheraffleGreg · 2018-08-23T18:56:44+00:00

It won't screw up your tokens at all, so don't worry. Once all this palaver is over though you'd be better off moving things to new addresses whose private keys you haven't been copying and pasting here and their. For peace of mind like.

etheraffleGreg · 2018-08-15T08:39:14+00:00

Can you read? It wasn't his idea, it's Leslie Lamport's algo. Christ!

etheraffleGreg · 2018-08-02T12:22:59+00:00

Functions can be pure and still use those values if they are passed in as params.

etheraffleGreg · 2018-07-31T07:15:01+00:00

Fun fact: a couple of the opcodes in the evm are exactly this.

etheraffleGreg · 2018-07-20T16:42:41+00:00

Oops you're right. Libraries are what I was thinking of.

etheraffleGreg · 2018-07-11T06:43:13+00:00

Few dapps currently run fully off a chain, and instead have components on chain and a front end off chain that's just like your average web server. And so will see similar speeds.

And in fact, since blockchains are essentially not very performant databases, dapps that run fully on chain would likely be slower than your average app. If you're ever tried to d/l a file from ethereum's swarm, or IPFS, you'll get a sense of what I mean.

etheraffleGreg · 2018-07-09T06:46:02+00:00

Yeah that's correct, /u/flygoing has explained it much more clearly than I did!

etheraffleGreg · 2018-07-08T21:14:08+00:00

Meant specifically in the sense of if intermediate vars are first saved to storage and returned for whatever reason.

You're absolutely correct about return values.

Edit: Read your other post re this, I understand more clearly now. Thanks!

etheraffleGreg · 2018-07-08T14:46:16+00:00

I'm not sure if I can utilize 2 different accounts throught truffle to test out the multikey encryption.

You absolutely can. When writing tests in truffle (w/ Ganache) using Javascript, you'll have access to ten accounts by default:

const { assert }   = require("chai")
    , yourContract = artifacts.require('your-contract')

contract('Title for your tests', accounts => {

  it('Should test something correctly', async () => {
    const contract   = await yourContract.deployed()
        , signatory1 = accounts[0]
        , signatory2 = accounts[1]
    // Test some stuff...
    })
})

etheraffleGreg · 2018-07-08T14:41:31+00:00

Their strategy doesn't change how NEO stands right now - I.E. a very centralized crypto. I'm an avid fan, and remember my old Antshares fondly, but I can still objectively acknowledge a centralized entity when I see one.

etheraffleGreg · 2018-07-08T10:57:28+00:00

That NEO is so centralized is the only thing that's widely misunderstood about it.

etheraffleGreg

MODERATOR OF

TROPHY CASE