Price prediction thread

EOY $0.3
2021/02 $1
2021/06 $3

Attached: GRT.jpg (400x400, 16.06K)

When projects start fomoing in, the sky is the limit. Especially all those defi shitcoins with money to burn.

Do projects using the graph need the token

why would defi fomo in? defi is dead, and even if it weren't, why would they buy in their token

Unless they're ready to run their own server and manage their own data, they have no choice but to buy GRT. For most of them it will be cheaper anyway.

Crap like 88mph is built on The Graph and it's at a $7m cap. There is so much dumb money floating around that it's easier for them just to pay someone else

I don't understand the first part. How is using the graph actually incentivized? Why not build your own server and fetch the data from the smart contract, seems just about as much effort, you just need to put it on AWS and cover the costs for that. Why pay essentially for a subscription?

at listing $0.3
one week after $1
two weeks after $3
2 months after $1.3
6 months after $0.7
12 months after $3.5

WHEN WILL IT BE RELEASED

maybe December

EOY IT RELEASES

>why not build your own oracle
>literally a json parser
>*insert a tech company/bank name here* will make chainlink obsolete
same will happen here

I didn't participate in the 2017 bread crumbs. I get why you can't build your own oracle, but this is different. Why not deploy your own server and track the data you need? Why pay a subscription fee to a particular subgraph who may later modify the schema and fuck up the data you're relying on? Genuinely trying to understand

The incentive is accessibility. Anyone with a basic understanding of GraphQL can work The Graph, else you just end up hiring someone else to keep everything running after importing parts of a smart contract.

>EOY $0.3
nice fud

x10 listing dickface

Not sure I understand. What you're pointing at is that it's more expensive to house an internal developer that's in charge of integration than to rely on The Graph's community? I'm not sure sure. Say you're a project developing a product and you want the data from smart contracts. I'm sure the guy in charge of deploying smart contract relaying any changes he made and updating the server code as well is cheaper than just throwing your money at a particular subgraph.

1. same as for chainlink the data is decentralized
2. it's timesaving for devs to use it
To be fair we're not even talking about possible adoption here. If all the projects from binance and uniswap to coingecko and compund using it then it's good enough. It's not speculation at this point, the market has decided already.

An engineer on the team would be the one creating the subgraph, and it is up to curators to signal on it. The project is not beholden to the curator as the curator has no incentive to signal on a subgraph that has no queries. Plus the engineer only needs a basic understanding to build and maintain it.

Yeah seems a bit weird to be having the "not sure anyone will use it" argument about a project that everyone is using already.

Already 10B queries on a monthly basis. It's one of the few projects that isn't VAPORWARE. To be fair this project will be valuated equally to LINK.

conservative but accurate. I think 12mos we are peaking 12-15 personally. Total crypto mc will be 1T+ and this will be in the top 5 with 15-20B mc

user your thread the other day about Graph valuation and potential got posted in Cronje and Ivan telegram group (I got to first know Graph from there a year ago), Developers criticized your high query fee pricetag, 0.01$ is too high, I agree with that.

Regardless i think even if Graph charge 0.0001$ query fees (Extremely cheap) they should still be among the top 5-10 by revenue. In reality fees are likely to be between 0.0001-0.002$.

i agree, query fee at $0.01 is a bit too steep. But still 1 of the best projects there indeed. What is your price prediction>?

The current adoption was the main reason why I'm interested, even some minor defi project literally no one heard about used some TheGraph requests that I had to reenable in uMatrix. I know there's a fault in my logic I just don't see it just yet.

can you explain like I'm like a complete brainlet why the engineer would rather build a subgraph than build and host his own server?

if the engineer builds his own server that will take away the whole point of a decentralized querying protocol. Doesn't it?

Will those projects stick around after Graph become decentralized and charge fees tho? Tho i guess if some leave Graph could compensate on that with new projects onboard, their growth is really impressive.

How important is that the data indexed will be decentralized tho? Because this will be Graph main selling point after full network launch (Rightnow it's not fully decentralized), Does the same Chainlink logic apply here ("Decentralization will win in the end")?

I get your point, but keep in mind it's all about the narrative. Because in the end, how important is decentralization really besides censorship resistance?

Wtf is this shit actually going to generate possibly 10m in fees monthly?

>that will take away the whole point of a decentralized querying protocol.
I can buy that argument, but this user makes a fair point. You need decentralization when you're putting data on-chain because you need to trust that source data isn't manipulated. But once that data is on-chain, do you really need a decentralized source of indexed data? You could definitely make that argument if everyone is untrustworthy by default and users of a 3rd party project would rather rely on a decentralized indexer like a subgraph instead of project's centralized source that can be manipulated. I understand this a bit better now so thanks for that. We'll just have to see how this evolves down the road. Also, checked.

It's the difference between one company doing the work of finding, sorting, indexing and maintaining subgraphs, or creating an incentivised ecosystem where any technologically competent participant can join and profit.

well additionally the graph will allow for applications to be server-less. This is important for ease of use, ease of deployment and reduced costs