[ 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

Search:

View post   
>> No.12377540 [View]
File: 440 KB, 600x387, 1522251800173.png [View same] [iqdb] [saucenao] [google]
12377540

>>12377351
>can u even explain what "V2

V2 is the software infrastructure that allows them basically to implement most of the functionality outlined in the White Paper.

If you're looking for the code, I don't think it's released yet.

They discovered that the V1 was not user friendly and required an Eth balance and was clumsy for non crypto users, so it was abandoned and allowed them to develop what we hope is something that will be the final product.

The learning curve was steep for these guys, but they have hired a lot of developers and have been working this whole year, so I think the future is looking good.

>> No.9657514 [View]
File: 440 KB, 600x387, 1522345366093.png [View same] [iqdb] [saucenao] [google]
9657514

>> No.9560738 [View]
File: 440 KB, 600x387, 1522251211595.png [View same] [iqdb] [saucenao] [google]
9560738

Whats stopping us from just sending ETH to this address and burning large amounts of REQ thus creating an artificial burn ratio?

>https://etherscan.io/address/0x3038045cd883abff0c6eea4b1954843c0fa5a735

This is what happened yesterday. Someone sent 0.5 ETH to the address prompting a 2K REQ burn.

>> No.9156979 [View]
File: 440 KB, 600x387, req1.png [View same] [iqdb] [saucenao] [google]
9156979

i dont know anymore, i lost all hope

>> No.8967794 [View]
File: 440 KB, 600x387, 1522345366093.png [View same] [iqdb] [saucenao] [google]
8967794

>> No.8818838 [View]
File: 440 KB, 600x387, 1522251211595.png [View same] [iqdb] [saucenao] [google]
8818838

Damn link kids...ruining REQ for everyone. When is Sergey putting that chain online? Next year?

>> No.8731468 [View]
File: 440 KB, 600x387, req1.png [View same] [iqdb] [saucenao] [google]
8731468

people are preparing for the bithumb listing

>> No.8728917 [View]
File: 440 KB, 600x387, 1522251211595.png [View same] [iqdb] [saucenao] [google]
8728917

$100 EoY

>> No.8665153 [View]
File: 440 KB, 600x387, req1.png [View same] [iqdb] [saucenao] [google]
8665153

EOY 2.3$ get

>> No.8655188 [View]
File: 440 KB, 600x387, 1522251211595.png [View same] [iqdb] [saucenao] [google]
8655188

Since going live on Mainnet.
REQ has burned 45.7793301344 tokens so far.

$100 EOY confirmed

>> No.8642628 [View]
File: 440 KB, 600x387, 1522190844795.png [View same] [iqdb] [saucenao] [google]
8642628

So if the req fud true? I really want to invest now because the mainnet will come out but I here all the fud about the token burn.

So here's my question? If req is really poorly designed and has this burning bug, should I not sell before mainnet? What is the percentage that my coins reqs burn vs what is my moon gains?

I just want a better understandment.

>> No.8627852 [View]
File: 440 KB, 600x387, 1522251211595.png [View same] [iqdb] [saucenao] [google]
8627852

Agreed

>> No.8612238 [View]
File: 440 KB, 600x387, req1.png [View same] [iqdb] [saucenao] [google]
8612238

>>8612157
what the fuck? use the right one bro

>> No.8605177 [View]
File: 440 KB, 600x387, 1522251211595.png [View same] [iqdb] [saucenao] [google]
8605177

Mainnet Live?
The official post will probably be in the Friday bi-weekly. Sneaky bastards slipped it past us. Time to Dump.

RequestEthereum:
>https://etherscan.io/address/0x3038045cd883abff0c6eea4b1954843c0fa5a735#code

RequestCore:
>https://etherscan.io/address/0xdb600fda54568a35b78565b5257125bebc51eb27#code

REQ Burning:
>https://etherscan.io/tx/0x5120f3cd62e6797184fa6ca7d5efc0ba3fe289c896c2cba680225ac3dbb08570

>> No.8604987 [View]
File: 440 KB, 600x387, req1.png [View same] [iqdb] [saucenao] [google]
8604987

>>8604819
smart

>> No.8593361 [View]
File: 440 KB, 600x387, req1.png [View same] [iqdb] [saucenao] [google]
8593361

>>8591839

Navigation
View posts[+24][+48][+96]