[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance


View post   

File: 318 KB, 1080x1728, 20180725_063128.jpg [View same] [iqdb] [saucenao] [google]
10412452 No.10412452 [Reply] [Original]

Not trying to fud, but I'm wondering what they meant by this.

>which are then paid using a preferred form of payment

Sirgay was asked at SXSW if node operators would be paid in Link, and he said they would.

>> No.10412460

>>10412452
They obviously changed it. How are you going to get paid in Link on Hyperledger?

>> No.10412464

>>10412460
I would like to amend that to say that he didn't specify they would be paid ONLY in Link. Node Operators would be paid in whatever the preferred method was that could be Link.

Its quite a dick punch.

>> No.10412479

>>10412452
Questions like this are for the Slack or some other way to reach the actual people behind the project. I don't see how /biz/ speculation would put this to rest.

>> No.10412509

It's hard to say what they're talking about here. Is it talking about the payment to the API provider that the node operator has to pay if it's a paid API, which is obviously not in LINK, or is it talking about the payment that the smart contract is written in to fulfill?

It really doesn't seem like the payment to a node operator would be in anything except link because of the code they already have, the UI they've already created that shows your link balance, and the functionality of the token. I'd chalk this up to poor wording (which isn't surprising given all the typos) and ask in the slack.

>> No.10412523

This has come up before: the person is paid by converting LINK into their preferred form of payment.

>> No.10412535

>>10412523
customers will be invoiced using request, and receive the payment how they please

>> No.10412558
File: 105 KB, 666x660, 1523920801461.jpg [View same] [iqdb] [saucenao] [google]
10412558

API requests/smart contract services can be payed for with any currency. When the end user pays for API data/SC services with USD for example. That USD is taken and exchanged for LINK at its current market price, then a portion is paid to the node operator/network etc.
Can you imagine multimillion dollar companies paying for smart contracts with their USD which in turn lands back in their pockets due to the fact Sergey gave them loads of LINK tokens which will only go up in value with network effect. the whole thing perpetuates, big business had an easy adoption as they never had to front big risky money to adopt a more efficient system.

>> No.10412566
File: 134 KB, 1152x693, Swift.jpg [View same] [iqdb] [saucenao] [google]
10412566

It's obvious that you'll be able to get paid in USD through swift. Pic very related

>> No.10412574

>>10412452
It's talking about paying the APIs, not the nodes. Brainlet.

>> No.10412585
File: 48 KB, 640x778, 1519511288012.jpg [View same] [iqdb] [saucenao] [google]
10412585

>>10412574
apis are paid for by the node operator.
with the fuck ton of money they'll be making.

>> No.10412604

>>10412558
Brainlet here, where does the Link come from in the USD/Link conversion. I guess it's the same question I have when Req is brought up. Is there an exchange setup just for these types of transactions?

>> No.10412615

>>10412604
Chainlink will unironically allow for decentralized fiat-crypto exchanges.

>> No.10412752

>>10412604
it will be purchased on the open market (exchanges), link holders will then decide the price.. and see >>10412615

>> No.10412758

>>10412615
even if there is not a direct LINK/USD pairing yet, the system will convert USD to ETH to LINK

>> No.10413129

>>10412566
Yup and SWIFT automatically routes the payment while using LINK to pay nodes and post collateral. Anons here don’t quite grasp how big SWIFT is. But to be fair the vast majority of people in finance don’t really understand SWIFT either unless you work on the backend and payments related shit

>> No.10413667

>>10412452
>request
>request

>> No.10413684

>>10412535
>>10413667
This