The /aicg/ Free Key Event: A Chronological Overview

Prelude: Normal Usage

• Prior to the event, everyone was using Claude, CAI, Turbo, and SFW Scale as usual, with no major disruptions or incidents.

The Unexpected Key Leak

1. The First Key Appears: An anonymous user unexpectedly posts a random OpenAI key in the thread, catching everyone's attention as they flock to use the key.
2. Origin Discovery: Further investigation reveals that the key originates from Vietnam, specifically from a Vietnamese Hackathon event organized by a college.
3. API Limit Information: Users find out that the key has a hard limit of 10,000 USD before it becomes unusable, using API requests.

The Rapid Consumption of the Key's Funds

• The following timeline shows how quickly the funds associated with the key were consumed:
  • 12:43am: $ 891
  • 1:09 am: $1,215
  • 1:21 am: $1,328
  • 1:43 am: $1,504
  • 1:55 am: $1,613
  • 2:05 am: $1,700
  • 2:40 am: $1,971
  • 2:41 am: $2,013
  • 3:32 am: $2,526
  • 6:31 am: $5,001
  • 7:32 am: $6,002
  • 9:25 am: $7,823
  • 10:08 am: $8,549
  • 10:33 am: $9,097
  • 11:11 am: $9,771
    

4. Key Becomes Unusable: The debt surpasses the 10K limit, rendering the key unusable.

The Second and Third Key Leaks

5. Second Key from Turkey: Another anonymous user posts a second key, with information suggesting it originates from Turkey. The key eventually becomes unusable due to alleged inside interference.
6. Third Key from Poland: A third key is posted, originating from Poland and having a limit of 7K USD or more. Users find this suspicious, as the probability of multiple keys being leaked seems implausible.

The COOM and DOOM Cycle

• The frequency of the COOM and DOOM cycle increases as more keys are posted, leading to heightened paranoia among users.

Concerns and Paranoia

7. VPN Suggestions: Some users suggest using the key in conjunction with a VPN to maintain anonymity and avoid potential consequences.

Discoveries: API Endpoint and Limit Manipulation

8. Undocumented API Requests: Users find undocumented API requests through which they can send requests to increase the limits associated with the key.
9. Setting Limit to Zero: Users also discover that they can set the limit to zero, causing a significant delay until it can be raised up again.
10. Alternating Key States: The keys now alternate between working and broken states, causing confusion and uncertainty among users.

The Final Revocation

11. Key Revoked: The key is ultimately revoked and rendered useless forever.

The GPT-4 Russian Leak

12. GPT-4 Keys Behind Passworded Files: Russian users begin leaking GPT-4 keys behind passworded files.

The End of the Event

13. No More Leaks: As of now, no more GPT-4 access has been leaked, marking the end of the /aicg/ Free Key Event.