It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
. | • Chinese : (ANN, Whitepaper) • Arabic : (ANN, Whitepaper) | • Japanese : (ANN, Whitepaper) • Russian : (ANN, Whitepaper) | • Korean : (ANN, Whitepaper) • Spanish : (ANN, Whitepaper) | • Vietnamese : (ANN, Whitepaper ) • German : (ANN, Whitepaper ) |
00000000000000000000000000000000000000 Philosophy • Reliability, Security, Portability, Compatibility are all paramount • Performance important: Multi-threaded, asynchronous. • General facilities that can be re-used 1) Support kernel-mode extensibility (for better or worse) 2) Provide unified mechanisms that can be shared 3) Kernel/executive split provides a clean layering model 4) Choose designs with architectural headroom | 00000000000000000000000000000000000000 Features • Highly multi-threaded in a process-like environment • Completely asynchronous I/O model • Thread-based scheduling • Unified management of kernel data structures, kernel references, user references (handles), namespace, synchronization objects, resource charging, cross- process sharing • Centralized ACL-based security reference monitor • Configuration store decoupled from a file system | 00000000000000000000000000000000000000 Mode • EXOS (aka ‘the kernel’) (a) Kernel layer (abstracts the CPU) (b) Executive layer (OS kernel functions) • Drivers (kernel-mode extension model) (1) Interface to devices (2) Implement file system, storage, networking (3) New kernel services • HAL (Hardware Abstraction Layer) (1) Hides Chipset/BIOS details (2) Allows EXOS and drivers to run unchanged |
. | 2014, Q-4 Project Idea Was Proposed | |
. | 2015, Q-1
The Team Was Build & Development Of Excalibur OS Was Started
Pages:
Jump to:
|