├── LICENSE └── README.md /LICENSE: -------------------------------------------------------------------------------- 1 | GNU LESSER GENERAL PUBLIC LICENSE 2 | Version 2.1, February 1999 3 | 4 | Copyright (C) 1991, 1999 Free Software Foundation, Inc. 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | [This is the first released version of the Lesser GPL. It also counts 10 | as the successor of the GNU Library Public License, version 2, hence 11 | the version number 2.1.] 12 | 13 | Preamble 14 | 15 | The licenses for most software are designed to take away your 16 | freedom to share and change it. By contrast, the GNU General Public 17 | Licenses are intended to guarantee your freedom to share and change 18 | free software--to make sure the software is free for all its users. 19 | 20 | This license, the Lesser General Public License, applies to some 21 | specially designated software packages--typically libraries--of the 22 | Free Software Foundation and other authors who decide to use it. You 23 | can use it too, but we suggest you first think carefully about whether 24 | this license or the ordinary General Public License is the better 25 | strategy to use in any particular case, based on the explanations below. 26 | 27 | When we speak of free software, we are referring to freedom of use, 28 | not price. Our General Public Licenses are designed to make sure that 29 | you have the freedom to distribute copies of free software (and charge 30 | for this service if you wish); that you receive source code or can get 31 | it if you want it; that you can change the software and use pieces of 32 | it in new free programs; and that you are informed that you can do 33 | these things. 34 | 35 | To protect your rights, we need to make restrictions that forbid 36 | distributors to deny you these rights or to ask you to surrender these 37 | rights. These restrictions translate to certain responsibilities for 38 | you if you distribute copies of the library or if you modify it. 39 | 40 | For example, if you distribute copies of the library, whether gratis 41 | or for a fee, you must give the recipients all the rights that we gave 42 | you. You must make sure that they, too, receive or can get the source 43 | code. If you link other code with the library, you must provide 44 | complete object files to the recipients, so that they can relink them 45 | with the library after making changes to the library and recompiling 46 | it. And you must show them these terms so they know their rights. 47 | 48 | We protect your rights with a two-step method: (1) we copyright the 49 | library, and (2) we offer you this license, which gives you legal 50 | permission to copy, distribute and/or modify the library. 51 | 52 | To protect each distributor, we want to make it very clear that 53 | there is no warranty for the free library. Also, if the library is 54 | modified by someone else and passed on, the recipients should know 55 | that what they have is not the original version, so that the original 56 | author's reputation will not be affected by problems that might be 57 | introduced by others. 58 | 59 | Finally, software patents pose a constant threat to the existence of 60 | any free program. We wish to make sure that a company cannot 61 | effectively restrict the users of a free program by obtaining a 62 | restrictive license from a patent holder. Therefore, we insist that 63 | any patent license obtained for a version of the library must be 64 | consistent with the full freedom of use specified in this license. 65 | 66 | Most GNU software, including some libraries, is covered by the 67 | ordinary GNU General Public License. This license, the GNU Lesser 68 | General Public License, applies to certain designated libraries, and 69 | is quite different from the ordinary General Public License. We use 70 | this license for certain libraries in order to permit linking those 71 | libraries into non-free programs. 72 | 73 | When a program is linked with a library, whether statically or using 74 | a shared library, the combination of the two is legally speaking a 75 | combined work, a derivative of the original library. The ordinary 76 | General Public License therefore permits such linking only if the 77 | entire combination fits its criteria of freedom. The Lesser General 78 | Public License permits more lax criteria for linking other code with 79 | the library. 80 | 81 | We call this license the "Lesser" General Public License because it 82 | does Less to protect the user's freedom than the ordinary General 83 | Public License. It also provides other free software developers Less 84 | of an advantage over competing non-free programs. These disadvantages 85 | are the reason we use the ordinary General Public License for many 86 | libraries. However, the Lesser license provides advantages in certain 87 | special circumstances. 88 | 89 | For example, on rare occasions, there may be a special need to 90 | encourage the widest possible use of a certain library, so that it becomes 91 | a de-facto standard. To achieve this, non-free programs must be 92 | allowed to use the library. A more frequent case is that a free 93 | library does the same job as widely used non-free libraries. In this 94 | case, there is little to gain by limiting the free library to free 95 | software only, so we use the Lesser General Public License. 96 | 97 | In other cases, permission to use a particular library in non-free 98 | programs enables a greater number of people to use a large body of 99 | free software. For example, permission to use the GNU C Library in 100 | non-free programs enables many more people to use the whole GNU 101 | operating system, as well as its variant, the GNU/Linux operating 102 | system. 103 | 104 | Although the Lesser General Public License is Less protective of the 105 | users' freedom, it does ensure that the user of a program that is 106 | linked with the Library has the freedom and the wherewithal to run 107 | that program using a modified version of the Library. 108 | 109 | The precise terms and conditions for copying, distribution and 110 | modification follow. Pay close attention to the difference between a 111 | "work based on the library" and a "work that uses the library". The 112 | former contains code derived from the library, whereas the latter must 113 | be combined with the library in order to run. 114 | 115 | GNU LESSER GENERAL PUBLIC LICENSE 116 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 117 | 118 | 0. This License Agreement applies to any software library or other 119 | program which contains a notice placed by the copyright holder or 120 | other authorized party saying it may be distributed under the terms of 121 | this Lesser General Public License (also called "this License"). 122 | Each licensee is addressed as "you". 123 | 124 | A "library" means a collection of software functions and/or data 125 | prepared so as to be conveniently linked with application programs 126 | (which use some of those functions and data) to form executables. 127 | 128 | The "Library", below, refers to any such software library or work 129 | which has been distributed under these terms. A "work based on the 130 | Library" means either the Library or any derivative work under 131 | copyright law: that is to say, a work containing the Library or a 132 | portion of it, either verbatim or with modifications and/or translated 133 | straightforwardly into another language. (Hereinafter, translation is 134 | included without limitation in the term "modification".) 135 | 136 | "Source code" for a work means the preferred form of the work for 137 | making modifications to it. For a library, complete source code means 138 | all the source code for all modules it contains, plus any associated 139 | interface definition files, plus the scripts used to control compilation 140 | and installation of the library. 141 | 142 | Activities other than copying, distribution and modification are not 143 | covered by this License; they are outside its scope. The act of 144 | running a program using the Library is not restricted, and output from 145 | such a program is covered only if its contents constitute a work based 146 | on the Library (independent of the use of the Library in a tool for 147 | writing it). Whether that is true depends on what the Library does 148 | and what the program that uses the Library does. 149 | 150 | 1. You may copy and distribute verbatim copies of the Library's 151 | complete source code as you receive it, in any medium, provided that 152 | you conspicuously and appropriately publish on each copy an 153 | appropriate copyright notice and disclaimer of warranty; keep intact 154 | all the notices that refer to this License and to the absence of any 155 | warranty; and distribute a copy of this License along with the 156 | Library. 157 | 158 | You may charge a fee for the physical act of transferring a copy, 159 | and you may at your option offer warranty protection in exchange for a 160 | fee. 161 | 162 | 2. You may modify your copy or copies of the Library or any portion 163 | of it, thus forming a work based on the Library, and copy and 164 | distribute such modifications or work under the terms of Section 1 165 | above, provided that you also meet all of these conditions: 166 | 167 | a) The modified work must itself be a software library. 168 | 169 | b) You must cause the files modified to carry prominent notices 170 | stating that you changed the files and the date of any change. 171 | 172 | c) You must cause the whole of the work to be licensed at no 173 | charge to all third parties under the terms of this License. 174 | 175 | d) If a facility in the modified Library refers to a function or a 176 | table of data to be supplied by an application program that uses 177 | the facility, other than as an argument passed when the facility 178 | is invoked, then you must make a good faith effort to ensure that, 179 | in the event an application does not supply such function or 180 | table, the facility still operates, and performs whatever part of 181 | its purpose remains meaningful. 182 | 183 | (For example, a function in a library to compute square roots has 184 | a purpose that is entirely well-defined independent of the 185 | application. Therefore, Subsection 2d requires that any 186 | application-supplied function or table used by this function must 187 | be optional: if the application does not supply it, the square 188 | root function must still compute square roots.) 189 | 190 | These requirements apply to the modified work as a whole. If 191 | identifiable sections of that work are not derived from the Library, 192 | and can be reasonably considered independent and separate works in 193 | themselves, then this License, and its terms, do not apply to those 194 | sections when you distribute them as separate works. But when you 195 | distribute the same sections as part of a whole which is a work based 196 | on the Library, the distribution of the whole must be on the terms of 197 | this License, whose permissions for other licensees extend to the 198 | entire whole, and thus to each and every part regardless of who wrote 199 | it. 200 | 201 | Thus, it is not the intent of this section to claim rights or contest 202 | your rights to work written entirely by you; rather, the intent is to 203 | exercise the right to control the distribution of derivative or 204 | collective works based on the Library. 205 | 206 | In addition, mere aggregation of another work not based on the Library 207 | with the Library (or with a work based on the Library) on a volume of 208 | a storage or distribution medium does not bring the other work under 209 | the scope of this License. 210 | 211 | 3. You may opt to apply the terms of the ordinary GNU General Public 212 | License instead of this License to a given copy of the Library. To do 213 | this, you must alter all the notices that refer to this License, so 214 | that they refer to the ordinary GNU General Public License, version 2, 215 | instead of to this License. (If a newer version than version 2 of the 216 | ordinary GNU General Public License has appeared, then you can specify 217 | that version instead if you wish.) Do not make any other change in 218 | these notices. 219 | 220 | Once this change is made in a given copy, it is irreversible for 221 | that copy, so the ordinary GNU General Public License applies to all 222 | subsequent copies and derivative works made from that copy. 223 | 224 | This option is useful when you wish to copy part of the code of 225 | the Library into a program that is not a library. 226 | 227 | 4. You may copy and distribute the Library (or a portion or 228 | derivative of it, under Section 2) in object code or executable form 229 | under the terms of Sections 1 and 2 above provided that you accompany 230 | it with the complete corresponding machine-readable source code, which 231 | must be distributed under the terms of Sections 1 and 2 above on a 232 | medium customarily used for software interchange. 233 | 234 | If distribution of object code is made by offering access to copy 235 | from a designated place, then offering equivalent access to copy the 236 | source code from the same place satisfies the requirement to 237 | distribute the source code, even though third parties are not 238 | compelled to copy the source along with the object code. 239 | 240 | 5. A program that contains no derivative of any portion of the 241 | Library, but is designed to work with the Library by being compiled or 242 | linked with it, is called a "work that uses the Library". Such a 243 | work, in isolation, is not a derivative work of the Library, and 244 | therefore falls outside the scope of this License. 245 | 246 | However, linking a "work that uses the Library" with the Library 247 | creates an executable that is a derivative of the Library (because it 248 | contains portions of the Library), rather than a "work that uses the 249 | library". The executable is therefore covered by this License. 250 | Section 6 states terms for distribution of such executables. 251 | 252 | When a "work that uses the Library" uses material from a header file 253 | that is part of the Library, the object code for the work may be a 254 | derivative work of the Library even though the source code is not. 255 | Whether this is true is especially significant if the work can be 256 | linked without the Library, or if the work is itself a library. The 257 | threshold for this to be true is not precisely defined by law. 258 | 259 | If such an object file uses only numerical parameters, data 260 | structure layouts and accessors, and small macros and small inline 261 | functions (ten lines or less in length), then the use of the object 262 | file is unrestricted, regardless of whether it is legally a derivative 263 | work. (Executables containing this object code plus portions of the 264 | Library will still fall under Section 6.) 265 | 266 | Otherwise, if the work is a derivative of the Library, you may 267 | distribute the object code for the work under the terms of Section 6. 268 | Any executables containing that work also fall under Section 6, 269 | whether or not they are linked directly with the Library itself. 270 | 271 | 6. As an exception to the Sections above, you may also combine or 272 | link a "work that uses the Library" with the Library to produce a 273 | work containing portions of the Library, and distribute that work 274 | under terms of your choice, provided that the terms permit 275 | modification of the work for the customer's own use and reverse 276 | engineering for debugging such modifications. 277 | 278 | You must give prominent notice with each copy of the work that the 279 | Library is used in it and that the Library and its use are covered by 280 | this License. You must supply a copy of this License. If the work 281 | during execution displays copyright notices, you must include the 282 | copyright notice for the Library among them, as well as a reference 283 | directing the user to the copy of this License. Also, you must do one 284 | of these things: 285 | 286 | a) Accompany the work with the complete corresponding 287 | machine-readable source code for the Library including whatever 288 | changes were used in the work (which must be distributed under 289 | Sections 1 and 2 above); and, if the work is an executable linked 290 | with the Library, with the complete machine-readable "work that 291 | uses the Library", as object code and/or source code, so that the 292 | user can modify the Library and then relink to produce a modified 293 | executable containing the modified Library. (It is understood 294 | that the user who changes the contents of definitions files in the 295 | Library will not necessarily be able to recompile the application 296 | to use the modified definitions.) 297 | 298 | b) Use a suitable shared library mechanism for linking with the 299 | Library. A suitable mechanism is one that (1) uses at run time a 300 | copy of the library already present on the user's computer system, 301 | rather than copying library functions into the executable, and (2) 302 | will operate properly with a modified version of the library, if 303 | the user installs one, as long as the modified version is 304 | interface-compatible with the version that the work was made with. 305 | 306 | c) Accompany the work with a written offer, valid for at 307 | least three years, to give the same user the materials 308 | specified in Subsection 6a, above, for a charge no more 309 | than the cost of performing this distribution. 310 | 311 | d) If distribution of the work is made by offering access to copy 312 | from a designated place, offer equivalent access to copy the above 313 | specified materials from the same place. 314 | 315 | e) Verify that the user has already received a copy of these 316 | materials or that you have already sent this user a copy. 317 | 318 | For an executable, the required form of the "work that uses the 319 | Library" must include any data and utility programs needed for 320 | reproducing the executable from it. However, as a special exception, 321 | the materials to be distributed need not include anything that is 322 | normally distributed (in either source or binary form) with the major 323 | components (compiler, kernel, and so on) of the operating system on 324 | which the executable runs, unless that component itself accompanies 325 | the executable. 326 | 327 | It may happen that this requirement contradicts the license 328 | restrictions of other proprietary libraries that do not normally 329 | accompany the operating system. Such a contradiction means you cannot 330 | use both them and the Library together in an executable that you 331 | distribute. 332 | 333 | 7. You may place library facilities that are a work based on the 334 | Library side-by-side in a single library together with other library 335 | facilities not covered by this License, and distribute such a combined 336 | library, provided that the separate distribution of the work based on 337 | the Library and of the other library facilities is otherwise 338 | permitted, and provided that you do these two things: 339 | 340 | a) Accompany the combined library with a copy of the same work 341 | based on the Library, uncombined with any other library 342 | facilities. This must be distributed under the terms of the 343 | Sections above. 344 | 345 | b) Give prominent notice with the combined library of the fact 346 | that part of it is a work based on the Library, and explaining 347 | where to find the accompanying uncombined form of the same work. 348 | 349 | 8. You may not copy, modify, sublicense, link with, or distribute 350 | the Library except as expressly provided under this License. Any 351 | attempt otherwise to copy, modify, sublicense, link with, or 352 | distribute the Library is void, and will automatically terminate your 353 | rights under this License. However, parties who have received copies, 354 | or rights, from you under this License will not have their licenses 355 | terminated so long as such parties remain in full compliance. 356 | 357 | 9. You are not required to accept this License, since you have not 358 | signed it. However, nothing else grants you permission to modify or 359 | distribute the Library or its derivative works. These actions are 360 | prohibited by law if you do not accept this License. Therefore, by 361 | modifying or distributing the Library (or any work based on the 362 | Library), you indicate your acceptance of this License to do so, and 363 | all its terms and conditions for copying, distributing or modifying 364 | the Library or works based on it. 365 | 366 | 10. Each time you redistribute the Library (or any work based on the 367 | Library), the recipient automatically receives a license from the 368 | original licensor to copy, distribute, link with or modify the Library 369 | subject to these terms and conditions. You may not impose any further 370 | restrictions on the recipients' exercise of the rights granted herein. 371 | You are not responsible for enforcing compliance by third parties with 372 | this License. 373 | 374 | 11. If, as a consequence of a court judgment or allegation of patent 375 | infringement or for any other reason (not limited to patent issues), 376 | conditions are imposed on you (whether by court order, agreement or 377 | otherwise) that contradict the conditions of this License, they do not 378 | excuse you from the conditions of this License. If you cannot 379 | distribute so as to satisfy simultaneously your obligations under this 380 | License and any other pertinent obligations, then as a consequence you 381 | may not distribute the Library at all. For example, if a patent 382 | license would not permit royalty-free redistribution of the Library by 383 | all those who receive copies directly or indirectly through you, then 384 | the only way you could satisfy both it and this License would be to 385 | refrain entirely from distribution of the Library. 386 | 387 | If any portion of this section is held invalid or unenforceable under any 388 | particular circumstance, the balance of the section is intended to apply, 389 | and the section as a whole is intended to apply in other circumstances. 390 | 391 | It is not the purpose of this section to induce you to infringe any 392 | patents or other property right claims or to contest validity of any 393 | such claims; this section has the sole purpose of protecting the 394 | integrity of the free software distribution system which is 395 | implemented by public license practices. Many people have made 396 | generous contributions to the wide range of software distributed 397 | through that system in reliance on consistent application of that 398 | system; it is up to the author/donor to decide if he or she is willing 399 | to distribute software through any other system and a licensee cannot 400 | impose that choice. 401 | 402 | This section is intended to make thoroughly clear what is believed to 403 | be a consequence of the rest of this License. 404 | 405 | 12. If the distribution and/or use of the Library is restricted in 406 | certain countries either by patents or by copyrighted interfaces, the 407 | original copyright holder who places the Library under this License may add 408 | an explicit geographical distribution limitation excluding those countries, 409 | so that distribution is permitted only in or among countries not thus 410 | excluded. In such case, this License incorporates the limitation as if 411 | written in the body of this License. 412 | 413 | 13. The Free Software Foundation may publish revised and/or new 414 | versions of the Lesser General Public License from time to time. 415 | Such new versions will be similar in spirit to the present version, 416 | but may differ in detail to address new problems or concerns. 417 | 418 | Each version is given a distinguishing version number. If the Library 419 | specifies a version number of this License which applies to it and 420 | "any later version", you have the option of following the terms and 421 | conditions either of that version or of any later version published by 422 | the Free Software Foundation. If the Library does not specify a 423 | license version number, you may choose any version ever published by 424 | the Free Software Foundation. 425 | 426 | 14. If you wish to incorporate parts of the Library into other free 427 | programs whose distribution conditions are incompatible with these, 428 | write to the author to ask for permission. For software which is 429 | copyrighted by the Free Software Foundation, write to the Free 430 | Software Foundation; we sometimes make exceptions for this. Our 431 | decision will be guided by the two goals of preserving the free status 432 | of all derivatives of our free software and of promoting the sharing 433 | and reuse of software generally. 434 | 435 | NO WARRANTY 436 | 437 | 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO 438 | WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. 439 | EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR 440 | OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY 441 | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE 442 | IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 443 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE 444 | LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME 445 | THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 446 | 447 | 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN 448 | WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY 449 | AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU 450 | FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR 451 | CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE 452 | LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING 453 | RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A 454 | FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF 455 | SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH 456 | DAMAGES. 457 | 458 | END OF TERMS AND CONDITIONS 459 | 460 | How to Apply These Terms to Your New Libraries 461 | 462 | If you develop a new library, and you want it to be of the greatest 463 | possible use to the public, we recommend making it free software that 464 | everyone can redistribute and change. You can do so by permitting 465 | redistribution under these terms (or, alternatively, under the terms of the 466 | ordinary General Public License). 467 | 468 | To apply these terms, attach the following notices to the library. It is 469 | safest to attach them to the start of each source file to most effectively 470 | convey the exclusion of warranty; and each file should have at least the 471 | "copyright" line and a pointer to where the full notice is found. 472 | 473 | 474 | Copyright (C) 475 | 476 | This library is free software; you can redistribute it and/or 477 | modify it under the terms of the GNU Lesser General Public 478 | License as published by the Free Software Foundation; either 479 | version 2.1 of the License, or (at your option) any later version. 480 | 481 | This library is distributed in the hope that it will be useful, 482 | but WITHOUT ANY WARRANTY; without even the implied warranty of 483 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU 484 | Lesser General Public License for more details. 485 | 486 | You should have received a copy of the GNU Lesser General Public 487 | License along with this library; if not, write to the Free Software 488 | Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 489 | USA 490 | 491 | Also add information on how to contact you by electronic and paper mail. 492 | 493 | You should also get your employer (if you work as a programmer) or your 494 | school, if any, to sign a "copyright disclaimer" for the library, if 495 | necessary. Here is a sample; alter the names: 496 | 497 | Yoyodyne, Inc., hereby disclaims all copyright interest in the 498 | library `Frob' (a library for tweaking knobs) written by James Random 499 | Hacker. 500 | 501 | , 1 April 1990 502 | Ty Coon, President of Vice 503 | 504 | That's all there is to it! 505 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ![Hello hackathon](https://github.com/Web3-Club/Hello-hackathon/assets/76860915/56c9e012-cf5a-45d6-9112-eb615bcd086e) 4 | 5 | 6 | 7 |

