세계 최초 수준! 구글·깃허브 연동형 공개 검증 시스템. 로또아이는 2025년 2월 8일 첫 기록부터 지금까지, 추첨 전 데이터를 외부 시스템에 고정하여 사후 조작이나 은폐가 불가능한 투명한 검증 구조를 유지하고 있습니다.
(LOTTOi Public Verification Framework Whitepaper – EN)
Since 2025. 02. 08.
LOTTOi has applied an external public verification method since February 8, 2025, by recording generated numbers in an external public document before the draw, rather than keeping them only inside its internal system.Since January 29, 2026, LOTTOi has also applied an external public verification framework in which the Google document URL for each round is first fixed on GitHub before the draw, allowing anyone to check after the draw whether the disclosed verification URL was changed afterward.
The term “world-first-level” in this whitepaper does not refer to the entire lottery service, winning probability, prediction performance, profit, or result guarantees.
It refers to a public verification structure in which generated numbers are recorded before the draw in an external public document that users can easily check, and the reference point of that document is fixed in a separate external public record in advance, so that both records can be cross-checked after the draw.Based on public web research, LOTTOi has not found any identical prior case to date. Based on this research and the actual applied structure, LOTTOi describes this structure as a world-first-level external public verification framework.
LOTTOi has designed and applied a public verification method that records pre-draw data in an external public document, so that anyone can compare the prior existence of generated numbers with the results of each round.
The core of this method is not merely to disclose numbers.
LOTTOi has built an external public verification framework so that users can directly check whether generated numbers actually existed before the draw, and whether those records were changed after the draw.
The current LOTTOi public verification framework consists of the following two standards.
Through this structure, anyone can check after the draw whether the disclosed Google document URL was arbitrarily changed afterward, and can also compare it with the actual generated number records in the Google document.
This whitepaper was prepared to explain LOTTOi’s public verification principles, the roles of Google documents and GitHub, the structure of the external public verification framework, and the scope and limits of the expression “world-first-level.”
While reviewing lottery-related services, LunaSG found that even when users see results, it can be difficult for them to directly verify whether the numbers actually existed before the draw and whether they were unchanged afterward.
In general, lottery-related services present their performance in various ways, such as result explanations, reviews, images, and interviews.
However, such methods alone may make it difficult for users to directly verify whether recommended or generated numbers actually existed before the draw, and whether those records remained unchanged afterward.
To reduce this limitation, LOTTOi reviewed a method of recording generated numbers in an external public document instead of keeping them only inside its internal system.
As a result, LOTTOi designed an external public verification framework that records pre-draw data in an external public document and fixes the reference point of that document in a separate external public record, enabling post-draw comparison.
This awareness of the issue became a major background for LunaSG in designing and operating LOTTOi.
LOTTOi did not choose Google documents merely for storage convenience.
Google is an external platform familiar to general users.
In addition, Google documents present information in a table-like format, making number records relatively easy for non-developers to review.
Developer-oriented repositories such as GitHub provide strong history-checking features, but they may feel difficult for general users.
By contrast, Google documents are easy for users to open directly and check round-by-round number records in a table format.
LOTTOi set the standard that public verification should not exist only as a technical mechanism, but should also be directly checkable by real users.
Google documents also provide a structure in which document revision history can be checked.
LOTTOi uses this characteristic so that users can directly review whether generated numbers were recorded in an external public document rather than being kept only inside the internal system.
Therefore, in LOTTOi, Google documents are not merely storage. They serve as an external public verification window that users can directly check.
LOTTOi does not use the expression “world-first-level” to refer to the entire lottery service or to winning prediction performance.
In this whitepaper, “world-first-level” refers to the following public verification structure.
First, generated numbers are recorded before the draw in an external public document that users can easily check, allowing anyone to review them afterward regardless of whether they use the service.
Second, the reference point of the external public document containing the actual generated number records is fixed in a separate external public record before the draw, allowing anyone to check whether the verification URL disclosed after the draw was changed afterward.
Third, the actual generated number records and the external reference-point record can be compared together, allowing the prior existence of the pre-draw record and any post-draw changes to be reviewed through a cross-checkable public verification structure.
Currently, LOTTOi uses Google documents and GitHub to implement this structure.
The actual generated number records are stored in Google documents.
The corresponding Google document URL is first fixed on GitHub before the draw.
Based on public web research, LOTTOi has not found any identical prior case to date. Based on this research and the actual applied structure, LOTTOi describes this structure as a world-first-level external public verification framework.
However, this expression does not mean a guarantee of winning probability, prediction performance, profit, or results.
It refers to a public verification design method that combines pre-draw records with external verification standards.
External public verification is a method designed so that anyone can directly check whether generated numbers were recorded in an external public document before the draw, and whether those records were changed after the draw.
LOTTOi does not keep generated numbers only inside its internal system. It records them in an external public document before the draw so that post-draw verification is possible.
An external public verification framework means the overall structure that allows users to check, through external records, when, where, and under what standard pre-draw records were created.
LOTTOi’s external public verification framework combines an external public document that users can easily check with a separate external reference-point record.
Under the current applied standard, the roles of Google documents and GitHub are separated.
The actual generated number records are stored in Google documents.
The corresponding Google document URL is recorded on GitHub before the draw.
Therefore, anyone can compare Google documents and GitHub records after the draw to check the prior existence of the disclosed verification URL and generated number records, as well as whether any post-draw changes occurred.
An external public document that users can easily check refers to an external public document that general users can open directly and review easily.
In LOTTOi, Google documents currently serve this role.
Google documents allow number records to be checked in a table format, making it relatively easy even for non-developers to review round-by-round records.
An external reference-point record means a method of recording the location or reference information of the external public document containing the actual records in a separate external record before the draw.
In LOTTOi, GitHub currently serves this role.
The Google document URL for each round is recorded on GitHub before the draw.
This allows anyone to check after the draw whether the disclosed Google document URL was changed afterward.
A cross-checkable public verification structure means a structure that compares external records with different roles to verify prior existence and post-draw change status.
In LOTTOi, the actual generated number records in Google documents and the URL pre-draw fixing records on GitHub are cross-checked together.
This structure differs from ordinary result disclosure methods because it does not rely on a single internal record, but uses both an external public document and an external reference-point record.
When this whitepaper uses the expression “public verification chain,” it does not mean blockchain.
Here, “chain” refers to a public verification structure in which pre-draw records and external reference-point records are connected and can be compared.
To reduce misunderstanding, this whitepaper primarily uses the expressions “external public verification framework” or “cross-checkable public verification structure.”
LOTTOi’s external public verification is designed so that anyone can directly check whether generated numbers were recorded in an external public document before the draw, and whether those records were changed after the draw.
In a typical internal-record method, it is difficult for anyone to directly verify whether the numbers actually existed before the draw, regardless of whether they use the service.
To reduce this limitation, LOTTOi records generated number data in an external public document and allows anyone to check those records and their change history after the draw.
The core principles of external public verification are as follows.
LOTTOi does not simply aim to make record modification impossible.
The core point is to make it difficult to hide the time and details of any modification if it occurs.
Through this, LOTTOi provides a verification standard that can reduce post-draw manipulation concerns and can be directly checked by anyone regardless of service use.
LOTTOi’s external public verification framework is structured in the following order under the actual applied standard.
[Pre-creation of an external public document for each round]
└ Create an external public document where actual generated number records will be stored
└ The document creation time and permission-change history are recorded on the external platform
↓
[Pre-fixing of an external reference point]
└ Store the external public document URL for the round in a separate external public record before the draw
└ The prior existence time of the URL can be checked through the external record history
↓
[Generated numbers are finalized and the system is closed]
↓
[On draw day, after lottery purchase closing and before the draw begins]
└ Store generated number data in the external public document
└ The storage time and change history are recorded on the external platform
↓
[Lottery draw takes place]
↓
[Post-draw verification by anyone]
└ Check whether the public document URL was fixed before the draw in the external reference-point record
└ Check generated number records and version history in the external public document
└ Check whether the data was modified after the draw
In LOTTOi, this structure is currently applied as follows.
[Google Document]
└ Verification standard for actual generated number records
[GitHub]
└ Verification standard for whether the Google document URL was fixed before the draw
[Post-Draw Verification]
└ Compare Google document records and GitHub records together
In this structure, Google documents and GitHub have different roles.
Google documents are the standard for checking actual generated number records.
GitHub is the standard for checking whether the corresponding Google document URL was fixed before the draw.
By comparing the two records together, the prior existence of pre-draw records and post-draw change status can be checked more clearly.
Google documents are the external public documents where actual generated number records are stored in LOTTOi’s public verification method.
LOTTOi creates a Google document for each round and records the necessary generated number data in that document before the draw.
The following can be checked in Google documents.
The core role of Google documents is to provide a standard for checking whether actual generated numbers were recorded in an external document before the draw.
Google documents also provide a table format that general users can open directly and understand easily.
LOTTOi applied the standard that public verification should not be understandable only to developers or experts, but should also be directly checkable by general users.
Therefore, Google documents serve as a user-friendly public verification window within LOTTOi’s external public verification framework.
GitHub serves as an external reference point that allows users to check whether a Google document URL was recorded before the draw and whether it was changed afterward.
Within LOTTOi’s external public verification framework, GitHub’s core role is to fix the Google document URL as an external record before the draw.
The actual generated number records are stored in Google documents.
The corresponding Google document URL is recorded on GitHub before the draw.
Therefore, after the draw, anyone can directly check whether the Google document URL disclosed on the LOTTOi website had been recorded on GitHub before the draw.
GitHub records provide the following standards.
The core verification standard is whether the Google document URL used as the final public verification standard was fixed on GitHub before the draw.
LOTTOi uses Google documents so that pre-draw records and permission-change processes remain recorded according to external time standards.
A Google document is created in advance for each round.
The document creation time and subsequent permission-change records remain in the Google system.
After lottery purchase closing, the permission changes and data storage required to store generated numbers are carried out.
At this time, generated number data is recorded in the Google document.
The storage time and subsequent change history can be checked through the Google document version history.
This method is intended to leave major points where operator intervention may occur as external system records.
Anyone can directly check data integrity and public verification standards through the following paths.
On GitHub, the following can be checked.
GitHub’s core role is to provide an external reference point that fixes the Google document URL before the draw.
In Google documents, the following can be checked.
In particular, it is important to check whether the record at the pre-draw reference time matches the currently disclosed result.
GitHub and Google documents have different roles.
GitHub is the standard for checking whether the URL was fixed in advance.
Google documents are the standard for checking the actual generated number records.
By comparing the two records together, the prior existence of pre-draw records and post-draw change status can be checked more clearly.
It is technically impossible to completely exclude the possibility that a public document may be modified after the draw.
However, the important standard in LOTTOi’s external public verification framework is not a claim that modification is entirely impossible.
The important point is a structure in which traces cannot be hidden if modification occurs.
Google documents may retain the following information.
GitHub may retain the following information.
Therefore, anyone can check through post-draw verification whether data was changed after the draw time.
LOTTOi does not claim that post-draw modification is impossible.
Instead, it aims to provide a verification environment in which post-draw modification status can be checked through external records.
GitHub records may be modified before the draw due to an incorrect URL entry, document connection error, input error, or similar reason.
In this case, LOTTOi considers the following standards important.
The core verification standard is whether the Google document URL used as the final public verification standard was fixed on GitHub before the draw.
If a URL change occurs after the draw, the verification standard and change details for that round must be checked separately.
Due to unavoidable factors such as external network delays, Google or GitHub platform failures, and permission-change delays, the creation of records or finalization of public verification standards may be temporarily delayed.
The purpose of this structure is not to claim a perfect system with no delays.
The purpose is to ensure that if delays or modifications occur, those facts remain as external records and can be checked afterward.
Because the actual creation time and change history remain on external platforms, the time relationship with the draw can be checked afterward.
LOTTOi uses the expression “world-first-level external public verification framework” not as an absolute advertising statement, but in the limited sense that no identical prior case has been found based on public web research.
This section summarizes the first research standards and comparison results used to review whether any prior cases identical or similar to LOTTOi’s external public verification framework exist in publicly available web materials.
However, the comparison target of this whitepaper is not all number-recommendation businesses or lottery draw systems.
The comparison target is number-selection lottery prediction, recommendation, and generation services and projects.
For similar domestic services, individual service names are not directly listed in the public table in order to avoid unnecessary misunderstanding that could be interpreted as naming specific companies or comparative advertising. Instead, they are summarized under the category “domestic lottery number recommendation services in general.”
Individual service names, URLs, screenshots, verification dates, and similar details are kept in a separate internal research log.
This first research was summarized as of May 2026 and may be supplemented later as publicly available web materials change.
The research focused on the following categories.
The following categories are excluded from direct comparison or are treated only as references.
Although the excluded categories may be adjacent cases in a broad sense of “verifiability,” their purpose and structure differ from the market compared by LOTTOi, which is number-selection lottery number recommendation and generation services.
The main search terms used in the research are as follows.
| Language | Search Term |
|---|---|
| Korean | 로또 번호 공개 검증 |
| Korean | 로또 추천번호 추첨 전 공개 |
| Korean | 로또 번호 추첨 전 기록 |
| Korean | 로또 GitHub 검증 |
| Korean | 로또 구글 공개 검증 |
| Korean | 로또 예측번호 공개 기록 |
| Korean | 로또 번호 추천 검증 시스템 |
| Korean | 로또 번호 추천 서비스 |
| Korean | 로또 번호 생성 서비스 |
| Korean | 로또 번호 분석 서비스 |
| English | lotto prediction public verification |
| English | lottery prediction public verification |
| English | lottery numbers before draw public record |
| English | lottery prediction GitHub timestamp |
| English | Google Sheets lottery prediction GitHub |
| English | lottery number prediction proof before draw |
| English | verifiable lottery prediction system |
| English | timestamped lottery prediction |
| English | public lottery prediction record |
| English | lotto number generator verification |
| English | lottery number recommendation verification |
| Simplified Chinese | 彩票 预测号码 公开 验证 |
| Simplified Chinese | 彩票 预测 抽奖前 公开 |
| Simplified Chinese | 彩票 号码 公开记录 |
| Simplified Chinese | 彩票 预测 GitHub 验证 |
| Simplified Chinese | 彩票 Google 表格 预测 |
| Simplified Chinese | 彩票 预测 公开 时间戳 |
| Simplified Chinese | 彩票 号码 推荐 验证 系统 |
| Traditional Chinese | 彩券 預測號碼 公開 驗證 |
| Traditional Chinese | 彩券 預測 抽獎前 公開 |
| Traditional Chinese | 彩券 號碼 公開紀錄 |
| Traditional Chinese | 彩券 預測 GitHub 驗證 |
| Traditional Chinese | 彩券 Google 試算表 預測 |
| Japanese | ロト 予想番号 公開 検証 |
| Japanese | ロト 予想番号 抽選前 公開 |
| Japanese | 宝くじ 予想 検証 公開 |
| Japanese | ロト GitHub 検証 |
| Japanese | ロト Google スプレッドシート 予想 |
| Spanish | predicción lotería verificación pública |
| Spanish | números de lotería antes del sorteo registro público |
| Spanish | predicción lotería GitHub |
| Spanish | predicción lotería hoja de cálculo Google |
| French | prédiction loto vérification publique |
| French | numéros loto avant tirage registre public |
| French | prédiction loterie GitHub |
| French | prédiction loto feuille Google |
| German | Lotto Vorhersage öffentliche Verifizierung |
| German | Lottozahlen vor Ziehung öffentlicher Nachweis |
| German | Lotto Vorhersage GitHub |
| German | Lotto Vorhersage Google Tabelle |
In this whitepaper, an “identical case” does not simply mean a case that predicts lottery numbers, discloses draw results, or uploads program code to GitHub.
The comparison target of this whitepaper is not all number-recommendation businesses.
The comparison target is the field of number-selection lottery number recommendation and generation services.
To be considered identical to LOTTOi, the following conditions must be met together.
LOTTOi’s reference structure is as follows.
Google Document
Actual generated number recordsGitHub
The corresponding Google document URL is fixed before the drawPost-Draw Verification
Google document records and GitHub commit history are cross-checked
Therefore, simple prediction code, simple number generators, statistical analysis tools, and post-draw result disclosure services may be classified as similar cases, but they are not considered identical unless they meet all of the above conditions.
This comparison table focuses on number-selection lottery number prediction, recommendation, and generation services and projects.
Blockchain lotteries, Chainlink VRF, commit-reveal, RANDOM.ORG, and similar cases are adjacent technologies related to the fairness of lottery draws or general random-number verification.
However, they are excluded from this comparison table because their purpose differs from the service structure of LOTTOi, which verifies the prior existence and post-draw change status of recommended or generated numbers received by users.
Similar domestic services are categorized as “domestic lottery number recommendation services in general” rather than listing individual service names directly in the public whitepaper.
This is intended to reduce unnecessary misunderstanding that could be interpreted as naming specific companies or comparative advertising.
| Category | Case Name / Type | Confirmed Details | Similarity to LOTTOi | Difference from LOTTOi | Identical Case |
|---|---|---|---|---|---|
| Reference Case | LOTTOi | A structure that records generated numbers in Google documents, fixes the corresponding Google document URL on GitHub before the draw, and cross-checks both records after the draw | Pre-draw external record, post-draw change history check, publicly verifiable structure | Reference case | Reference case |
| Domestic lottery number recommendation services in general | Lottery number recommendation and analysis services | Domestic service types that provide past winning number analysis, number recommendation, statistics, and some result disclosure features | Similar in that they provide lottery number recommendation and analysis | No structure has been confirmed in which recommended numbers are recorded before the draw in an external public document that users can easily check, the reference point is fixed in a separate external public record in advance, and post-draw change status is cross-checked | Not identical |
| GitHub prediction code | Lottery number prediction code | AI, LSTM, machine learning, and statistics-based prediction code repositories | Similar in the theme of lottery number prediction | Publicly available prediction code, not a structure for pre-draw external recording and post-draw verification of recommended numbers | Not identical |
| GitHub prediction apps | Lottery prediction web apps | Number prediction or analysis apps implemented with Flask, Python, Streamlit, and similar tools | Similar in prediction and web-service form | No pre-draw external record, change history check, or cross-checking structure | Not identical |
| Google Sheets use cases | Google Sheets-based lottery analysis templates | Number analysis and prediction templates using Excel or Google Sheets | Some similarity in the possible use of Google Sheets or table-format tools | Personal analysis tools, not a structure for pre-draw external public recording and GitHub reference-point fixing | Not identical |
| Mobile apps | Lotto Prediction Android app types | Apps that provide lottery number prediction or generation features | Similar in number recommendation and prediction functions | No confirmed public verification framework, external records, or change-history comparison structure | Not identical |
| Patents / Ideas | Lottery prediction number provision system types | Ideas related to lottery prediction service systems that provide multiple prediction number combinations | Similar in that they provide prediction numbers | No external public document recording, external reference-point fixing, or post-draw change verification structure | Not identical |
| Chinese-language prediction projects | 彩票 prediction and analysis projects | Projects that collect and analyze Chinese lottery data and provide AI prediction features | Similar in lottery data collection, statistical analysis, and AI prediction | Closer to prediction models or analysis apps; not a structure that records recommended numbers in Google documents before the draw and pre-fixes URLs on GitHub | Not identical |
| Japanese-language prediction projects | ロト prediction and analysis projects | Japanese lottery number analysis and prediction code or content for ロト6, ロト7, and similar games | Similar in number-selection lottery prediction | Mainly prediction code or analysis content; not a structure for pre-draw external public recording and post-draw change verification | Not identical |
| Spanish-language prediction projects | lotería prediction projects | Machine learning or statistics-based lottery number prediction projects | Similar in lottery number prediction models | Model development and prediction-oriented; no pre-draw external public record or post-draw change-history verification structure | Not identical |
| French / European prediction projects | loto prediction projects | Loto number prediction and past-data learning projects | Similar in Loto number prediction and past-data learning | Mainly prediction code; not a framework for verifying recommended numbers with Google documents and GitHub records before the draw | Not identical |
| Multilingual GitHub prediction groups | lottery-prediction / loto topic groups | Various prediction and analysis repositories related to lottery, loto, and lotto prediction across multiple language groups | Shows that lottery prediction code and analysis attempts exist globally | Most are limited to code, models, and analysis disclosure; no structure has been confirmed for cross-checking prior existence and post-draw change status of recommended numbers through external records | Not identical |
※ Case names, repository names, search result captures, and access URLs for this comparison table are kept in a separate research log.
※ Detailed comparison materials for similar domestic services are kept in a separate internal research log to avoid publicly naming specific companies.
In the first public web research, no structure completely identical to LOTTOi was found.
In particular, no case was found that satisfies all of the following conditions.
The similar cases found can be divided into four main categories.
First, domestic and international lottery number recommendation and analysis service types.
These may provide past winning number analysis, number recommendation, statistics, and some result disclosure functions, but no structure has been confirmed in which recommended numbers are recorded before the draw in an external document, a reference point is fixed in a separate external record in advance, and post-draw change status is cross-checked.
Second, lottery number prediction code.
These mostly focus on predicting or generating numbers through AI, LSTM, machine learning, or statistical analysis.
Third, lottery number analysis apps or web apps.
These provide past winning number data analysis, number recommendation, number generation, statistical visualization, and similar functions.
Fourth, multilingual prediction and analysis projects, including Chinese, Japanese, Spanish, and French language groups.
These are similar in that they involve number-selection lottery prediction or analysis, but no pre-draw external public record or post-draw change-history verification structure has been confirmed.
Therefore, under the first research standard, LOTTOi’s structure is distinguished from existing similar cases in the following way.
Existing Similar Cases
Focused on lottery number recommendation, number generation, statistical analysis, AI models, and prediction code disclosureLOTTOi
A structure that cross-checks whether recommended numbers actually existed before the draw,
and whether they were changed after the draw,
through an external public document that users can easily check and an external reference-point record
This research is a first-stage review based on publicly available web materials.
It has the following limitations.
Therefore, rather than using “world first” as an absolute or definitive expression, LOTTOi explains it in the following limited manner based on the research scope and the characteristics of the public verification structure.
In the field of number-selection lottery number recommendation and generation services,
LOTTOi applies a cross-checkable external public verification framework
that combines an external public document users can easily check
with an external reference-point record,
for which no identical prior case has been found based on public web research.
LOTTOi describes this structure as a world-first-level external public verification framework.
This expression does not mean a guarantee of winning probability, prediction performance, profit, or results.
It refers to a public verification design method that combines pre-draw records with external verification standards.
The current LOTTOi external public verification framework is mainly applied through Google document records and pre-draw GitHub URL fixing.
This whitepaper explains the standards and verification methods of the public verification framework currently being applied.
Future expansion and application methods will be reviewed based on user understanding, reliability of external records, verification convenience, and technical stability.
If expansion takes place, LOTTOi will continue to supplement the public verification framework based on the accessibility of external public documents, the reliability of external reference-point records, and user verifiability.
This whitepaper was prepared for the following purposes.
This document does not guarantee winning probability, prediction performance, profit, or results.
It must not be interpreted as an investment, prediction, or guarantee document under any circumstances.
The expression “world-first-level” is also a limited explanation of a structure for which no identical prior case has been found based on public web research, and it is not a definitive statement that no non-public case exists anywhere in the world.
Before speaking about results, LOTTOi sought to establish a record standard through which those results could be checked.
The LOTTOi Public Verification Whitepaper was prepared to help users understand the principles and structure of the external public verification framework applied by LOTTOi and directly review the corresponding public records.
LOTTOi applies an external public verification framework in which generated numbers are recorded externally before the draw and the reference point of those records is connected to a separate external public record for post-draw verification.
Through this verification structure, LOTTOi aims to increase user confidence in its generated-number records and result disclosure process and to provide a more transparent service environment.
LOTTOi will continue to place importance on clear record and verification standards in order to support a transparent environment in which users can make reasonable choices.
Copyright in the text, tables, diagrams, editorial arrangement, and related materials contained in this whitepaper belongs to the lawful rights holder.
Publication of this whitepaper does not constitute a waiver of rights in the technical configurations, system structures, or operating methods described herein, nor does it grant permission to freely reproduce, modify, implement, introduce, or commercially use them.
The technical configurations and system structures described in this whitepaper may be subject to separate intellectual property protection. Access to or publication of this whitepaper does not, by itself, grant any right of use or license concerning them.
Any partnership, technical implementation, licensing, or commercial use involving LOTTOi materials is subject to separate consultation and agreement with the rights holder.
Google documents store the actual generated number records.
GitHub fixes the corresponding Google document URL before the draw.
After the draw, anyone can compare both records and check whether post-draw changes occurred.
Based on public web research, LOTTOi has not found any identical prior case to date. Based on this research and the actual applied structure, LOTTOi describes this structure as a world-first-level external public verification framework.
| Date | Description |
|---|---|
| 2025. 02. 08. | Google-based external public verification method applied |
| 2026. 01. 29. | External public verification framework applied, fixing Google document URLs on GitHub before each draw |
| 2026. 02. 19. | Public verification whitepaper released |
LOTTOi has applied a Google-based external public verification method since February 8, 2025.
Since January 29, 2026, LOTTOi has applied an external public verification framework in which Google document URLs are first fixed on GitHub before the draw, allowing anyone to cross-check Google document records and GitHub commit history after the draw.
Based on public web research, LOTTOi has not found any identical prior case to date. Based on this research and the actual applied structure, LOTTOi describes this structure as a world-first-level external public verification framework.