{
  "id": 351801,
  "title": "Competition End",
  "url": "/competitions/ai-village-ctf/discussion/351801",
  "author_name": "",
  "post_date": "2022-09-12T00:03:43.108388200Z",
  "votes": 26,
  "comment_count": 3,
  "views": 0,
  "content": "<p>The AI Village CTF at Defcon 30 is officially over. Congrats to the winners and everyone who learned something new! We’d like to thank Kaggle for their incredible platform, support, and sponsorship. The platform handled the classic security capture-the-flag (CTF) format with ease and brought an awesome community with it. Thank you to everyone who donated their time and challenges. Joe and I would also like to thank NVIDIA for the time and unwavering support to build and support this event throughout.</p>\n<p>We’d also like to thank <strong>YOU</strong>, the participants. When building this CTF we guessed that maybe 20 people would play, but certainly no more than 200. We ended with 670+ participants with 4000+ entries, which heavily exceeded our expectations. Thank you for being patient with us while we fixed issues that came up (token servers). Thank you for being good-sports with regards to hints, we know this was a different type of challenge for the ML community but we hope you had fun with it.</p>\n<p>Finally, thank you for teaching us - you gave us feedback with the questions you asked, frustrations you expressed, and solutions you shared. Not only do we have a list of things to improve on for next year, but I personally learned a lot about how I can approach attacking models differently in my own day-to-day. If you’d like to be involved next year or think a similar event would be a good addition to one of your events, send us an email at <strong>ctf@aivillage.org</strong>.</p>\n<p>With that said, this competition was ultimately about education and community building. As machine learning continues to make its way into our daily lives through core business processes, medical decisions, cyber security, loan approvals, policing, energy management, self-driving, etc. It’s important we develop and teach the skills necessary to enumerate, communicate, and manage the risks inherent in ML systems. This was just one event from the AI Village. We encourage you to stick around the Discord and find other channels that might interest you throughout the year.</p>\n<p><strong>FAQ</strong></p>\n<p><strong>Will you release the challenge containers used for the competition?</strong></p>\n<p>All the challenges were donated and the AI Village doesn’t own them. We are leaving it up to the authors to open-source them if they so choose. If/when authors post their challenges, we’ll update this post with links. The servers will be turned off on September 16th.</p>\n<p><strong>Will you be back next year?</strong></p>\n<p>We certainly hope so. Your feedback will help shape future iterations (<a href=\"https://www.kaggle.com/competitions/ai-village-ctf/discussion/346451)\" target=\"_blank\">https://www.kaggle.com/competitions/ai-village-ctf/discussion/346451)</a>. This event was only possible with support from Kaggle and the village.  We welcome your contributions (as players, challenge authors, or organizers next year). Your experience and any interesting approaches might also be good candidates for presenting at the village next year! Keep an eye out for the call-for-proposals on our twitter: <a href=\"https://twitter.com/aivillage_dc\" target=\"_blank\">https://twitter.com/aivillage_dc</a>.</p>\n<p><strong>Can we post blogs of our solutions?</strong></p>\n<p>Absolutely, we'd be disappointed if you didn't. You’re welcome to post standalone blogs, blogs as Kaggle discussions, and make your notebooks public. Let us know you do so we can read them! By September 25th, we’ll review the Kaggle discussion board and any blog links you send. Particularly insightful or interesting authors will be eligible for some swag!</p>",
  "messages": [
    {
      "id": "1935200",
      "postDate": "09/12/2022 00:03:43",
      "content": "<p>The AI Village CTF at Defcon 30 is officially over. Congrats to the winners and everyone who learned something new! We’d like to thank Kaggle for their incredible platform, support, and sponsorship. The platform handled the classic security capture-the-flag (CTF) format with ease and brought an awesome community with it. Thank you to everyone who donated their time and challenges. Joe and I would also like to thank NVIDIA for the time and unwavering support to build and support this event throughout.</p>\n<p>We’d also like to thank <strong>YOU</strong>, the participants. When building this CTF we guessed that maybe 20 people would play, but certainly no more than 200. We ended with 670+ participants with 4000+ entries, which heavily exceeded our expectations. Thank you for being patient with us while we fixed issues that came up (token servers). Thank you for being good-sports with regards to hints, we know this was a different type of challenge for the ML community but we hope you had fun with it.</p>\n<p>Finally, thank you for teaching us - you gave us feedback with the questions you asked, frustrations you expressed, and solutions you shared. Not only do we have a list of things to improve on for next year, but I personally learned a lot about how I can approach attacking models differently in my own day-to-day. If you’d like to be involved next year or think a similar event would be a good addition to one of your events, send us an email at <strong>ctf@aivillage.org</strong>.</p>\n<p>With that said, this competition was ultimately about education and community building. As machine learning continues to make its way into our daily lives through core business processes, medical decisions, cyber security, loan approvals, policing, energy management, self-driving, etc. It’s important we develop and teach the skills necessary to enumerate, communicate, and manage the risks inherent in ML systems. This was just one event from the AI Village. We encourage you to stick around the Discord and find other channels that might interest you throughout the year.</p>\n<p><strong>FAQ</strong></p>\n<p><strong>Will you release the challenge containers used for the competition?</strong></p>\n<p>All the challenges were donated and the AI Village doesn’t own them. We are leaving it up to the authors to open-source them if they so choose. If/when authors post their challenges, we’ll update this post with links. The servers will be turned off on September 16th.</p>\n<p><strong>Will you be back next year?</strong></p>\n<p>We certainly hope so. Your feedback will help shape future iterations (<a href=\"https://www.kaggle.com/competitions/ai-village-ctf/discussion/346451)\" target=\"_blank\">https://www.kaggle.com/competitions/ai-village-ctf/discussion/346451)</a>. This event was only possible with support from Kaggle and the village.  We welcome your contributions (as players, challenge authors, or organizers next year). Your experience and any interesting approaches might also be good candidates for presenting at the village next year! Keep an eye out for the call-for-proposals on our twitter: <a href=\"https://twitter.com/aivillage_dc\" target=\"_blank\">https://twitter.com/aivillage_dc</a>.</p>\n<p><strong>Can we post blogs of our solutions?</strong></p>\n<p>Absolutely, we'd be disappointed if you didn't. You’re welcome to post standalone blogs, blogs as Kaggle discussions, and make your notebooks public. Let us know you do so we can read them! By September 25th, we’ll review the Kaggle discussion board and any blog links you send. Particularly insightful or interesting authors will be eligible for some swag!</p>",
      "rawMarkdown": "The AI Village CTF at Defcon 30 is officially over. Congrats to the winners and everyone who learned something new! We’d like to thank Kaggle for their incredible platform, support, and sponsorship. The platform handled the classic security capture-the-flag (CTF) format with ease and brought an awesome community with it. Thank you to everyone who donated their time and challenges. Joe and I would also like to thank NVIDIA for the time and unwavering support to build and support this event throughout.\n\nWe’d also like to thank **YOU**, the participants. When building this CTF we guessed that maybe 20 people would play, but certainly no more than 200. We ended with 670+ participants with 4000+ entries, which heavily exceeded our expectations. Thank you for being patient with us while we fixed issues that came up (token servers). Thank you for being good-sports with regards to hints, we know this was a different type of challenge for the ML community but we hope you had fun with it.\n\nFinally, thank you for teaching us - you gave us feedback with the questions you asked, frustrations you expressed, and solutions you shared. Not only do we have a list of things to improve on for next year, but I personally learned a lot about how I can approach attacking models differently in my own day-to-day. If you’d like to be involved next year or think a similar event would be a good addition to one of your events, send us an email at **ctf@aivillage.org**.\n\nWith that said, this competition was ultimately about education and community building. As machine learning continues to make its way into our daily lives through core business processes, medical decisions, cyber security, loan approvals, policing, energy management, self-driving, etc. It’s important we develop and teach the skills necessary to enumerate, communicate, and manage the risks inherent in ML systems. This was just one event from the AI Village. We encourage you to stick around the Discord and find other channels that might interest you throughout the year.\n\n**FAQ**\n\n**Will you release the challenge containers used for the competition?**\n\nAll the challenges were donated and the AI Village doesn’t own them. We are leaving it up to the authors to open-source them if they so choose. If/when authors post their challenges, we’ll update this post with links. The servers will be turned off on September 16th.\n\n**Will you be back next year?**\n\nWe certainly hope so. Your feedback will help shape future iterations (https://www.kaggle.com/competitions/ai-village-ctf/discussion/346451). This event was only possible with support from Kaggle and the village.  We welcome your contributions (as players, challenge authors, or organizers next year). Your experience and any interesting approaches might also be good candidates for presenting at the village next year! Keep an eye out for the call-for-proposals on our twitter: https://twitter.com/aivillage_dc.\n\n**Can we post blogs of our solutions?**\n\nAbsolutely, we'd be disappointed if you didn't. You’re welcome to post standalone blogs, blogs as Kaggle discussions, and make your notebooks public. Let us know you do so we can read them! By September 25th, we’ll review the Kaggle discussion board and any blog links you send. Particularly insightful or interesting authors will be eligible for some swag!",
      "votes": null
    },
    {
      "id": "1935404",
      "postDate": "09/12/2022 04:49:45",
      "content": "<p>Thanks for hosting this competition, it was really fun!</p>",
      "rawMarkdown": "Thanks for hosting this competition, it was really fun!",
      "votes": null
    },
    {
      "id": "1935473",
      "postDate": "09/12/2022 06:30:06",
      "content": "<p>This competition was fun. Thanks for hosting!</p>",
      "rawMarkdown": "This competition was fun. Thanks for hosting!",
      "votes": null
    },
    {
      "id": "1935706",
      "postDate": "09/12/2022 10:25:13",
      "content": "<p>I had really fresh experience in this competition. I've got more and more interest on CTF and topics on ML security. I'd like to join other CTF competitions if it held. Thanks for holding this competition.</p>",
      "rawMarkdown": "I had really fresh experience in this competition. I've got more and more interest on CTF and topics on ML security. I'd like to join other CTF competitions if it held. Thanks for holding this competition.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1935404,
      "author_name": "ironbar",
      "author_url": "",
      "post_date": "09/12/2022 04:49:45",
      "content": "<p>Thanks for hosting this competition, it was really fun!</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 1935473,
      "author_name": "joatom",
      "author_url": "",
      "post_date": "09/12/2022 06:30:06",
      "content": "<p>This competition was fun. Thanks for hosting!</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 1935706,
      "author_name": "tatamikenn",
      "author_url": "",
      "post_date": "09/12/2022 10:25:13",
      "content": "<p>I had really fresh experience in this competition. I've got more and more interest on CTF and topics on ML security. I'd like to join other CTF competitions if it held. Thanks for holding this competition.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "1935200": "The AI Village CTF at Defcon 30 is officially over. Congrats to the winners and everyone who learned something new! We’d like to thank Kaggle for their incredible platform, support, and sponsorship. The platform handled the classic security capture-the-flag (CTF) format with ease and brought an awesome community with it. Thank you to everyone who donated their time and challenges. Joe and I would also like to thank NVIDIA for the time and unwavering support to build and support this event throughout.\n\nWe’d also like to thank **YOU**, the participants. When building this CTF we guessed that maybe 20 people would play, but certainly no more than 200. We ended with 670+ participants with 4000+ entries, which heavily exceeded our expectations. Thank you for being patient with us while we fixed issues that came up (token servers). Thank you for being good-sports with regards to hints, we know this was a different type of challenge for the ML community but we hope you had fun with it.\n\nFinally, thank you for teaching us - you gave us feedback with the questions you asked, frustrations you expressed, and solutions you shared. Not only do we have a list of things to improve on for next year, but I personally learned a lot about how I can approach attacking models differently in my own day-to-day. If you’d like to be involved next year or think a similar event would be a good addition to one of your events, send us an email at **ctf@aivillage.org**.\n\nWith that said, this competition was ultimately about education and community building. As machine learning continues to make its way into our daily lives through core business processes, medical decisions, cyber security, loan approvals, policing, energy management, self-driving, etc. It’s important we develop and teach the skills necessary to enumerate, communicate, and manage the risks inherent in ML systems. This was just one event from the AI Village. We encourage you to stick around the Discord and find other channels that might interest you throughout the year.\n\n**FAQ**\n\n**Will you release the challenge containers used for the competition?**\n\nAll the challenges were donated and the AI Village doesn’t own them. We are leaving it up to the authors to open-source them if they so choose. If/when authors post their challenges, we’ll update this post with links. The servers will be turned off on September 16th.\n\n**Will you be back next year?**\n\nWe certainly hope so. Your feedback will help shape future iterations (https://www.kaggle.com/competitions/ai-village-ctf/discussion/346451). This event was only possible with support from Kaggle and the village.  We welcome your contributions (as players, challenge authors, or organizers next year). Your experience and any interesting approaches might also be good candidates for presenting at the village next year! Keep an eye out for the call-for-proposals on our twitter: https://twitter.com/aivillage_dc.\n\n**Can we post blogs of our solutions?**\n\nAbsolutely, we'd be disappointed if you didn't. You’re welcome to post standalone blogs, blogs as Kaggle discussions, and make your notebooks public. Let us know you do so we can read them! By September 25th, we’ll review the Kaggle discussion board and any blog links you send. Particularly insightful or interesting authors will be eligible for some swag!",
    "1935404": "Thanks for hosting this competition, it was really fun!",
    "1935473": "This competition was fun. Thanks for hosting!",
    "1935706": "I had really fresh experience in this competition. I've got more and more interest on CTF and topics on ML security. I'd like to join other CTF competitions if it held. Thanks for holding this competition."
  },
  "source": "meta"
}