8 | 你的第一本黑客松入门手册 助你参与人生第一场黑客松 9 | 10 |

11 | 12 | ***还在施工中*** 13 | 14 | 15 | 16 | 17 | # 前言 18 | 19 | 20 | ## 由何而起？ 21 | 22 | 我在2023年初开始的一年间，在Covid-19解封之后，大学一年级下学期开始 我主要作为产品和测试，参加了十几场黑客松。 23 | 24 | （如 Ethereum Beijing，Singapore，Hangzhou 、Polkadot Winter Hong kong、Circle Hackathon etc.） 25 | 26 | 27 | 于是我身边不少听过我的经历，但没有参与过黑客松又对黑客松很感兴趣的朋友 经常问我： 28 | 29 | **如何去开启第一场黑客松？** & **我不会开发/不是hacker，值得去参加一次吗？** 30 | 31 | --- 32 | 33 | 不少朋友也是因为各种原因而无法参加相关领域的黑客松————害怕自己做不出什么东西、感觉自己能力有限、找不到最近的黑客松活动信息...... 34 | 35 | 基于上述情况，我创建了这个仓库，旨在帮助所有的黑客松小白**能开启他人生中的第一场黑客松**。 36 | 37 | --- 38 | 39 | ## 为什么你要去打黑客松？ 40 | 41 | 我认为每一位 42 | 43 | - 刚开始了解一个领域（不止是Web3） 44 | - 学习一门新语言，无论何种技术栈 45 | - 会一些技能的朋友，例如设计，演讲，哪怕是做PPT 46 | 47 | **都可以去尝试去体验黑客松的整个赛程** 48 | 49 |
50 | 51 | 无论是线上或者是线下 ***（当然线下氛围更好）*** 52 | 53 | 无论你是开发者，产品，想要让自己的想法变成现实，做一些自己的产品， 54 | 55 | 还是设计师，“布道者”，让团队的作品让更多人看到其中的创新点或闪光点。 56 | 57 | --- 58 | 59 | 特别是对于所有朋友来说，黑客松是很好的一次获得自我提升以及接触人脉，认识新朋友的机会。 60 | 61 | 特别是提高自己的技术实现能力和商业计划水平。 62 | 63 | 我[自己](http://github.com/yanboishere)深有体会。 64 | 65 |
66 |
67 |
68 | 69 | 70 | # 正文 71 | 72 | ## 黑客松分类 73 | 74 | 黑客松的类型各有不同，既有大厂（Microsoft），公链（ [以太坊](https://ethereum.org/zh/community/events/)、[Solana](https://solana.com/events)、[Sui](https://sui.io/community-events-hub) ，也有预言机、跨链桥（Chainlink、Circle CCTP）等各类产品，当然也有社区和组织开展的开放性主题黑客松（如[AdventureX](https://adventure-x.org/) ） 75 | 76 | 第一次打黑客松，建议最好是去线下去体验，感受更浓厚的氛围和更好的交流体验。 77 | 78 | ## 比赛过程 79 | 80 | ### 前期报名/组队 81 | #### 报名 82 | 在前期报名的过程中，主办方会在活动官网发布报名的表格（也有直接提交项目的黑客松） 83 | 84 | 来去通过收集你的个人信息 85 | 86 | 可能包括但不限于以下信息： 87 | 88 | - 个人基本信息 89 | - 姓名 90 | - 年龄 91 | - 联系方式 92 | - 邮件 93 | - 微信 94 | - Telegram 95 | - Discord 96 | - 个人社交媒体 97 | - X 98 | - 作品集 99 | - GitHub 100 | - 博客 101 | - 个人经验 102 | - 本行业从业年限 103 | - 曾经做过什么项目 104 | - 是否是首次参赛 105 | - 在团队中的角色 106 | - 技术 107 | - 前端 108 | - 后端 109 | - 智能合约 110 | - 产品 111 | - 设计 112 | - UI 113 | - UX 114 | - 是否为学生 115 | - 在本次黑客松想做的事情（项目） 116 | 117 | --- 118 | 119 | 提交完以上信息 请等待项目方给你的邮件或者社交媒体回复↩️ 120 | 121 | - 是否成功报名 122 | - 有名额限制的热门黑客松 123 | - 是否入选到黑客松中 124 | 125 | #### 组队 126 | 在收到/未收到 报名及入选成功信息后（最好是在收到报名及入选成功信息后） 127 | 128 | 如果你不想自己去solo独立搞事情，最好去黑客松官方的社群，或者项目初期展示时，去找到能力适合自己项目、可以并肩作战的队友。 129 | 130 | （黑客松官方可能会组织未组队的朋友/正在急召队友的队伍 在线上会议或者通过表格信息的形式自由组织组队） 131 | 132 | ### 项目初期展示 133 | 134 | 有部分线下/线上黑客松，会在开赛之初 让所有参赛者用1-3分钟时间轮流介绍自己的项目。 135 | 136 | 此时需要你简短的去概括自己的项目/介绍自己的团队， 137 | 138 | 最好讲述的让场下的朋友们印象深刻些，讲出自己的创新点或项目特点。 139 | 140 | 这时候也可以提到自己的队伍缺少什么角色的队友，如前端，产品（一般情况下是缺少技术角色的队友），问下在场的朋友有没有还未组队的情况。 141 | 142 | --- 143 | 144 | 同时你可以跟各个团队在现场（线上黑客松可以在线上勾兑）交流，互相介绍对方并聊一下各自想在黑客松的项目。 145 | 146 | ### 中期检查 147 | 148 | 一些黑客松会在比赛赛程达到中期时进行中期检查，为的是检查完成程度以及安排导师或工作人员下场指导。 149 | 150 | 此时请把握好这个机会，将你对项目/赛道/赛制......等等问题，统统抛给导师或工作人员。 151 | 152 | 有些黑客松会把中期检查的情况作为评分点，因此务必注意好时机，好好表现。 153 | 154 | ### 提交 155 | 156 | (To be continue......) 157 | 158 | 159 | ### 初赛筛选 160 | 161 | (To be continue......) 162 | 163 | ### 决赛（Demo Day） 164 | 165 | 决赛的pitch环节是很重要的环节 166 | 167 | (To be continue......) 168 | 169 | 170 | --- 171 | 172 | 173 | ## Q&A 答疑 174 | ### Q：我不会技术 可不可以参加黑客松？ 175 | 176 | A： 177 | 借用Jupiter老师的总结 178 | 179 | 其实不会技术的同学也可以参加黑客松，黑客松虽然关注技术，但是其实也有很多东西可以关注。 180 | 181 | 比如如果做B端产品，那其实同时参加黑客松的这些项目就可能是你的客户，就需要你去BD（Bussiness Developer）。 182 | 183 | 另外也可以在这个过程，比如pitch或者demo day的时候去锻炼讲故事的能力，讲好一个故事对于任何产品来说都很重要，任何产品都需要有一定技术的人来叙事的，所以这个能力真的非常需要关注，不能只盯着技术。 184 | 185 | 黑客松还会涌现出一些趋势性的或者很新的产品，可以去做一些相关赛道的分析，在黑客松之外抓住机会。 186 | 187 | --- 188 | 189 | 包括我自己大一刚开始的时候也是技术小白的情况下参与了人生第一次黑客松，还作为队长带领团队去做产品。 190 | 191 | 虽然那时候不懂技术，开发对我来说约等于完全不会，但很感谢的是我找到了一些很会帮我解决技术和开发问题的朋友。 192 | 193 | 特别是在那次黑客松上，我发现大家使用各种AIGC（人工智能生成内容）工具去做产品中的代码、美术（LOGO、PPT、海报）部分，我认为未来借助于AIGC应用，一人去参赛或者一人公司的情况也会越来越多。 194 | 195 | ## Q：黑客松是否只能在比赛期间构建项目？ 196 | A：理论上是这样的 包括很多黑客松的规定是只能在黑客松期间去构建自己的项目 197 | 198 | 但实际上仍有很多项目是在黑客松之前的很长一段时间已经构建很久周期去做的项目再去进行提交 199 | 200 | 个人实际上是反对这种做法的 但是如果你是想在赛前去 提前做测试、完善想法和思路、了解需要的技术栈情况 201 | 202 | 或者是在之前项目的基础上 在这次黑客松赛程期间 加入新的功能/做一些新的尝试 203 | 204 | 那是在可允许范围之内的 205 | 206 | ## 致谢 207 | 在此我要感谢近一年一路上所有支持我的家人和朋友，以及黑客松主办方。 208 | 209 | 没有你们就没有现在的我以及这个教程。 210 | 211 |
212 | 213 | --- 214 | 215 | 216 | # 附录 217 | ## 黑客松活动网站 218 | - [DevPost](https://devpost.com/) 219 | - [dorahacks](https://dorahacks.io/zh) 220 | 221 | 222 | ## 黑客松日历 223 | （还在建设中） 224 | 225 | [Social Layer](https://app.sola.day/event/hackathons) 226 | 227 | 228 |
229 | 230 | 231 | # 项目合作社区 232 | ## 周周黑客松 233 | ![621724814808_ pic](https://github.com/user-attachments/assets/b7be21b3-a5c5-4384-aa76-6aad0f2be1dc) 234 | 235 | ### 简介 236 | HackathonWeekly周周黑客松是一个公益开源的极客社区，定期举办交流会和黑客松，旨在帮助每个参与者实现最小可行产品。 237 | 238 | ### 官网 239 | [hackathonweekly](https://hackathonweekly.com/) 240 | 241 | ### 微信号 242 | `hackathonweekly` 243 | 244 |
245 |
246 |
247 | 248 | 249 | 250 | ## 更多资料 251 | 252 | ### Twitter Space 253 | [浙大链协ZJUBCA-为什么人人都应该参与一场黑客松](https://x.com/zjubca/status/1705159500884590701) 254 | 255 | #### Twitter Space发言嘉宾总结 256 | ##### 小红书 257 | [黑客松分享(一)-Jupiter](http://xhslink.com/N7pgGJ) 258 | 259 | [黑客松分享(二)-Jupiter](http://xhslink.com/UfLgGJ) 260 | 261 | ### GitHub Repo 262 | [33357-黑客松对于开发者来说有什么用](https://github.com/33357/smartcontract-apps/blob/main/Meeting/Hackathon.md) 263 | 264 | 265 | ### 我们的联系方式 266 | 267 | 268 | 269 | 270 | ©️ Web3Club 2024 271 | 272 | 273 | --------------------------------------------------------------------------------