[ 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.54750522 [View]
File: 17 KB, 425x283, 11.jpg [View same] [iqdb] [saucenao] [google]
54750522

>>54750427
11 cents

>> No.53523213 [View]
File: 17 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
53523213

>>53523169
>>53523179
>>53523183
damn looks like you guys really pissed em off
whatever you do, don't point out to them that they're basically worse than biz jannies because they spend hundreds of hours obsessing and seething over a token they don't hold FOR FREE
makes em even madder

>> No.53433700 [View]
File: 17 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
53433700

>>53432739
>seethes at link
>still hasnt figured out how filters work

>> No.53376389 [View]
File: 17 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
53376389

>>53375576
Wait... are you that guy in that other thread calling people "incel cucks" while posting your collection of chastity cages?

>> No.53375572 [View]
File: 17 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
53375572

>>53372584
"Shut up incel cuck" - guy with a folder filled with chastity cages

>> No.53354264 [View]
File: 17 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
53354264

>>53354230
>one day of work making fud spammers kvetch for laughs
Vs
>spending all day every day angrily fudding a token you dont hold before being ousted as a mentally ill coomer or reject
yeah the archive anon is definitely the loser in this situation
Thanks for correcting the record

>> No.53345781 [View]
File: 17 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
53345781

>>53345671
Holy shit my sides are in orbit right now
Its not hard for linkchads to win when all their enemies are fucking losers apparently KEK

>> No.49642809 [View]
File: 17 KB, 425x283, 1629754455711.jpg [View same] [iqdb] [saucenao] [google]
49642809

OIL BARONS

>> No.24911925 [View]
File: 18 KB, 425x283, ab8-2.jpg [View same] [iqdb] [saucenao] [google]
24911925

>school
>partner
>office
>dollars
AHAHAHAHHAHAHAHAHAHHAHAHAHHAHAHAHHAHAHAHHAHHAHAHAHAHAHHAHAHHAHAHAHAHHAHAHHAHAHAH FAAAGGGOOOOOOOTTTTT AHAHHAHAHAHAHAHAHHAHAHAH

>> No.24468899 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
24468899

>>24468872

>> No.24409739 [View]
File: 18 KB, 425x283, 600.jpg [View same] [iqdb] [saucenao] [google]
24409739

Bullrun has begun boys

>> No.21781886 [View]
File: 18 KB, 425x283, 1597803497952.jpg [View same] [iqdb] [saucenao] [google]
21781886

>>21779272
>believing /biz/
joke's on you, newfag

>> No.21614538 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
21614538

Kek he thought we were going up

>> No.21609767 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
21609767

Massive loads of 700K are transferred to binance and Sergey Livestreams his dump from a new golden toilet

>> No.21596392 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
21596392

>>21596251
Imagine holding a token that's dev team gets called LESS transparent than a team that dumps monthly on their community

My sides...
Oh sweet Jesus my sides
AHHHHHHAHAHAHAHAHAHAHAHAHAHAHAHA

>> No.21503154 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
21503154

>>21502586

>> No.19733804 [View]
File: 18 KB, 425x283, 1549755834302.jpg [View same] [iqdb] [saucenao] [google]
19733804

Please, lets all take a moment to point and laugh at all the bears that bought puts against SPY this morning and thought it was going to keep going down only to find out that they've lost all of their money

>> No.19201703 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
19201703

>>19201292
Friendly reminder PIVX was suspected of knowing a bug existed and took advantage of it to make forgeries of their own token to profit

https://cointelegraph.com/news/pivx-possibly-other-pos-chains-vulnerable-to-bug-attackers-profit

>Accusations against the PIVX team

>Moreover, the firm noted that "what's worse is that PIVX has known that this bug was not fixed and has kept quiet to themselves."
>The author of the report claims that he contacted the PIVX core developers and has been told that there was no other solution than waiting for an update which would be issued in the third quarter of the current year.

>He also says that after he managed to contact PIVX members directly and asked about information concerning an address which was exploiting the vulnerability in question, he obtained no answer and the attack stopped.

>> No.19201588 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
19201588

>>19199392
Friendly reminder PIVX was suspected of knowing a bug existed and took advantage of it to make forgeries of their own token to profit

https://cointelegraph.com/news/pivx-possibly-other-pos-chains-vulnerable-to-bug-attackers-profit

>Accusations against the PIVX team

>Moreover, the firm noted that "what's worse is that PIVX has known that this bug was not fixed and has kept quiet to themselves."
>The author of the report claims that he contacted the PIVX core developers and has been told that there was no other solution than waiting for an update which would be issued in the third quarter of the current year.

>He also says that after he managed to contact PIVX members directly and asked about information concerning an address which was exploiting the vulnerability in question, he obtained no answer and the attack stopped.

>> No.19201483 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
19201483

>>19201340
Friendly reminder PIVX was suspected of knowing a bug existed and took advantage of it to make forgeries of their own token to profit

https://cointelegraph.com/news/pivx-possibly-other-pos-chains-vulnerable-to-bug-attackers-profit

>Accusations against the PIVX team

>Moreover, the firm noted that "what's worse is that PIVX has known that this bug was not fixed and has kept quiet to themselves."
>The author of the report claims that he contacted the PIVX core developers and has been told that there was no other solution than waiting for an update which would be issued in the third quarter of the current year.

>He also says that after he managed to contact PIVX members directly and asked about information concerning an address which was exploiting the vulnerability in question, he obtained no answer and the attack stopped.

>> No.19201268 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
19201268

>>19199717
Friendly reminder PIVX was suspected of knowing a bug existed and took advantage of it to make forgeries of their own token to profit

https://cointelegraph.com/news/pivx-possibly-other-pos-chains-vulnerable-to-bug-attackers-profit

>Accusations against the PIVX team

>Moreover, the firm noted that "what's worse is that PIVX has known that this bug was not fixed and has kept quiet to themselves."
>The author of the report claims that he contacted the PIVX core developers and has been told that there was no other solution than waiting for an update which would be issued in the third quarter of the current year.

>He also says that after he managed to contact PIVX members directly and asked about information concerning an address which was exploiting the vulnerability in question, he obtained no answer and the attack stopped.

>> No.19201166 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
19201166

>>19199006
Friendly reminder PIVX was suspected of knowing a bug existed and took advantage of it to make forgeries of their own token to profit

https://cointelegraph.com/news/pivx-possibly-other-pos-chains-vulnerable-to-bug-attackers-profit

>Accusations against the PIVX team

>Moreover, the firm noted that "what's worse is that PIVX has known that this bug was not fixed and has kept quiet to themselves."
>The author of the report claims that he contacted the PIVX core developers and has been told that there was no other solution than waiting for an update which would be issued in the third quarter of the current year.

>He also says that after he managed to contact PIVX members directly and asked about information concerning an address which was exploiting the vulnerability in question, he obtained no answer and the attack stopped.

>> No.19201048 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
19201048

>>19198073
Friendly reminder PIVX was suspected of knowing a bug existed and took advantage of it to make forgeries of their own token to profit

https://cointelegraph.com/news/pivx-possibly-other-pos-chains-vulnerable-to-bug-attackers-profit

>Accusations against the PIVX team

>Moreover, the firm noted that "what's worse is that PIVX has known that this bug was not fixed and has kept quiet to themselves."
>The author of the report claims that he contacted the PIVX core developers and has been told that there was no other solution than waiting for an update which would be issued in the third quarter of the current year.

>He also says that after he managed to contact PIVX members directly and asked about information concerning an address which was exploiting the vulnerability in question, he obtained no answer and the attack stopped.

>> No.19200868 [View]
File: 18 KB, 425x283, ab8.jpg [View same] [iqdb] [saucenao] [google]
19200868

>>19200194
Friendly reminder PIVX was suspected of knowing a bug existed and took advantage of it to make forgeries of their own token to profit

https://cointelegraph.com/news/pivx-possibly-other-pos-chains-vulnerable-to-bug-attackers-profit

>Accusations against the PIVX team

>Moreover, the firm noted that "what's worse is that

>PIVX has known that this bug was not fixed and has kept quiet to themselves."
>The author of the report claims that he contacted the PIVX core developers and has been told that there was no other solution than waiting for an update which would be issued in the third quarter of the current year.

>He also says that after he managed to contact PIVX members directly and asked about information concerning an address which was exploiting the vulnerability in question, he obtained no answer and the attack stopped.

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