Rows:
| CHALLENGE | AUTHORS | SOLVES (CURRENT) | SOLVE RATE (AT CONTEST TIME) |
|---|---|---|---|
WelcomeMisc | 895solves | - | |
Simple LoginWeb | 381solves | Top 28%= 84/300 users | |
echoPwn | 250solves | Top 32%= 56/174 users | |
182solves | Top 15%= 71/458 users | ||
qrimeCrypto | 180solves | Top 38%= 91/239 users | |
Country DBWeb | 154solves | Top 33%= 246/729 teams | |
inboundPwn | 146solves | Top 28%= 57/197 users | |
masking tapeRev | 115solves | Top 19%= 61/316 users | |
before-writePwn | 111solves | - | |
catcpyPwn | 106solves | Top 20%= 41/197 users | |
91solves | Top 15%= 42/279 users | ||
Alpaca PollWeb | 90solves | Top 9%= 42/458 users | |
hexechoPwn | 89solves | Top 15%= 27/174 users | |
Rainbow Sweet AlchemistCrypto | 89solves | Top 17%= 42/239 users | |
OysterPwn | 67solves | Top 42%= 40/95 users | |
CaaSWeb | 64solves | Top 4%= 13/300 users | |
Pico Note 1Web | 59solves | Top 3%= 10/300 users | |
A Dance of Add and MulCrypto | 59solves | Top 12%= 30/239 users | |
writePwn | 58solves | - | |
XOR-CBCCrypto | 57solves | - |
Rows:
I made a blog service consists of two servers: API server and Frontend server. The former provides APIs that you can see, add, or modify posts. The latter uses responses from API server and render it.
If you could get 1,000,000,000,000 likes on your post, I will give you the flag. The maximum number of likes is 5,000, though.
