64 skills found · Page 1 of 3
airbus-seclab / SoxyA suite of services (SOCKS, FTP, shell, etc.) over Citrix, VMware Horizon and native Windows RDP virtual channels.
earthquake / UniversalDVCUniversal Dynamic Virtual Channel connector for Remote Desktop Services
tonywagner / EPlusTVVirtual linear channels for various providers
aignacio / RavenocRaveNoC is a configurable HDL NoC (Network-On-Chip) suitable for MPSoCs and different MP applications
jettbrains / L W3C Strategic Highlights September 2019 This report was prepared for the September 2019 W3C Advisory Committee Meeting (W3C Member link). See the accompanying W3C Fact Sheet — September 2019. For the previous edition, see the April 2019 W3C Strategic Highlights. For future editions of this report, please consult the latest version. A Chinese translation is available. ☰ Contents Introduction Future Web Standards Meeting Industry Needs Web Payments Digital Publishing Media and Entertainment Web & Telecommunications Real-Time Communications (WebRTC) Web & Networks Automotive Web of Things Strengthening the Core of the Web HTML CSS Fonts SVG Audio Performance Web Performance WebAssembly Testing Browser Testing and Tools WebPlatform Tests Web of Data Web for All Security, Privacy, Identity Internationalization (i18n) Web Accessibility Outreach to the world W3C Developer Relations W3C Training Translations W3C Liaisons Introduction This report highlights recent work of enhancement of the existing landscape of the Web platform and innovation for the growth and strength of the Web. 33 working groups and a dozen interest groups enable W3C to pursue its mission through the creation of Web standards, guidelines, and supporting materials. We track the tremendous work done across the Consortium through homogeneous work-spaces in Github which enables better monitoring and management. We are in the middle of a period where we are chartering numerous working groups which demonstrate the rapid degree of change for the Web platform: After 4 years, we are nearly ready to publish a Payment Request API Proposed Recommendation and we need to soon charter follow-on work. In the last year we chartered the Web Payment Security Interest Group. In the last year we chartered the Web Media Working Group with 7 specifications for next generation Media support on the Web. We have Accessibility Guidelines under W3C Member review which includes Silver, a new approach. We have just launched the Decentralized Identifier Working Group which has tremendous potential because Decentralized Identifier (DID) is an identifier that is globally unique, resolveable with high availability, and cryptographically verifiable. We have Privacy IG (PING) under W3C Member review which strengthens our focus on the tradeoff between privacy and function. We have a new CSS charter under W3C Member review which maps the group's work for the next three years. In this period, W3C and the WHATWG have succesfully completed the negotiation of a Memorandum of Understanding rooted in the mutual belief that that having two distinct specifications claiming to be normative is generally harmful for the Web community. The MOU, signed last May, describes how the two organizations are to collaborate on the development of a single authoritative version of the HTML and DOM specifications. W3C subsequently rechartered the HTML Working Group to assist the W3C community in raising issues and proposing solutions for the HTML and DOM specifications, and for the production of W3C Recommendations from WHATWG Review Drafts. As the Web evolves continuously, some groups are looking for ways for specifications to do so as well. So-called "evergreen recommendations" or "living standards" aim to track continuous development (and maintenance) of features, on a feature-by-feature basis, while getting review and patent commitments. We see the maturation and further development of an incredible number of new technologies coming to the Web. Continued progress in many areas demonstrates the vitality of the W3C and the Web community, as the rest of the report illustrates. Future Web Standards W3C has a variety of mechanisms for listening to what the community thinks could become good future Web standards. These include discussions with the Membership, discussions with other standards bodies, the activities of thousands of participants in over 300 community groups, and W3C Workshops. There are lots of good ideas. The W3C strategy team has been identifying promising topics and invites public participation. Future, recent and under consideration Workshops include: Inclusive XR (5-6 November 2019, Seattle, WA, USA) to explore existing and future approaches on making Virtual and Augmented Reality experiences more inclusive, including to people with disabilities; W3C Workshop on Data Models for Transportation (12-13 September 2019, Palo Alto, CA, USA) W3C Workshop on Web Games (27-28 June 2019, Redmond, WA, USA), view report Second W3C Workshop on the Web of Things (3-5 June 2019, Munich, Germany) W3C Workshop on Web Standardization for Graph Data; Creating Bridges: RDF, Property Graph and SQL (4-6 March 2019, Berlin, Germany), view report Web & Machine Learning. The Strategy Funnel documents the staff's exploration of potential new work at various phases: Exploration and Investigation, Incubation and Evaluation, and eventually to the chartering of a new standards group. The Funnel view is a GitHub Project where new area are issues represented by “cards” which move through the columns, usually from left to right. Most cards start in Exploration and move towards Chartering, or move out of the funnel. Public input is welcome at any stage but particularly once Incubation has begun. This helps W3C identify work that is sufficiently incubated to warrant standardization, to review the ecosystem around the work and indicate interest in participating in its standardization, and then to draft a charter that reflects an appropriate scope. Ongoing feedback can speed up the overall standardization process. Since the previous highlights document, W3C has chartered a number of groups, and started discussion on many more: Newly Chartered or Rechartered Web Application Security WG (03-Apr) Web Payment Security IG (17-Apr) Patent and Standards IG (24-Apr) Web Applications WG (14-May) Web & Networks IG (16-May) Media WG (23-May) Media and Entertainment IG (06-Jun) HTML WG (06-Jun) Decentralized Identifier WG (05-Sep) Extended Privacy IG (PING) (30-Sep) Verifiable Claims WG (30-Sep) Service Workers WG (31-Dec) Dataset Exchange WG (31-Dec) Web of Things Working Group (31-Dec) Web Audio Working Group (31-Dec) Proposed charters / Advance Notice Accessibility Guidelines WG Privacy IG (PING) RDF Literal Direction WG Timed Text WG CSS WG Web Authentication WG Closed Internationalization Tag Set IG Meeting Industry Needs Web Payments All Web Payments specifications W3C's payments standards enable a streamlined checkout experience, enabling a consistent user experience across the Web with lower front end development costs for merchants. Users can store and reuse information and more quickly and accurately complete online transactions. The Web Payments Working Group has republished Payment Request API as a Candidate Recommendation, aiming to publish a Proposed Recommendation in the Fall 2019, and is discussing use cases and features for Payment Request after publication of the 1.0 Recommendation. Browser vendors have been finalizing implementation of features added in the past year (view the implementation report). As work continues on the Payment Handler API and its implementation (currently in Chrome and Edge Canary), one focus in 2019 is to increase adoption in other browsers. Recently, Mastercard demonstrated the use of Payment Request API to carry out EMVCo's Secure Remote Commerce (SRC) protocol whose payment method definition is being developed with active participation by Visa, Mastercard, American Express, and Discover. Payment method availability is a key factor in merchant considerations about adopting Payment Request API. The ability to get uniform adoption of a new payment method such as Secure Remote Commerce (SRC) also depends on the availability of the Payment Handler API in browsers, or of proprietary alternatives. Web Monetization, which the Web Payments Working Group will discuss again at its face-to-face meeting in September, can be used to enable micropayments as an alternative revenue stream to advertising. Since the beginning of 2019, Amazon, Brave Software, JCB, Certus Cybersecurity Solutions and Netflix have joined the Web Payments Working Group. In April, W3C launched the Web Payment Security Group to enable W3C, EMVCo, and the FIDO Alliance to collaborate on a vision for Web payment security and interoperability. Participants will define areas of collaboration and identify gaps between existing technical specifications in order to increase compatibility among different technologies, such as: How do SRC, FIDO, and Payment Request relate? The Payment Services Directive 2 (PSD2) regulations in Europe are scheduled to take effect in September 2019. What is the role of EMVCo, W3C, and FIDO technologies, and what is the current state of readiness for the deadline? How can we improve privacy on the Web at the same time as we meet industry requirements regarding user identity? Digital Publishing All Digital Publishing specifications, Publication milestones The Web is the universal publishing platform. Publishing is increasingly impacted by the Web, and the Web increasingly impacts Publishing. Topic of particular interest to Publishing@W3C include typography and layout, accessibility, usability, portability, distribution, archiving, offline access, print on demand, and reliable cross referencing. And the diverse publishing community represented in the groups consist of the traditional "trade" publishers, ebook reading system manufacturers, but also publishers of audio book, scholarly journals or educational materials, library scientists or browser developers. The Publishing Working Group currently concentrates on Audiobooks which lack a comprehensive standard, thus incurring extra costs and time to publish in this booming market. Active development is ongoing on the future standard: Publication Manifest Audiobook profile for Web Publications Lightweight Packaging Format The BD Comics Manga Community Group, the Synchronized Multimedia for Publications Community Group, the Publishing Community Group and a future group on archival, are companions to the working group where specific work is developed and incubated. The Publishing Community Group is a recently launched incubation channel for Publishing@W3C. The goal of the group is to propose, document, and prototype features broadly related to: publications on the Web reading modes and systems and the user experience of publications The EPUB 3 Community Group has successfully completed the revision of EPUB 3.2. The Publishing Business Group fosters ongoing participation by members of the publishing industry and the overall ecosystem in the development of Web infrastructure to better support the needs of the industry. The Business Group serves as an additional conduit to the Publishing Working Group and several Community Groups for feedback between the publishing ecosystem and W3C. The Publishing BG has played a vital role in fostering and advancing the adoption and continued development of EPUB 3. In particular the BG provided critical support to the update of EPUBCheck to validate EPUB content to the new EPUB 3.2 specification. This resulted in the development, in conjunction with the EPUB3 Community Group, of a new generation of EPUBCheck, i.e., EPUBCheck 4.2 production-ready release. Media and Entertainment All Media specifications The Media and Entertainment vertical tracks media-related topics and features that create immersive experiences for end users. HTML5 brought standard audio and video elements to the Web. Standardization activities since then have aimed at turning the Web into a professional platform fully suitable for the delivery of media content and associated materials, enabling missing features to stream video content on the Web such as adaptive streaming and content protection. Together with Microsoft, Comcast, Netflix and Google, W3C received an Technology & Engineering Emmy Award in April 2019 for standardization of a full TV experience on the Web. Current goals are to: Reinforce core media technologies: Creation of the Media Working Group, to develop media-related specifications incubated in the WICG (e.g. Media Capabilities, Picture-in-picture, Media Session) and maintain maintain/evolve Media Source Extensions (MSE) and Encrypted Media Extensions (EME). Improve support for Media Timed Events: data cues incubation. Enhance color support (HDR, wide gamut), in scope of the CSS WG and in the Color on the Web CG. Reduce fragmentation: Continue annual releases of a common and testable baseline media devices, in scope of the Web Media APIs CG and in collaboration with the CTA WAVE Project. Maintain the Road-map of Media Technologies for the Web which highlights Web technologies that can be used to build media applications and services, as well as known gaps to enable additional use cases. Create the future: Discuss perspectives for Media and Entertainment for the Web. Bring the power of GPUs to the Web (graphics, machine learning, heavy processing), under incubation in the GPU for the Web CG. Transition to a Working Group is under discussion. Determine next steps after the successful W3C Workshop on Web Games of June 2019. View the report. Timed Text The Timed Text Working Group develops and maintains formats used for the representation of text synchronized with other timed media, like audio and video, and notably works on TTML, profiles of TTML, and WebVTT. Recent progress includes: A robust WebVTT implementation report poises the specification for publication as a proposed recommendation. Discussions around re-chartering, notably to add a TTML Profile for Audio Description deliverable to the scope of the group, and clarify that rendering of captions within XR content is also in scope. Immersive Web Hardware that enables Virtual Reality (VR) and Augmented Reality (AR) applications are now broadly available to consumers, offering an immersive computing platform with both new opportunities and challenges. The ability to interact directly with immersive hardware is critical to ensuring that the web is well equipped to operate as a first-class citizen in this environment. The Immersive Web Working Group has been stabilizing the WebXR Device API while the companion Immersive Web Community Group incubates the next series of features identified as key for the future of the Immersive Web. W3C plans a workshop focused on the needs and benefits at the intersection of VR & Accessibility (Inclusive XR), on 5-6 November 2019 in Seattle, WA, USA, to explore existing and future approaches on making Virtual and Augmented Reality experiences more inclusive. Web & Telecommunications The Web is the Open Platform for Mobile. Telecommunication service providers and network equipment providers have long been critical actors in the deployment of Web technologies. As the Web platform matures, it brings richer and richer capabilities to extend existing services to new users and devices, and propose new and innovative services. Real-Time Communications (WebRTC) All Real-Time Communications specifications WebRTC has reshaped the whole communication landscape by making any connected device a potential communication end-point, bringing audio and video communications anywhere, on any network, vastly expanding the ability of operators to reach their customers. WebRTC serves as the corner-stone of many online communication and collaboration services. The WebRTC Working Group aims to bringing WebRTC 1.0 (and companion specification Media Capture and Streams) to Recommendation by the end of 2019. Intense efforts are focused on testing (supported by a dedicated hackathon at IETF 104) and interoperability. The group is considering pushing features that have not gotten enough traction to separate modules or to a later minor revision of the spec. Beyond WebRTC 1.0, the WebRTC Working Group will focus its efforts on WebRTC NV which the group has started documenting by identifying use cases. Web & Networks Recently launched, in the wake of the May 2018 Web5G workshop, the Web & Networks Interest Group is chaired by representatives from AT&T, China Mobile and Intel, with a goal to explore solutions for web applications to achieve better performance and resource allocation, both on the device and network. The group's first efforts are around use cases, privacy & security requirements and liaisons. Automotive All Automotive specifications To create a rich application ecosystem for vehicles and other devices allowed to connect to the vehicle, the W3C Automotive Working Group is delivering a service specification to expose all common vehicle signals (engine temperature, fuel/charge level, range, tire pressure, speed, etc.) The Vehicle Information Service Specification (VISS), which is a Candidate Recommendation, is seeing more implementations across the industry. It provides the access method to a common data model for all the vehicle signals –presently encapsulating a thousand or so different data elements– and will be growing to accommodate the advances in automotive such as autonomous and driver assist technologies and electrification. The group is already working on a successor to VISS, leveraging the underlying data model and the VIWI submission from Volkswagen, for a more robust means of accessing vehicle signals information and the same paradigm for other automotive needs including location-based services, media, notifications and caching content. The Automotive and Web Platform Business Group acts as an incubator for prospective standards work. One of its task forces is using W3C VISS in performing data sampling and off-boarding the information to the cloud. Access to the wealth of information that W3C's auto signals standard exposes is of interest to regulators, urban planners, insurance companies, auto manufacturers, fleet managers and owners, service providers and others. In addition to components needed for data sampling and edge computing, capturing user and owner consent, information collection methods and handling of data are in scope. The upcoming W3C Workshop on Data Models for Transportation (September 2019) is expected to focus on the need of additional ontologies around transportation space. Web of Things All Web of Things specifications W3C's Web of Things work is designed to bridge disparate technology stacks to allow devices to work together and achieve scale, thus enabling the potential of the Internet of Things by eliminating fragmentation and fostering interoperability. Thing descriptions expressed in JSON-LD cover the behavior, interaction affordances, data schema, security configuration, and protocol bindings. The Web of Things complements existing IoT ecosystems to reduce the cost and risk for suppliers and consumers of applications that create value by combining multiple devices and information services. There are many sectors that will benefit, e.g. smart homes, smart cities, smart industry, smart agriculture, smart healthcare and many more. The Web of Things Working Group is finishing the initial Web of Things standards, with support from the Web of Things Interest Group: Web of Things Architecture Thing Descriptions Strengthening the Core of the Web HTML The HTML Working Group was chartered early June to assist the W3C community in raising issues and proposing solutions for the HTML and DOM specifications, and to produce W3C Recommendations from WHATWG Review Drafts. A few days before, W3C and the WHATWG signed a Memorandum of Understanding outlining the agreement to collaborate on the development of a single version of the HTML and DOM specifications. Issues and proposed solutions for HTML and DOM done via the newly rechartered HTML Working Group in the WHATWG repositories The HTML Working Group is targetting November 2019 to bring HTML and DOM to Candidate Recommendations. CSS All CSS specifications CSS is a critical part of the Open Web Platform. The CSS Working Group gathers requirements from two large groups of CSS users: the publishing industry and application developers. Within W3C, those groups are exemplified by the Publishing groups and the Web Platform Working Group. The former requires things like better pagination support and advanced font handling, the latter needs intelligent (and fast!) scrolling and animations. What we know as CSS is actually a collection of almost a hundred specifications, referred to as ‘modules’. The current state of CSS is defined by a snapshot, updated once a year. The group also publishes an index defining every term defined by CSS specifications. Fonts All Fonts specifications The Web Fonts Working Group develops specifications that allow the interoperable deployment of downloadable fonts on the Web, with a focus on Progressive Font Enrichment as well as maintenance of WOFF Recommendations. Recent and ongoing work includes: Early API experiments by Adobe and Monotype have demonstrated the feasibility of a font enrichment API, where a server delivers a font with minimal glyph repertoire and the client can query the full repertoire and request additional subsets on-the-fly. In other experiments, the Brotli compression used in WOFF 2 was extended to support shared dictionaries and patch update. Metrics to quantify improvement are a current hot discussion topic. The group will meet at ATypi 2019 in Japan, to gather requirements from the international typography community. The group will first produce a report summarizing the strengths and weaknesses of each prototype solution by Q2 2020. SVG All SVG specifications SVG is an important and widely-used part of the Open Web Platform. The SVG Working Group focuses on aligning the SVG 2.0 specification with browser implementations, having split the specification into a currently-implemented 2.0 and a forward-looking 2.1. Current activity is on stabilization, increased integration with the Open Web Platform, and test coverage analysis. The Working Group was rechartered in March 2019. A new work item concerns native (non-Web-browser) uses of SVG as a non-interactive, vector graphics format. Audio The Web Audio Working Group was extended to finish its work on the Web Audio API, expecting to publish it as a Recommendation by year end. The specification enables synthesizing audio in the browser. Audio operations are performed with audio nodes, which are linked together to form a modular audio routing graph. Multiple sources — with different types of channel layout — are supported. This modular design provides the flexibility to create complex audio functions with dynamic effects. The first version of Web Audio API is now feature complete and is implemented in all modern browsers. Work has started on the next version, and new features are being incubated in the Audio Community Group. Performance Web Performance All Web Performance specifications There are currently 18 specifications in development in the Web Performance Working Group aiming to provide methods to observe and improve aspects of application performance of user agent features and APIs. The W3C team is looking at related work incubated in the W3C GPU for the Web (WebGPU) Community Group which is poised to transition to a W3C Working Group. A preliminary draft charter is available. WebAssembly All WebAssembly specifications WebAssembly improves Web performance and power by being a virtual machine and execution environment enabling loaded pages to run native (compiled) code. It is deployed in Firefox, Edge, Safari and Chrome. The specification will soon reach Candidate Recommendation. WebAssembly enables near-native performance, optimized load time, and perhaps most importantly, a compilation target for existing code bases. While it has a small number of native types, much of the performance increase relative to Javascript derives from its use of consistent typing. WebAssembly leverages decades of optimization for compiled languages and the byte code is optimized for compactness and streaming (the web page starts executing while the rest of the code downloads). Network and API access all occurs through accompanying Javascript libraries -- the security model is identical to that of Javascript. Requirements gathering and language development occur in the Community Group while the Working Group manages test development, community review and progression of specifications on the Recommendation Track. Testing Browser testing plays a critical role in the growth of the Web by: Improving the reliability of Web technology definitions; Improving the quality of implementations of these technologies by helping vendors to detect bugs in their products; Improving the data available to Web developers on known bugs and deficiencies of Web technologies by publishing results of these tests. Browser Testing and Tools The Browser Testing and Tools Working Group is developing WebDriver version 2, having published last year the W3C Recommendation of WebDriver. WebDriver acts as a remote control interface that enables introspection and control of user agents, provides a platform- and language-neutral wire protocol as a way for out-of-process programs to remotely instruct the behavior of Web, and emulates the actions of a real person using the browser. WebPlatform Tests The WebPlatform Tests project now provides a mechanism which allows to fully automate tests that previously needed to be run manually: TestDriver. TestDriver enables sending trusted key and mouse events, sending complex series of trusted pointer and key interactions for things like in-content drag-and-drop or pinch zoom, and even file upload. Since 2014 W3C began work on this coordinated open-source effort to build a cross-browser test suite for the Web Platform, which WHATWG, and all major browsers adopted. Web of Data All Data specifications There have been several great success stories around the standardization of data on the web over the past year. Verifiable Claims seems to have significant uptake. It is also significant that the Distributed Identifier WG charter has received numerous favorable reviews, and was just recently launched. JSON-LD has been a major success with the large deployment on Web sites via schema.org. JSON-LD 1.1 completed technical work, about to transition to CR More than 25% of websites today include schema.org data in JSON-LD The Web of Things description is in CR since May, making use of JSON-LD Verifiable Credentials data model is in CR since July, also making use of JSON-LD Continued strong interest in decentralized identifiers Engagement from the TAG with reframing core documents, such as Ethical Web Principles, to include data on the web within their scope Data is increasingly important for all organizations, especially with the rise of IoT and Big Data. W3C has a mature and extensive suite of standards relating to data that were developed over two decades of experience, with plans for further work on making it easier for developers to work with graph data and knowledge graphs. Linked Data is about the use of URIs as names for things, the ability to dereference these URIs to get further information and to include links to other data. There are ever-increasing sources of open Linked Data on the Web, as well as data services that are restricted to the suppliers and consumers of those services. The digital transformation of industry is seeking to exploit advanced digital technologies. This will facilitate businesses to integrate horizontally along the supply and value chains, and vertically from the factory floor to the office floor. W3C is seeking to make it easier to support enterprise-wide data management and governance, reflecting the strategic importance of data to modern businesses. Traditional approaches to data have focused on tabular databases (SQL/RDBMS), Comma Separated Value (CSV) files, and data embedded in PDF documents and spreadsheets. We're now in midst of a major shift to graph data with nodes and labeled directed links between them. Graph data is: Faster than using SQL and associated JOIN operations More favorable to integrating data from heterogeneous sources Better suited to situations where the data model is evolving In the wake of the recent W3C Workshop on Graph Data we are in the process of launching a Graph Standardization Business Group to provide a business perspective with use cases and requirements, to coordinate technical standards work and liaisons with external organizations. Web for All Security, Privacy, Identity All Security specifications, all Privacy specifications Authentication on the Web As the WebAuthn Level 1 W3C Recommendation published last March is seeing wide implementation and adoption of strong cryptographic authentication, work is proceeding on Level 2. The open standard Web API gives native authentication technology built into native platforms, browsers, operating systems (including mobile) and hardware, offering protection against hacking, credential theft, phishing attacks, thus aiming to end the era of passwords as a security construct. You may read more in our March press release. Privacy An increasing number of W3C specifications are benefitting from Privacy and Security review; there are security and privacy aspects to every specification. Early review is essential. Working with the TAG, the Privacy Interest Group has updated the Self-Review Questionnaire: Security and Privacy. Other recent work of the group includes public blogging further to the exploration of anti-patterns in standards and permission prompts. Security The Web Application Security Working Group adopted Feature Policy, aiming to allow developers to selectively enable, disable, or modify the behavior of some of these browser features and APIs within their application; and Fetch Metadata, aiming to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used. The Web Payment Security Interest Group, launched last April, convenes members from W3C, EMVCo, and the FIDO Alliance to discuss cooperative work to enhance the security and interoperability of Web payments (read more about payments). Internationalization (i18n) All Internationalization specifications, educational articles related to Internationalization, spec developers checklist Only a quarter or so current Web users use English online and that proportion will continue to decrease as the Web reaches more and more communities of limited English proficiency. If the Web is to live up to the "World Wide" portion of its name, and for the Web to truly work for stakeholders all around the world engaging with content in various languages, it must support the needs of worldwide users as they engage with content in the various languages. The growth of epublishing also brings requirements for new features and improved typography on the Web. It is important to ensure the needs of local communities are captured. The W3C Internationalization Initiative was set up to increase in-house resources dedicated to accelerating progress in making the World Wide Web "worldwide" by gathering user requirements, supporting developers, and education & outreach. For an overview of current projects see the i18n radar. W3C's Internationalization efforts progressed on a number of fronts recently: Requirements: New African and European language groups will work on the gap analysis, errata and layout requirements. Gap analysis: Japanese, Devanagari, Bengali, Tamil, Lao, Khmer, Javanese, and Ethiopic updated in the gap-analysis documents. Layout requirements document: notable progress tracked in the Southeast Asian Task Force while work continues on Chinese layout requirements. Developer support: Spec reviews: the i18n WG continues active review of specifications of the WHATWG and other W3C Working Groups. Short review checklist: easy way to begin a self-review to help spec developers understand what aspects of their spec are likely to need attention for internationalization, and points them to more detailed checklists for the relevant topics. It also helps those reviewing specs for i18n issues. Strings on the Web: Language and Direction Metadata lays out issues and discusses potential solutions for passing information about language and direction with strings in JSON or other data formats. The document was rewritten for clarity, and expanded. The group is collaborating with the JSON-LD and Web Publishing groups to develop a plan for updating RDF, JSON-LD and related specifications to handle metadata for base direction of text (bidi). User-friendly test format: a new format was developed for Internationalization Test Suite tests, which displays helpful information about how the test works. This particularly useful because those tests are pointed to by educational materials and gap-analysis documents. Web Platform Tests: a large number of tests in the i18n test suite have been ported to the WPT repository, including: css-counter-styles, css-ruby, css-syntax, css-test, css-text-decor, css-writing-modes, and css-pseudo. Education & outreach: (for all educational materials, see the HTML & CSS Authoring Techniques) Web Accessibility All Accessibility specifications, WAI resources The Web Accessibility Initiative supports W3C's Web for All mission. Recent achievements include: Education and training: Inaccessibility of CAPTCHA updated to bring our analysis and recommendations up to date with CAPTCHA practice today, concluding two years of extensive work and invaluable input from the public (read more on the W3C Blog Learn why your web content and applications should be accessible. The Education and Outreach Working Group has completed revision and updating of the Business Case for Digital Accessibility. Accessibility guidelines: The Accessibility Guidelines Working Group has continued to update WCAG Techniques and Understanding WCAG 2.1; and published a Candidate Recommendation of Accessibility Conformance Testing Rules Format 1.0 to improve inter-rater reliability when evaluating conformance of web content to WCAG An updated charter is being developed to host work on "Silver", the next generation accessibility guidelines (WCAG 2.2) There are accessibility aspects to most specifications. Check your work with the FAST checklist. Outreach to the world W3C Developer Relations To foster the excellent feedback loop between Web Standards development and Web developers, and to grow participation from that diverse community, recent W3C Developer Relations activities include: @w3cdevs tracks the enormous amount of work happening across W3C W3C Track during the Web Conference 2019 in San Francisco Tech videos: W3C published the 2019 Web Games Workshop videos The 16 September 2019 Developer Meetup in Fukuoka, Japan, is open to all and will combine a set of technical demos prepared by W3C groups, and a series of talks on a selected set of W3C technologies and projects W3C is involved with Mozilla, Google, Samsung, Microsoft and Bocoup in the organization of ViewSource 2019 in Amsterdam (read more on the W3C Blog) W3C Training In partnership with EdX, W3C's MOOC training program, W3Cx offers a complete "Front-End Web Developer" (FEWD) professional certificate program that consists of a suite of five courses on the foundational languages that power the Web: HTML5, CSS and JavaScript. We count nearly 900K students from all over the world. Translations Many Web users rely on translations of documents developed at W3C whose official language is English. W3C is extremely grateful to the continuous efforts of its community in ensuring our various deliverables in general, and in our specifications in particular, are made available in other languages, for free, ensuring their exposure to a much more diverse set of readers. Last Spring we developed a more robust system, a new listing of translations of W3C specifications and updated the instructions on how to contribute to our translation efforts. W3C Liaisons Liaisons and coordination with numerous organizations and Standards Development Organizations (SDOs) is crucial for W3C to: make sure standards are interoperable coordinate our respective agenda in Internet governance: W3C participates in ICANN, GIPO, IGF, the I* organizations (ICANN, IETF, ISOC, IAB). ensure at the government liaison level that our standards work is officially recognized when important to our membership so that products based on them (often done by our members) are part of procurement orders. W3C has ARO/PAS status with ISO. W3C participates in the EU MSP and Rolling Plan on Standardization ensure the global set of Web and Internet standards form a compatible stack of technologies, at the technical and policy level (patent regime, fragmentation, use in policy making) promote Standards adoption equally by the industry, the public sector, and the public at large Coralie Mercier, Editor, W3C Marketing & Communications $Id: Overview.html,v 1.60 2019/10/15 12:05:52 coralie Exp $ Copyright © 2019 W3C ® (MIT, ERCIM, Keio, Beihang) Usage policies apply.
nktknshn / TgmountMount Telegram dialogs and channels as a Virtual File System.
nccgroup / FenrirPoC to tunnel the Meterpreter reverse HTTP shell over RDP Virtual Channels
abdulkarimgizzini / Enhancing Least Square Channel Estimation Using Deep LearningThis repository includes the source code of the LS-DNN based channel estimators proposed in "Enhancing Least Square Channel Estimation Using Deep Learning" paper that is published in the proceedings of the 2020 IEEE 91st Vehicular Technology Conference (VTC2020-Spring) virtual conference.
TKMAX777 / RDPRelativeInputSupports relative input in RDP (Remote Desktop Protocol) sessions from Windows to Windows using RDP Virtual Channels
javonn13 / AWS Basic For BeginnersThis course will teach you AWS basics right through to advanced cloud computing concepts. Ideal for beginners - absolutely no cloud computing experience is required! There are lots of hands-on exercises using an AWS free tier account to give you practical experience with Amazon Web Services. Visual slides and animations will help you gain a deep understanding of Cloud Computing. This is the perfect course for Beginners to the Cloud who want to learn the fundamentals of AWS - putting you in the perfect position to launch your AWS Certification journey and career in cloud computing. 👍 Download the course code and files here: https://digitalcloud.training/aws-bas... 👍 Access your free Guide to AWS Certifications (ebook) here: https://digitalcloud.training/aws-fre... 🎥 Course developed by Neal Davis - Founder of Digital Cloud Training 🔗 Check out the Digital Cloud Training YouTube channel: https://www.youtube.com/c/digitalclou... ⭐️ Course Contents ⭐️ (00:00:00) Course Introduction Section 1 - AWS Basics (00:00:53) Introduction (00:01:19) Amazon Web Services Overview (00:04:26) AWS Global Infrastructure (00:07:35) AWS Pricing (00:15:37) Setup your AWS Free Tier Account (00:21:19) Create a Billing Alarm (00:27:34) IAM Overview (00:32:47) Create IAM User and Group (00:37:38) Amazon Virtual Private Cloud (VPC) (00:48:36) Security Groups and Network ACLs (00:58:40) AWS Public and Private Services (01:00:51) Install the AWS Command Line Interface Section 2 - Amazon Elastic Compute Cloud (EC2) (01:02:08) Introduction (01:02:36) Amazon EC2 Overview (01:08:00) Launching an Amazon EC2 Instance (01:16:42) Connecting to Amazon EC2 Instances (01:27:48) Create a Website Using User Data (01:33:52) Using Access Keys with EC2 (01:34:50) Using IAM Roles with EC2 (01:39:05) Scale Elastically with Amazon EC2 Auto Scaling (01:47:47) Create a Target Tracking Scaling Policy (01:55:43) Add Load Balancing with Amazon ELB Section 3 - AWS Storage Services (02:09:52) Introduction (02:10:28) AWS Storage Services Overview (02:12:40) Create an Attach EBS Volume (02:20:47) Instance Store Volumes (02:23:34) EBS Snapshots and AMIs (02:31:38) Create Amazon EFS File System (02:40:26) Amazon S3 Create Bucket and Make Public (02:47:32) Working with S3 Objects from the AWS CLI Section 4 - AWS Databases (02:52:49) Introduction (02:53:28) Amazon RDS Overview (02:59:52) Create Amazon RDS Multi-AZ (03:10:35) Add an Amazon RDS Read Replica (03:16:18) Install WordPress on EC2 with RDS Database (03:23:56) Amazon DynamoDB Section 5 - Automation on AWS (03:34:34) Introduction (03:35:34) How to Deploy Infrastructure Using AWS CloudFormation (03:37:36) Create Simple Stacks with AWS CloudFormation (03:47:52) Create Complex Stack with AWS CloudFormation (03:56:45) Deploy an Application Using AWS Elastic Beanstalk Section 6 - DevOps on AWS (04:02:00) Introduction (04:02:43) Continuous Integration and Continuous Delivery (CI/CD) (04:05:55) AWS CodePipeline with AWS Elastic Beanstalk (04:15:26) Create AWS CodeStar Project Section 7 - DNS Services and Content Delivery (04:25:47) Introduction (04:26:23) Amazon Route 53 Overview and Routing Policies (04:30:22) Register Domain Using Route 53 (04:35:44) Create Amazon CloudFront Distribution with S3 Static Website (04:44:30) Add an SSL/TLS Certificate and Route 53 Alias Record Section 8 - Docker Containers and Serverless Computing (04:53:35) Introduction (04:54:34) Docker Containers on Amazon ECS (05:06:06) Serverless with AWS Lambda Section 9 - Application Integration and Loose Coupling (05:13:12) Introduction (05:14:01) Amazon SNS and Amazon SQS (05:16:32) AWS Lambda to Amazon SQS Event Source Mapping (05:22:49) Serverless Application - Amazon SQS, SNS, and Lambda 🔗 Digital Cloud Training: https://digitalcloud.training/ 🔗 LinkedIn: https://www.linkedin.com/in/nealkdavis/ 🔗 Twitter: https://twitter.com/nealkdavis 🔗 Instagram: https://www.instagram.com/digitalclou... 👍 AWS Cloud Practitioner - https://digitalcloud.training/amazon-... 👍 AWS Solutions Architect Associate - https://digitalcloud.training/amazon-...
Synacktiv-contrib / Rdp2tcprdp2tcp is a tunneling tool on top of remote desktop protocol (RDP). It uses RDP virtual channel capabilities to multiplex several ports forwarding over an already established rdesktop session.
Mikael / VIPBotIf you already know everything about hosting a bot, you can skip this text file. If not, I'll quickly run through the process of creating a Discord Bot account with you so you can get started with your own custom Discord bot. Also I'll give you a brief overview of the possible ways to host a bot. == 1) CREATING A DISCORD BOT ACCOUNT == You need a Discord bot account to be able to run the code I've written for you. - Make sure you're logged on the Discord *website* here: https://discord.com/ - Open up this page in your web browser: https://discord.com/developers/applications - Click the "New Application" button on the top right. - Give your application a name and then click "Create". - Create a Bot account by navigating to the "Bot" tab and clicking "Add Bot". - If you want your bot to be able to invited by others, tick the "Public Bot" checkbox. - Copy the Token using the "Copy" button. - Replace TOKEN in the config.json with the bot token you just copied. WARNING: Do not UNDER ANY CIRCUMSTANCES share this Token with anyone as it's like a password for your bot. A Discord employee will never ask for it. Also, if your Bot is public and someone gets hold of the Token, they can wreak havoc on any server that the bot is on, including potentially deleting all messages. If your Token got leaked, make sure to click "Regnerate" as fast as possible to minimize the damage. == 2) INVITING THE BOT TO YOUR SERVER == Now that your bot has been created, you can invite it to your server. - Now click the "OAuth2" tab on the application page you were on for creating your bot. - Tick the "bot" checkbox under "Scopes" - Tick the permissions your bot will need to function properly. You can find the necessary permissions in the text file called "Needed permissions.txt" - you can also give your bot the Administrator permission, but keep in mind that this means that the bot has every possible permission. - In the "Scopes" section you will find the link to invite your bot to any server that you have the "Manage Server" permission on. == 3) HOSTING THE BOT == There are in general two ways to host your bot: Either you host the bot yourself on your computer (or any other local machine you have physical access to like a Raspberry Pi or even a smartphone) or you host it on a VPS (= Virtual Private Server), which is basically a small, cheap server that runs 24/7. Both have advantages and disadvantages: - When you host the bot on a local device, it's way easier to setup the bot and get running quickly, yet you have to keep that device powered on all the time, which might be undesirable. - A cheap VPS will cost you a few bucks monthly and you have to use SSH to connect to it and set it up, but it will be powered on 24/7 and will usually be a better overall solution for such a bot. == 3a) HOSTING THE BOT ON A LOCAL DEVICE == To run the bot on a local device, you need to have Python installed and install the necessary modules for Python. You can download the newest version of Python here: https://www.python.org/. Make sure to let the installer include Python in $PATH. Now install the modules. You can do that on Windows by navigating into the folder where this text document is, pressing Shift + Right click anywhere in the folder, clicking "Open in PowerShell" and running this command: python -m pip install -r requirements.txt The steps should be very similar on Linux and macOS. If it says something along the lines of "'python' not found", try it with python3 instead or without "python -m" entirely and if it still doesn't work, your Python installation might be screwed up. Try reinstalling Python. To run your bot, just run "python main.py" (without quotation marks); "python3" instead of "python" might work too. If you get a message that looks like "python: can't open file 'main.py': [Errno 2] No such file or directory", you're probably not in the right folder with your command prompt. == 3b) HOSTING THE BOT ON A VPS == The process of hosting your bot on a VPS is more complicated and will inevitably require you to do most of the research on your own, but I can boil it down to the following steps (considering that your VPS runs some Linux distribution like Debian or CentOS - if it runs Windows, install a Linux distribution). In general: - First of all, get the VPS up and running and establish a connection to it via SSH* (native on Linux and Mac, use PuTTY on Windows for that) on your machine. - Transfer the whole folder with the bot over to the VPS over e.g. SFTP (you could use FileZilla for that and don't use normal FTP, it's not secure). - Configure the VPS to your needs (like installing Python and other needed programs and libraries). - Get a supervisor running (you could use supervisord for that) and let it take care of running your bot. - Take security measures like closing unneeded ports, using keyfiles for SSH, not allowing root connections with SSH etc. - Think of a good backup strategy, in case something happens to the valuable data on your VPS. If you're using a VPS, it's very easy to screw something up (like not properly securing the SSH connection with keyfiles), so please do *A LOT* of research on how to run and maintain a VPS, otherwise you might end up having your database leaked or something similar. If you have further questions about hosting a Discord bot, just hit me up, I'll be glad to help. But I will not host your bot. * SSH = Secure Shell, a way to securely build up a remote connection to a server and use the command line in it, also includes SFTP for file transfer == 4) VPS CHOICE == The discord.py community recommends the following VPS providers: - https://scaleway.com/ - Incredibly cheap but powerful VPSes, owned by https://online.net/, based in Europe. - https://digitalocean.com/ - US-based cheap VPSes. The gold standard. Locations available world wide. - https://ovh.co.uk/ - Cheap VPSes, used by many people. France and Canadian locations available. - https://time4vps.eu/ - Cheap VPSes, seemingly based in Lithuania. - https://linode.com/ - More cheap VPSes! - https://vultr.com/ - US-based, DigitalOcean-like. - https://galaxygate.net/ - A reliable, affordable, and trusted host, Used by Dank Memer, Rythm, and many other people. Using one of the cheaper options is usually a good start and will do just fine for small bots (up to a around hundred servers) and most providers will give you a way to smoothly upgrade your current plan. But it of course also depends on what your bot can do: Does it save a lot (= many gigabytes) data, is it usually in many voice channels, does it do image/video manipulation a lot? But there are lots of other providers, just do a Google search and you'll be sure to find the right one. Be wary of free hosting providers like Heraku, those services are not made to host Discord bots and you'll run into issues when trying to do so (believe me, I've fallen for them myself). If you have a spare Raspberry Pi, you can theoretically use it, but it will have subpar performance (especially if it's older or weaker than the Raspberry Pi 3B+). That's about it, hopefully this helped you. If there's something wrong with your bot or something's not working, contact me. - Mikael.
Mdshobu / Liberty House Club Whitepaper# Liberty House Club **A Parallel Binance Chain to Enable Smart Contracts** _NOTE: This document is under development. Please check regularly for updates!_ ## Table of Contents - [Motivation](#motivation) - [Design Principles](#design-principles) - [Consensus and Validator Quorum](#consensus-and-validator-quorum) * [Proof of Staked Authority](#proof-of-staked-authority) * [Validator Quorum](#validator-quorum) * [Security and Finality](#security-and-finality) * [Reward](#reward) - [Token Economy](#token-economy) * [Native Token](#native-token) * [Other Tokens](#other-tokens) - [Cross-Chain Transfer and Communication](#cross-chain-transfer-and-communication) * [Cross-Chain Transfer](#cross-chain-transfer) * [BC to BSC Architecture](#bc-to-bsc-architecture) * [BSC to BC Architecture](#bsc-to-bc-architecture) * [Timeout and Error Handling](#timeout-and-error-handling) * [Cross-Chain User Experience](#cross-chain-user-experience) * [Cross-Chain Contract Event](#cross-chain-contract-event) - [Staking and Governance](#staking-and-governance) * [Staking on BC](#staking-on-bc) * [Rewarding](#rewarding) * [Slashing](#slashing) - [Relayers](#relayers) * [BSC Relayers](#bsc-relayers) * [Oracle Relayers](#oracle-relayers) - [Outlook](#outlook) # Motivation After its mainnet community [launch](https://www.binance.com/en/blog/327334696200323072/Binance-DEX-Launches-on-Binance-Chain-Invites-Further-Community-Development) in April 2019, [Binance Chain](https://www.binance.org) has exhibited its high speed and large throughput design. Binance Chain’s primary focus, its native [decentralized application](https://en.wikipedia.org/wiki/Decentralized_application) (“dApp”) [Binance DEX](https://www.binance.org/trade), has demonstrated its low-latency matching with large capacity headroom by handling millions of trading volume in a short time. Flexibility and usability are often in an inverse relationship with performance. The concentration on providing a convenient digital asset issuing and trading venue also brings limitations. Binance Chain's most requested feature is the programmable extendibility, or simply the [Smart Contract](https://en.wikipedia.org/wiki/Smart_contract) and Virtual Machine functions. Digital asset issuers and owners struggle to add new decentralized features for their assets or introduce any sort of community governance and activities. Despite this high demand for adding the Smart Contract feature onto Binance Chain, it is a hard decision to make. The execution of a Smart Contract may slow down the exchange function and add non-deterministic factors to trading. If that compromise could be tolerated, it might be a straightforward idea to introduce a new Virtual Machine specification based on [Tendermint](https://tendermint.com/core/), based on the current underlying consensus protocol and major [RPC](https://docs.binance.org/api-reference/node-rpc.html) implementation of Binance Chain. But all these will increase the learning requirements for all existing dApp communities, and will not be very welcomed. We propose a parallel blockchain of the current Binance Chain to retain the high performance of the native DEX blockchain and to support a friendly Smart Contract function at the same time. # Design Principles After the creation of the parallel blockchain into the Binance Chain ecosystem, two blockchains will run side by side to provide different services. The new parallel chain will be called “**Binance Smart Chain**” (short as “**BSC**” for the below sections), while the existing mainnet remains named “**Binance Chain**” (short as “**BC**” for the below sections). Here are the design principles of **BSC**: 1. **Standalone Blockchain**: technically, BSC is a standalone blockchain, instead of a layer-2 solution. Most BSC fundamental technical and business functions should be self-contained so that it can run well even if the BC stopped for a short period. 2. **Ethereum Compatibility**: The first practical and widely-used Smart Contract platform is Ethereum. To take advantage of the relatively mature applications and community, BSC chooses to be compatible with the existing Ethereum mainnet. This means most of the **dApps**, ecosystem components, and toolings will work with BSC and require zero or minimum changes; BSC node will require similar (or a bit higher) hardware specification and skills to run and operate. The implementation should leave room for BSC to catch up with further Ethereum upgrades. 3. **Staking Involved Consensus and Governance**: Staking-based consensus is more environmentally friendly and leaves more flexible option to the community governance. Expectedly, this consensus should enable better network performance over [proof-of-work](https://en.wikipedia.org/wiki/Proof_of_work) blockchain system, i.e., faster blocking time and higher transaction capacity. 4. **Native Cross-Chain Communication**: both BC and BSC will be implemented with native support for cross-chain communication among the two blockchains. The communication protocol should be bi-directional, decentralized, and trustless. It will concentrate on moving digital assets between BC and BSC, i.e., [BEP2](https://github.com/binance-chain/BEPs/blob/master/BEP2.md) tokens, and eventually, other BEP tokens introduced later. The protocol should care for the minimum of other items stored in the state of the blockchains, with only a few exceptions. # Consensus and Validator Quorum Based on the above design principles, the consensus protocol of BSC is to fulfill the following goals: 1. Blocking time should be shorter than Ethereum network, e.g. 5 seconds or even shorter. 2. It requires limited time to confirm the finality of transactions, e.g. around 1-min level or shorter. 3. There is no inflation of native token: BNB, the block reward is collected from transaction fees, and it will be paid in BNB. 4. It is compatible with Ethereum system as much as possible. 5. It allows modern [proof-of-stake](https://en.wikipedia.org/wiki/Proof_of_stake) blockchain network governance. ## Proof of Staked Authority Although Proof-of-Work (PoW) has been recognized as a practical mechanism to implement a decentralized network, it is not friendly to the environment and also requires a large size of participants to maintain the security. Ethereum and some other blockchain networks, such as [MATIC Bor](https://github.com/maticnetwork/bor), [TOMOChain](https://tomochain.com/), [GoChain](https://gochain.io/), [xDAI](https://xdai.io/), do use [Proof-of-Authority(PoA)](https://en.wikipedia.org/wiki/Proof_of_authority) or its variants in different scenarios, including both testnet and mainnet. PoA provides some defense to 51% attack, with improved efficiency and tolerance to certain levels of Byzantine players (malicious or hacked). It serves as an easy choice to pick as the fundamentals. Meanwhile, the PoA protocol is most criticized for being not as decentralized as PoW, as the validators, i.e. the nodes that take turns to produce blocks, have all the authorities and are prone to corruption and security attacks. Other blockchains, such as EOS and Lisk both, introduce different types of [Delegated Proof of Stake (DPoS)](https://en.bitcoinwiki.org/wiki/DPoS) to allow the token holders to vote and elect the validator set. It increases the decentralization and favors community governance. BSC here proposes to combine DPoS and PoA for consensus, so that: 1. Blocks are produced by a limited set of validators 2. Validators take turns to produce blocks in a PoA manner, similar to [Ethereum’s Clique](https://eips.ethereum.org/EIPS/eip-225) consensus design 3. Validator set are elected in and out based on a staking based governance ## Validator Quorum In the genesis stage, a few trusted nodes will run as the initial Validator Set. After the blocking starts, anyone can compete to join as candidates to elect as a validator. The staking status decides the top 21 most staked nodes to be the next validator set, and such an election will repeat every 24 hours. **BNB** is the token used to stake for BSC. In order to remain as compatible as Ethereum and upgradeable to future consensus protocols to be developed, BSC chooses to rely on the **BC** for staking management (Please refer to the below “[Staking and Governance](#staking-and-governance)” section). There is a **dedicated staking module for BSC on BC**. It will accept BSC staking from BNB holders and calculate the highest staked node set. Upon every UTC midnight, BC will issue a verifiable `ValidatorSetUpdate` cross-chain message to notify BSC to update its validator set. While producing further blocks, the existing BSC validators check whether there is a `ValidatorSetUpdate` message relayed onto BSC periodically. If there is, they will update the validator set after an **epoch period**, i.e. a predefined number of blocking time. For example, if BSC produces a block every 5 seconds, and the epoch period is 240 blocks, then the current validator set will check and update the validator set for the next epoch in 1200 seconds (20 minutes). ## Security and Finality Given there are more than ½\*N+1 validators are honest, PoA based networks usually work securely and properly. However, there are still cases where certain amount Byzantine validators may still manage to attack the network, e.g. through the “[Clone Attack](https://arxiv.org/pdf/1902.10244.pdf)”. To secure as much as BC, BSC users are encouraged to wait until receiving blocks sealed by more than ⅔\*N+1 different validators. In that way, the BSC can be trusted at a similar security level to BC and can tolerate less than ⅓\*N Byzantine validators. With 21 validators, if the block time is 5 seconds, the ⅔\*N+1 different validator seals will need a time period of (⅔\*21+1)*5 = 75 seconds. Any critical applications for BSC may have to wait for ⅔\*N+1 to ensure a relatively secure finality. However, besides such arrangement, BSC does introduce **Slashing** logic to penalize Byzantine validators for **double signing** or **inavailability**, which will be covered in the “Staking and Governance” section later. This Slashing logic will expose the malicious validators in a very short time and make the “Clone Attack” very hard or extremely non-beneficial to execute. With this enhancement, ½\*N+1 or even fewer blocks are enough as confirmation for most transactions. ## Reward All the BSC validators in the current validator set will be rewarded with transaction **fees in BNB**. As BNB is not an inflationary token, there will be no mining rewards as what Bitcoin and Ethereum network generate, and the gas fee is the major reward for validators. As BNB is also utility tokens with other use cases, delegators and validators will still enjoy other benefits of holding BNB. The reward for validators is the fees collected from transactions in each block. Validators can decide how much to give back to the delegators who stake their BNB to them, in order to attract more staking. Every validator will take turns to produce the blocks in the same probability (if they stick to 100% liveness), thus, in the long run, all the stable validators may get a similar size of the reward. Meanwhile, the stakes on each validator may be different, so this brings a counter-intuitive situation that more users trust and delegate to one validator, they potentially get less reward. So rational delegators will tend to delegate to the one with fewer stakes as long as the validator is still trustful (insecure validator may bring slashable risk). In the end, the stakes on all the validators will have less variation. This will actually prevent the stake concentration and “winner wins forever” problem seen on some other networks. Some parts of the gas fee will also be rewarded to relayers for Cross-Chain communication. Please refer to the “[Relayers](#relayers)” section below. # Token Economy BC and BSC share the same token universe for BNB and BEP2 tokens. This defines: 1. The same token can circulate on both networks, and flow between them bi-directionally via a cross-chain communication mechanism. 2. The total circulation of the same token should be managed across the two networks, i.e. the total effective supply of a token should be the sum of the token’s total effective supply on both BSC and BC. 3. The tokens can be initially created on BSC in a similar format as ERC20 token standard, or on BC as a BEP2, then created on the other. There are native ways on both networks to link the two and secure the total supply of the token. ## Native Token BNB will run on BSC in the same way as ETH runs on Ethereum so that it remains as “native token” for both BSC and BC. This means, in addition to BNB is used to pay most of the fees on Binance Chain and Binance DEX, BNB will be also used to: 1. pay “fees“ to deploy smart contracts on BSC 2. stake on selected BSC validators, and get corresponding rewards 3. perform cross-chain operations, such as transfer token assets across BC and BSC ### Seed Fund Certain amounts of BNB will be burnt on BC and minted on BSC during its genesis stage. This amount is called “Seed Fund” to circulate on BSC after the first block, which will be dispatched to the initial BC-to-BSC Relayer(described in later sections) and initial validator set introduced at genesis. These BNBs are used to pay transaction fees in the early stage to transfer more BNB from BC onto BSC via the cross-chain mechanism. The BNB cross-chain transfer is discussed in a later section, but for BC to BSC transfer, it is generally to lock BNB on BC from the source address of the transfer to a system-controlled address and unlock the corresponding amount from special contract to the target address of the transfer on BSC, or reversely, when transferring from BSC to BC, it is to lock BNB from the source address on BSC into a special contract and release locked amount on BC from the system address to the target address. The logic is related to native code on BC and a series of smart contracts on BSC. ## Other Tokens BC supports BEP2 tokens and upcoming [BEP8 tokens](https://github.com/binance-chain/BEPs/pull/69), which are native assets transferrable and tradable (if listed) via fast transactions and sub-second finality. Meanwhile, as BSC is Ethereum compatible, it is natural to support ERC20 tokens on BSC, which here is called “**BEP2E**” (with the real name to be introduced by the future BEPs,it potentially covers BEP8 as well). BEP2E may be “Enhanced” by adding a few more methods to expose more information, such as token denomination, decimal precision definition and the owner address who can decide the Token Binding across the chains. BSC and BC work together to ensure that one token can circulate in both formats with confirmed total supply and be used in different use cases. ### Token Binding BEP2 tokens will be extended to host a new attribute to associate the token with a BSC BEP2E token contract, called “**Binder**”, and this process of association is called “**Token Binding**”. Token Binding can happen at any time after BEP2 and BEP2E are ready. The token owners of either BEP2 or BEP2E don’t need to bother about the Binding, until before they really want to use the tokens on different scenarios. Issuers can either create BEP2 first or BEP2E first, and they can be bound at a later time. Of course, it is encouraged for all the issuers of BEP2 and BEP2E to set the Binding up early after the issuance. A typical procedure to bind the BEP2 and BEP2E will be like the below: 1. Ensure both the BEP2 token and the BEP2E token both exist on each blockchain, with the same total supply. BEP2E should have 3 more methods than typical ERC20 token standard: * symbol(): get token symbol * decimals(): get the number of the token decimal digits * owner(): get **BEP2E contract owner’s address.** This value should be initialized in the BEP2E contract constructor so that the further binding action can verify whether the action is from the BEP2E owner. 2. Decide the initial circulation on both blockchains. Suppose the total supply is *S*, and the expected initial circulating supply on BC is *K*, then the owner should lock S-K tokens to a system controlled address on BC. 3. Equivalently, *K* tokens is locked in the special contract on BSC, which handles major binding functions and is named as **TokenHub**. The issuer of the BEP2E token should lock the *K* amount of that token into TokenHub, resulting in *S-K* tokens to circulate on BSC. Thus the total circulation across 2 blockchains remains as *S*. 4. The issuer of BEP2 token sends the bind transaction on BC. Once the transaction is executed successfully after proper verification: * It transfers *S-K* tokens to a system-controlled address on BC. * A cross-chain bind request package will be created, waiting for Relayers to relay. 5. BSC Relayers will relay the cross-chain bind request package into **TokenHub** on BSC, and the corresponding request and information will be stored into the contract. 6. The contract owner and only the owner can run a special method of TokenHub contract, `ApproveBind`, to verify the binding request to mark it as a success. It will confirm: * the token has not been bound; * the binding is for the proper symbol, with proper total supply and decimal information; * the proper lock are done on both networks; 10. Once the `ApproveBind` method has succeeded, TokenHub will mark the two tokens are bounded and share the same circulation on BSC, and the status will be propagated back to BC. After this final confirmation, the BEP2E contract address and decimals will be written onto the BEP2 token as a new attribute on BC, and the tokens can be transferred across the two blockchains bidirectionally. If the ApproveBind fails, the failure event will also be propagated back to BC to release the locked tokens, and the above steps can be re-tried later. # Cross-Chain Transfer and Communication Cross-chain communication is the key foundation to allow the community to take advantage of the dual chain structure: * users are free to create any tokenization, financial products, and digital assets on BSC or BC as they wish * the items on BSC can be manually and programmingly traded and circulated in a stable, high throughput, lighting fast and friendly environment of BC * users can operate these in one UI and tooling ecosystem. ## Cross-Chain Transfer The cross-chain transfer is the key communication between the two blockchains. Essentially the logic is: 1. the `transfer-out` blockchain will lock the amount from source owner addresses into a system controlled address/contracts; 2. the `transfer-in` blockchain will unlock the amount from the system controlled address/contracts and send it to target addresses. The cross-chain transfer package message should allow the BSC Relayers and BC **Oracle Relayers** to verify: 1. Enough amount of token assets are removed from the source address and locked into a system controlled addresses/contracts on the source blockchain. And this can be confirmed on the target blockchain. 2. Proper amounts of token assets are released from a system controlled addresses/contracts and allocated into target addresses on the target blockchain. If this fails, it can be confirmed on source blockchain, so that the locked token can be released back (may deduct fees). 3. The sum of the total circulation of the token assets across the 2 blockchains are not changed after this transfer action completes, no matter if the transfer succeeds or not.  The architecture of cross-chain communication is as in the above diagram. To accommodate the 2 heteroid systems, communication handling is different in each direction. ## BC to BSC Architecture BC is a Tendermint-based, instant finality blockchain. Validators with at least ⅔\*N+1 of the total voting power will co-sign each block on the chain. So that it is practical to verify the block transactions and even the state value via **Block Header** and **Merkle Proof** verification. This has been researched and implemented as “**Light-Client Protocol**”, which are intensively discussed in [the Ethereum](https://github.com/ethereum/wiki/wiki/Light-client-protocol) community, studied and implemented for [Cosmos inter-chain communication](https://github.com/cosmos/ics/blob/a4173c91560567bdb7cc9abee8e61256fc3725e9/spec/ics-007-tendermint-client/README.md). BC-to-BSC communication will be verified in an “**on-chain light client**” implemented via BSC **Smart Contracts** (some of them may be **“pre-compiled”**). After some transactions and state change happen on BC, if a transaction is defined to trigger cross-chain communication,the Cross-chain “**package**” message will be created and **BSC Relayers** will pass and submit them onto BSC as data into the "build-in system contracts". The build-in system contracts will verify the package and execute the transactions if it passes the verification. The verification will be guaranteed with the below design: 1. BC blocking status will be synced to the light client contracts on BSC from time to time, via block header and pre-commits, for the below information: * block and app hash of BC that are signed by validators * current validatorset, and validator set update 2. the key-value from the blockchain state will be verified based on the Merkle Proof and information from above #1. After confirming the key-value is accurate and trustful, the build-in system contracts will execute the actions corresponding to the cross-chain packages. Some examples of such packages that can be created for BC-to-BSC are: 1. Bind: bind the BEP2 tokens and BEP2E 2. Transfer: transfer tokens after binding, this means the circulation will decrease (be locked) from BC and appear in the target address balance on BSC 3. Error Handling: to handle any timeout/failure event for BSC-to-BC communication 4. Validatorset update of BSC To ensure no duplication, proper message sequence and timely timeout, there is a “Channel” concept introduced on BC to manage any types of the communication. For relayers, please also refer to the below “Relayers” section. ## BSC to BC Architecture BSC uses Proof of Staked Authority consensus protocol, which has a chance to fork and requires confirmation of more blocks. One block only has the signature of one validator, so that it is not easy to rely on one block to verify data from BSC. To take full advantage of validator quorum of BC, an idea similar to many [Bridge ](https://github.com/poanetwork/poa-bridge)or Oracle blockchains is adopted: 1. The cross-chain communication requests from BSC will be submitted and executed onto BSC as transactions. The execution of the transanction wil emit `Events`, and such events can be observed and packaged in certain “**Oracle**” onto BC. Instead of Block Headers, Hash and Merkle Proof, this type of “Oracle” package directly contains the cross-chain information for actions, such as sender, receiver and amount for transfer. 2. To ensure the security of the Oracle, the validators of BC will form anothe quorum of “**Oracle Relayers**”. Each validator of the BC should run a **dedicated process** as the Oracle Relayer. These Oracle Relayers will submit and vote for the cross-chain communication package, like Oracle, onto BC, using the same validator keys. Any package signed by more than ⅔\*N+1 Oracle Relayers’ voting power is as secure as any block signed by ⅔\*N+1 of the same quorum of validators’ voting power. By using the same validator quorum, it saves the light client code on BC and continuous block updates onto BC. Such Oracles also have Oracle IDs and types, to ensure sequencing and proper error handling. ## Timeout and Error Handling There are scenarios that the cross-chain communication fails. For example, the relayed package cannot be executed on BSC due to some coding bug in the contracts. **Timeout and error handling logics are** used in such scenarios. For the recognizable user and system errors or any expected exceptions, the two networks should heal themselves. For example, when BC to BSC transfer fails, BSC will issue a failure event and Oracle Relayers will execute a refund on BC; when BSC to BC transfer fails, BC will issue a refund package for Relayer to relay in order to unlock the fund. However, unexpected error or exception may still happen on any step of the cross-chain communication. In such a case, the Relayers and Oracle Relayers will discover that the corresponding cross-chain channel is stuck in a particular sequence. After a Timeout period, the Relayers and Oracle Relayers can request a “SkipSequence” transaction, the stuck sequence will be marked as “Unexecutable”. A corresponding alerts will be raised, and the community has to discuss how to handle this scenario, e.g. payback via the sponsor of the validators, or event clear the fund during next network upgrade. ## Cross-Chain User Experience Ideally, users expect to use two parallel chains in the same way as they use one single chain. It requires more aggregated transaction types to be added onto the cross-chain communication to enable this, which will add great complexity, tight coupling, and maintenance burden. Here BC and BSC only implement the basic operations to enable the value flow in the initial launch and leave most of the user experience work to client side UI, such as wallets. E.g. a great wallet may allow users to sell a token directly from BSC onto BC’s DEX order book, in a secure way. ## Cross-Chain Contract Event Cross-Chain Contract Event (CCCE) is designed to allow a smart contract to trigger cross-chain transactions, directly through the contract code. This becomes possible based on: 1. Standard system contracts can be provided to serve operations callable by general smart contracts; 2. Standard events can be emitted by the standard contracts; 3. Oracle Relayers can capture the standard events, and trigger the corresponding cross-chain operations; 4. Dedicated, code-managed address (account) can be created on BC and accessed by the contracts on the BSC, here it is named as **“Contract Address on BC” (CAoB)**. Several standard operations are implemented: 1. BSC to BC transfer: this is implemented in the same way as normal BSC to BC transfer, by only triggered via standard contract. The fund can be transferred to any addresses on BC, including the corresponding CAoB of the transfer originating contract. 2. Transfer on BC: this is implemented as a special cross-chain transfer, while the real transfer is from **CAoB** to any other address (even another CAoB). 3. BC to BSC transfer: this is implemented as two-pass cross-chain communication. The first is triggered by the BSC contract and propagated onto BC, and then in the second pass, BC will start a normal BC to BSC cross-chain transfer, from **CAoB** to contract address on BSC. A special note should be paid on that the BSC contract only increases balance upon any transfer coming in on the second pass, and the error handling in the second pass is the same as the normal BC to BSC transfer. 4. IOC (Immediate-Or-Cancel) Trade Out: the primary goal of transferring assets to BC is to trade. This event will instruct to trade a certain amount of an asset in CAoB into another asset as much as possible and transfer out all the results, i.e. the left the source and the traded target tokens of the trade, back to BSC. BC will handle such relayed events by sending an “Immediate-Or-Cancel”, i.e. IOC order onto the trading pairs, once the next matching finishes, the result will be relayed back to BSC, which can be in either one or two assets. 5. Auction Trade Out: Such event will instruct BC to send an auction order to trade a certain amount of an asset in **CAoB** into another asset as much as possible and transfer out all the results back to BSC at the end of the auction. Auction function is upcoming on BC. There are some details for the Trade Out: 1. both can have a limit price (absolute or relative) for the trade; 2. the end result will be written as cross-chain packages to relay back to BSC; 3. cross-chain communication fees may be charged from the asset transferred back to BSC; 4. BSC contract maintains a mirror of the balance and outstanding orders on CAoB. No matter what error happens during the Trade Out, the final status will be propagated back to the originating contract and clear its internal state. With the above features, it simply adds the cross-chain transfer and exchange functions with high liquidity onto all the smart contracts on BSC. It will greatly add the application scenarios on Smart Contract and dApps, and make 1 chain +1 chain > 2 chains. # Staking and Governance Proof of Staked Authority brings in decentralization and community involvement. Its core logic can be summarized as the below. You may see similar ideas from other networks, especially Cosmos and EOS. 1. Token holders, including the validators, can put their tokens “**bonded**” into the stake. Token holders can **delegate** their tokens onto any validator or validator candidate, to expect it can become an actual validator, and later they can choose a different validator or candidate to **re-delegate** their tokens<sup>1</sup>. 2. All validator candidates will be ranked by the number of bonded tokens on them, and the top ones will become the real validators. 3. Validators can share (part of) their blocking reward with their delegators. 4. Validators can suffer from “**Slashing**”, a punishment for their bad behaviors, such as double sign and/or instability. 5. There is an “**unbonding period**” for validators and delegators so that the system makes sure the tokens remain bonded when bad behaviors are caught, the responsible will get slashed during this period. ## Staking on BC Ideally, such staking and reward logic should be built into the blockchain, and automatically executed as the blocking happens. Cosmos Hub, who shares the same Tendermint consensus and libraries with Binance Chain, works in this way. BC has been preparing to enable staking logic since the design days. On the other side, as BSC wants to remain compatible with Ethereum as much as possible, it is a great challenge and efforts to implement such logic on it. This is especially true when Ethereum itself may move into a different Proof of Stake consensus protocol in a short (or longer) time. In order to keep the compatibility and reuse the good foundation of BC, the staking logic of BSC is implemented on BC: 1. The staking token is BNB, as it is a native token on both blockchains anyway 2. The staking, i.e. token bond and delegation actions and records for BSC, happens on BC. 3. The BSC validator set is determined by its staking and delegation logic, via a staking module built on BC for BSC, and propagated every day UTC 00:00 from BC to BSC via Cross-Chain communication. 4. The reward distribution happens on BC around every day UTC 00:00. ## Rewarding Both the validator update and reward distribution happen every day around UTC 00:00. This is to save the cost of frequent staking updates and block reward distribution. This cost can be significant, as the blocking reward is collected on BSC and distributed on BC to BSC validators and delegators. (Please note BC blocking fees will remain rewarding to BC validators only.) A deliberate delay is introduced here to make sure the distribution is fair: 1. The blocking reward will not be sent to validator right away, instead, they will be distributed and accumulated on a contract; 2. Upon receiving the validator set update into BSC, it will trigger a few cross-chain transfers to transfer the reward to custody addresses on the corresponding validators. The custody addresses are owned by the system so that the reward cannot be spent until the promised distribution to delegators happens. 3. In order to make the synchronization simpler and allocate time to accommodate slashing, the reward for N day will be only distributed in N+2 days. After the delegators get the reward, the left will be transferred to validators’ own reward addresses. ## Slashing Slashing is part of the on-chain governance, to ensure the malicious or negative behaviors are punished. BSC slash can be submitted by anyone. The transaction submission requires **slash evidence** and cost fees but also brings a larger reward when it is successful. So far there are two slashable cases. ### Double Sign It is quite a serious error and very likely deliberate offense when a validator signs more than one block with the same height and parent block. The reference protocol implementation should already have logic to prevent this, so only the malicious code can trigger this. When Double Sign happens, the validator should be removed from the Validator **Set** right away. Anyone can submit a slash request on BC with the evidence of Double Sign of BSC, which should contain the 2 block headers with the same height and parent block, sealed by the offending validator. Upon receiving the evidence, if the BC verifies it to be valid: 1. The validator will be removed from validator set by an instance BSC validator set update Cross-Chain update; 2. A predefined amount of BNB would be slashed from the **self-delegated** BNB of the validator; Both validator and its delegators will not receive the staking rewards. 3. Part of the slashed BNB will allocate to the submitter’s address, which is a reward and larger than the cost of submitting slash request transaction 4. The rest of the slashed BNB will allocate to the other validators’ custody addresses, and distributed to all delegators in the same way as blocking reward. ### Inavailability The liveness of BSC relies on everyone in the Proof of Staked Authority validator set can produce blocks timely when it is their turn. Validators can miss their turn due to any reason, especially problems in their hardware, software, configuration or network. This instability of the operation will hurt the performance and introduce more indeterministic into the system. There can be an internal smart contract responsible for recording the missed blocking metrics of each validator. Once the metrics are above the predefined threshold, the blocking reward for validator will not be relayed to BC for distribution but shared with other better validators. In such a way, the poorly-operating validator should be gradually voted out of the validator set as their delegators will receive less or none reward. If the metrics remain above another higher level of threshold, the validator will be dropped from the rotation, and this will be propagated back to BC, then a predefined amount of BNB would be slashed from the **self-delegated** BNB of the validator. Both validators and delegators will not receive their staking rewards. ### Governance Parameters There are many system parameters to control the behavior of the BSC, e.g. slash amount, cross-chain transfer fees. All these parameters will be determined by BSC Validator Set together through a proposal-vote process based on their staking. Such the process will be carried on BC, and the new parameter values will be picked up by corresponding system contracts via a cross-chain communication. # Relayers Relayers are responsible to submit Cross-Chain Communication Packages between the two blockchains. Due to the heterogeneous parallel chain structure, two different types of Relayers are created. ## BSC Relayers Relayers for BC to BSC communication referred to as “**BSC Relayers**”, or just simply “Relayers”. Relayer is a standalone process that can be run by anyone, and anywhere, except that Relayers must register themselves onto BSC and deposit a certain refundable amount of BNB. Only relaying requests from the registered Relayers will be accepted by BSC. The package they relay will be verified by the on-chain light client on BSC. The successful relay needs to pass enough verification and costs gas fees on BSC, and thus there should be incentive reward to encourage the community to run Relayers. ### Incentives There are two major communication types: 1. Users triggered Operations, such as `token bind` or `cross chain transfer`. Users must pay additional fee to as relayer reward. The reward will be shared with the relayers who sync the referenced blockchain headers. Besides, the reward won't be paid the relayers' accounts directly. A reward distribution mechanism will be brought in to avoid monopolization. 2. System Synchronization, such as delivering `refund package`(caused by failures of most oracle relayers), special blockchain header synchronization(header contains BC validatorset update), BSC staking package. System reward contract will pay reward to relayers' accounts directly. If some Relayers have faster networks and better hardware, they can monopolize all the package relaying and leave no reward to others. Thus fewer participants will join for relaying, which encourages centralization and harms the efficiency and security of the network. Ideally, due to the decentralization and dynamic re-election of BSC validators, one Relayer can hardly be always the first to relay every message. But in order to avoid the monopolization further, the rewarding economy is also specially designed to minimize such chance: 1. The reward for Relayers will be only distributed in batches, and one batch will cover a number of successful relayed packages. 2. The reward a Relayer can get from a batch distribution is not linearly in proportion to their number of successful relayed packages. Instead, except the first a few relays, the more a Relayer relays during a batch period, the less reward it will collect. ## Oracle Relayers Relayers for BSC to BC communication are using the “Oracle” model, and so-called “**Oracle Relayers**”. Each of the validators must, and only the ones of the validator set, run Oracle Relayers. Each Oracle Relayer watches the blockchain state change. Once it catches Cross-Chain Communication Packages, it will submit to vote for the requests. After Oracle Relayers from ⅔ of the voting power of BC validators vote for the changes, the cross-chain actions will be performed. Oracle Replayers should wait for enough blocks to confirm the finality on BSC before submitting and voting for the cross-chain communication packages onto BC. The cross-chain fees will be distributed to BC validators together with the normal BC blocking rewards. Such oracle type relaying depends on all the validators to support. As all the votes for the cross-chain communication packages are recorded on the blockchain, it is not hard to have a metric system to assess the performance of the Oracle Relayers. The poorest performer may have their rewards clawed back via another Slashing logic introduced in the future. # Outlook It is hard to conclude for Binance Chain, as it has never stopped evolving. The dual-chain strategy is to open the gate for users to take advantage of the fast transferring and trading on one side, and flexible and extendable programming on the other side, but it will be one stop along the development of Binance Chain. Here below are the topics to look into so as to facilitate the community better for more usability and extensibility: 1. Add different digital asset model for different business use cases 2. Enable more data feed, especially DEX market data, to be communicated from Binance DEX to BSC 3. Provide interface and compatibility to integrate with Ethereum, including its further upgrade, and other blockchain 4. Improve client side experience to manage wallets and use blockchain more conveniently ------ [1]: BNB business practitioners may provide other benefits for BNB delegators, as they do now for long term BNB holders.
nccgroup / SleipnirTiny payload for transfer via LOKI - Provides high speed Virtual Channel two way file transfer capabilities
TanayGhanshyam / Crispy Octo GuideWe have come a long way since I was a child in the 1960s when all I wanted for Christmas was a slinky and some Rock’Em – Sock’Em Robots. Now imagine we have traveled ten years into the future, and it is Christmas 2031. Alexa has replaced kids’ parents and Santa Claus. Every toy is connected to the Internet and looks like a robot version of the animal it represents. Clean thermonuclear Christmas trees will be providing us with radiant, gamma-ray energy for all our holiday needs. Pogo sticks have also made a comeback, but they are solar-powered and can leap entire city blocks. And while I am busy pretending to be the Ghost of Christmas Future, I thought it would also be fun to ask the Office of the CTO team about their predictions for futuristic, technical toys. So, I posed these two questions: What cool TECHNICAL toy or gadget would you like Santa to bring you this year in 2021? As a participating member of the Office of the CTO, what cool TECHNICAL toy or gadget (that has not yet been invented) would you like Santa to bring you in 10 years from now in 2031? christmas wishlist for the octo team overlay You know what? We just might see I see a sneak preview of some of these magical tech toys of the future in just a few weeks at the CES 2022 conference. In the meantime, take a look at the wish list from all of our Extreme technical gurus: Marcus Burton – Wireless and Cloud Architect Christmas Wish 2021: Is a Tesla Cybertruck an option? I’ll even take a prototype. That will scratch several technology itches at the same time. Think about it…EV, autonomous driving, AI, 5G probably, cloud-connected, mobile-first, and all the best in materials sciences and mechanical engineering applied to trucks. What more could an outdoorsy tech guy want? Christmas Wish 2031: I’m kinda thinking that while everyone else has their brain slurped out in the metaverse (with VR!), I will prefer to go to the actual mountains. But you know, I have a wife and kids, so I have to think about safety. So here’s my wish: a smart personal device that has a full week of battery life (using ultra-thin silicon wafers) with rapid solar charging, LEO satellite connectivity (for sending “eat your heart out” 3D pics to my friends from the “there’s no 6G here” wilderness), and ultra-HD terrain feature maps for modern navigation. Carla Guzzetti – VP, Experience, Messaging & Enablement Christmas Wish 2021: I want this: Meeting Owl Pro – 360-Degree, 1080p HD Smart Video Conference Camera, Microphone, and Speaker Christmas Wish 2031: I want a gadget where we can have virtual meetings without the need for a wearable! Who wants to wear heavy goggles all day? Doug McDonald – Director of Product Management Christmas Wish 2021: As a technologist often looking for a balance between screen time and health and fitness I hope Santa brings me the Aura Strap. The Aura strap adds additional IoT sensory capabilities to compliment your Apple smartwatch. Bioelectrical impedance analysis is the cutting-edge science behind the AURA Strap. This innovation provides a way to truly see how your body changes over the course of a day. Their body composition analysis includes fat, muscle mass, minerals, and hydration; providing personalized insights that improve the results of your workouts, diet, and your lifestyle as a whole. Christmas Wish 2031: Hopefully, this innovation will be here sooner. Still, in the spirit of my first wish from Santa, I also hope to have a service engine warning light for me. The concept is utilizing advancements in biomedical sensory devices to pinpoint potential changes in your physical metrics that may help in seeking medical attention sooner than later if variances in health data occur. I spoke about this concept in the Digital Diagnosis episode of the Inflection Points podcast from the Office of the CTO. Ed Koehler – Principal Engineer Christmas Wish 2021: My answers are short and sweet. I want a nice drone with high-resolution pan, tilt, and zoom (PTZ) cameras. Christmas Wish 2031: In ten years, I want a drone that I can sit inside and fly away! Puneet Sehgal – Business Initiatives Program Manager Christmas Wish 2021: I have always wanted to enjoy the world from a bird’s eye view. Therefore, my wish is for Santa to bring me a good-quality drone camera this year. It is amazing how quickly drones have evolved from commercial /military use to becoming a personal gadget. Christmas Wish 2031: In 2031, I wish Santa could get me a virtual reality (VR) trainer to help me internalize physical motion by looking at a simulation video while sending an electrical impulse to mimic it. It will open endless possibilities, and I could become an ice skater, a karate expert, or a pianist – all in one. Maybe similar research is already being done, but we are far away from something like this maturing for practical use. So, who knows – it’s Santa after all and we are talking 2031! Tim Harrison – Director of Product Marketing, Service Provider Christmas Wish 2021: This year, I would love to extend my audio recording setup and move from a digital 24 channel mixer to a control surface that integrates with my DAW (digital audio workstation) and allows me to use my outboard microphone pre-amps. I’ve been looking at an ICON QCon Pro G2 plus one QCon EX G2 extender to give me direct control over 16 channels at once (I use 16 channels just for my drum kit). Christmas Wish 2031: Ten years from now, I sincerely hope to receive an anti-gravity platform. First, I’ll be old, and climbing stairs will have become more challenging for these creaky old bones. Secondly, who hasn’t hoped for a REAL hoverboard? Once we know what gravity is “made of,” we can start making it easier to manipulate objects on earth and make space more habitable for human physiology. Either that or a puppy. Puppy sitting Divya Balu Pazhayannur – Director of Business Initiatives Christmas Wish 2021: I’m upgrading parts of my house over the holidays and browsing online for kitchen and laundry appliances. If you had told me that I would be spending three hours reading blogs on choosing the right cooktop for me, I would not have believed you. Does it have the right power, is it reliable, is it Wi-Fi enabled, can you talk to it – I’m kidding on that last one. Having said that, I’d love to get the Bosch Benchmark Gas Stovetop. Although I can’t speak to my appliance, its minimalist look has me writing it down on my wish list for Santa. I’ll even offer him some crispy dosas in exchange. Christmas Wish 2031: Apart from flying cars and personal robot assistants, I’d love to get the gift of better connectivity. I miss my family and friends in India, and it would be amazing to engage with them through holographic technology. I imagine it would allow for a much higher level of communication than today’s ‘talking head’ approach. Although do I want my family sitting with me in my living room? Still – I’d like to think a holograph would be just fantastic. Yury Ostrovsky – Sr. Technology Manager Christmas Wish 2021: I believe 2022 will be the year of VR toys. Virtual Reality is already popular, but I believe more applications will be developed in this area. We might see radio waves coming from different sources (Wi-Fi, LTE, 5G, BT, etc.) and visualize propagation in real-time. Christmas Wish 2031: “Prediction is very difficult, especially if it’s about the future” – Niels Bohr Kurt Semba – Principal Architect Christmas Wish 2021: The Crown from Neurosity. It helps you get and stay in a deep focus to improve your work and gaming results. Christmas Wish 2031: A non-evasive health device that can quickly look deep into your body and cells and explain why you are not feeling well today. Jon Filson – Senior Producer, Content Christmas Wish 2021: I want a large rollable TV by LG. In part because I watch a lot of football. And while I have a Smart TV, I still can’t get it to connect to my Bluetooth speaker … so while I love it, I want it to work better, and isn’t that so often the way with tech? But more than that, I don’t like and have never liked that rooms have to be designed around TVs. They are big, which is fine, but they are often in the way, which is less so. They should disappear when not in use. It’s $100,000 so I don’t expect it any time soon. But it’s an idea whose time has come. Christmas Wish 2031: I cheated on this one and asked my 12-year-old son Jack what he would want. It’s the portal gun, from Rick and Morty, a show in which a crazed scientist named Rick takes his grandson Morty on wacky adventures in a multi-verse. That last part is important to me. Kids today are already well into multi-verses, while we adults are just struggling to make one decent Metaverse. The next generation is already way ahead of us digitally speaking, it’s clear. Alexey Reznik – Senior UX Designer Christmas Wish 2021: This awesome toy: DJI Mavic 2 Pro – Drone Quadcopter UAV with Hasselblad Camera 3-Axis Gimbal HDR 4K Video Adjustable Aperture 20MP 1″ CMOS Sensor, up to 48mph, Gray Christmas Wish 2031: Something along these lines: BMW Motorrad VISION NEXT 100 BMW Motorcycle Michael Rash – Distinguished Engineer – Security Christmas Wish 2021: Satechi USB-C Multiport MX Adapter – Dual 4K HDMI. Christmas Wish 2031: A virtual reality headset that actually works. Alena Amir – Senior Content and Communications Manager Christmas Wish 2021: With conversations around VR/AR and the metaverse taking the world by storm, Santa could help out with an Oculus Quest. Purely for research purposes of course! Christmas Wish 2031: The 1985 movie, Back to the Future, was a family favorite and sure we didn’t get it all exactly right by 2015 but hey, it’s almost 2022! About time we get those hoverboards! David Coleman – Director of Wireless Christmas Wish 2021: Well, it looks like drones are the #1 wish item for 2021, and I am no exception. My wife and I just bought a home in the mountains of Blue Ridge, Georgia, where there is an abundance of wildlife. I want a state-of-the-art drone for bear surveillance. Christmas Wish 2031: In ten years, I will be 71 years old, and I hope to be at least semi-retired and savoring the fruits of my long tech career. Even though we are looking to the future, I want a time machine to revisit the past. I would travel back to July 16th, 1969, and watch Apollo 11 liftoff from Cape Kennedy to the moon. I actually did that as a nine-year-old kid. Oh, and I would also travel back to 1966 and play with my Rock’Em – Sock’Em Robots. Rock'em Sock'em Robots To summarize, our peeps in the Office of the CTO all envision Christmas 2031, where the way we interact as a society will have progressed. In 2021, we already have unlimited access to information, so future tech toys might depend less on magical new technologies and more on the kinds of experiences these new technologies can create. And when those experiences can be shared across the globe in real-time, the world gains an opportunity to learn from each other and grow together in ways that would never have been possible.
lasseufpa / SSP RaymobtimeCodes and Data for the paper: Klautau, A., Oliveira, A., Pamplona, I. & Alves, W.. Generating MIMO Channels For 6G Virtual Worlds Using Ray-Tracing Simulations. IEEE Statistical Signal Processing Workshop, 2021.
htytewx / Softcam@___________________________________________@ @_______________SOFTCAM KEYS________________@ @_______UPDATE ® 31-03-2020______@ # # ############################################# # IRDETO 2 KEYS # ############################################# I 0604 02 DFDD0C4B92B4ABD26514B9AF9F0C79C4 ;Bulsatcom (39.0°E) I 0604 03 E94B84B099000C5DFD04C4C09AA022E9 ;Bulsatcom (39.0°E) I 0604 04 B39A18E24597DB0C3A1D71E722D35012 ;Bulsatcom (39.0°E) I 0604 06 D3940957F4B27B9E5A17EB1AE0F98A09 ;Bulsatcom (39.0°E) I 0604 M1 98B4DCAD44E8C9504C3F4E51692A7047 ;Bulsatcom (39.0°E) I 0604 M2 AE652B210BF89FC69507609842FD303E ;Bulsatcom (39.0°E) ############################################# #______________VIACCESS 2 KEYS______________# ############################################# V 021110 08 35F6B9217C2BA83F38C3C1FD23A5D321 ;Ant-1 (9.0°E) V 021110 D1 89CBB54EEB94E350 ;Des1_Key V 021110 X1 12BF4D2F2A10F590 ;XORArray V 021110 P1 0704020305000601 ;PermArray V 021110 C1 E96B9FD44D3D335E ;ChainArray V 021110 T1 9453847eee7345cfd1d482d3603036ecd6cd9af5da1fe5243e715cea8641ba1528a747c2172edcd920968e752f4a252c0d38ab4ca56e0e8d31644e5e7761189f781dfa85fd065922f7e92d9533a93ae8f1e788015de3d29262465ff21a543b5a0c3d58c939d8ae7f876cbfd569ce35c49b19c105c82bac3c40edb1fcbc990367a4b80aa102431c6852f8beffb6372aefb9a657bb004b29b4db7d1270e1aab53fd083b7e280349121e44d9d3276f066dfde7accc7979e8ca281901e937cc38a6ae67223bd6ff6cab37463c6feb2116d07a008560b096b10e06527149826ebb0afd79ca355a816c0514f491bdd0f79048fad505bf4f313c54889fb42f97b44cb8b ;TransformTable ############################################# #____________NAGRAVISION 2 KEYS_____________# ############################################# N 1102 00 F8780ECD862D143B9B23ECFFCBB872A4 ;UnityMedia Cable TV (German) N 1102 01 FAD9E99827B3D66B624FA382E52615E1 ;UnityMedia Cable TV (German) N 1102 M1 C75C2FECF494F6DD71BBF898C63F7FEBA11345DF14C71EE656BC23016C2F90A881429B82A68C095E472C997752D5890341CF9E06691672482718750B918AAE92 ;UnityMedia Cable TV (German) N 2111 00 69AA57C76AFCAAEEF4048183CB19395E ;Digi TV Cablu (Romania Cable TV) N 2111 01 10F5DB01646FD8852C0BCCA160F0B337 ;Digi TV Cablu (Romania Cable TV) N 2111 M1 7508665801DC6815F8DF965641A8C27CAE056ED0249CF60F60DEDD75A3A84D486E85285220F133439F038BFE54975543C8DFC4205067985E5CDAD7ABA4CF48A7 ;Digi TV Cablu (Romania Cable TV) N 7301 00 DB697B9CC19122AD0A92586091B64A73 ;Cablecom Swiss Cable TV (Switzerland) N 7301 01 5FD284AA40E9A4A35484305C41A3C3F5 ;Cablecom Swiss Cable TV (Switzerland) N 7301 M1 7544E982065D53E7CF049AF2E725544A50268DA1462F15D8A197ECE4B80FE221122F92AD56324380A04878EBF563427DD85C38645907583E23AC5153E300CF84 ;Cablecom Swiss Cable TV (Switzerland) ############################################# #_______________TANDBERG KEYS_______________# ############################################# T 0001 01 5FDB06AA1364E500 ;CNBC Asia Regional - 3900 H 30000 T 0002 01 CA138BF89FBE0E00 ;CNBC Asia Australia - 3900 H 30000 T 0003 01 52614F2CB05D3801 ;CNBC Asia NTSC - 3900 H 30000 T 0004 01 345E9B5B97D5BC01 ;CNBC Asia Feeds - 3900 H 30000 ------------------------------------------------------ T 0001 01 5FDB06AA1364E500 ;VTV 1 (132.0°E) - 3590 V 19200 T 03E8 01 8BAD71EFB7A83C00 ;VTV 2 (132.0°E) - 3590 V 19200 T 03E9 01 8BAD71EFB7A83C00 ;VTV 3 (132.0°E) - 3590 V 19200 T 03EA 01 8BAD71EFB7A83C00 ;VTV 4 (132.0°E) - 3590 V 19200 T 03EB 01 8BAD71EFB7A83C00 ;VTV 5 (132.0°E) - 3590 V 19200 T 03EC 01 8BAD71EFB7A83C00 ;VTV 6 (132.0°E) - 3590 V 19200 T 03ED 01 8BAD71EFB7A83C00 ;VTV 7 (132.0°E) - 3590 V 19200 T 1ED5 01 67A8578D03D5C400 ;VTV 8 (132.0°E) - 3590 V 19200 T 2706 01 D22D9D72FBB4B200 ;VTV 9 (132.0°E) - 3590 V 19200 ------------------------------------------------------ T 03E8 01 8BAD71EFB7A83C00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0691 01 D6B8F64C9AD2C000 ;IMG Asia (100.5°E) - 3700 V 30000 T 0693 01 E71E624D1EDB3B00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0694 01 EB62121C009B8A00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0695 01 8D4A0B4EEA27DE00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0696 01 559DBE62B3947A00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0697 01 B7ED31D476BA9000 ;IMG Asia (100.5°E) - 3700 V 30000 T 0698 01 2BB8F2CD65578F00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0699 01 9BD67458CF5DA900 ;IMG Asia (100.5°E) - 3700 V 30000 T 069A 01 800123885DA12500 ;IMG Asia (100.5°E) - 3700 V 30000 T 069B 01 C6825C05FD5DC700 ;IMG Asia (100.5°E) - 3700 V 30000 T 069C 01 C122F250366C2F00 ;IMG Asia (100.5°E) - 3700 V 30000 T 069D 01 27904CA5A5A7D700 ;IMG Asia (100.5°E) - 3700 V 30000 T 069E 01 4618FCB0B03AAF00 ;IMG Asia (100.5°E) - 3700 V 30000 T 069F 01 428EBDA9392D9200 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A0 01 F61D2EA2C8AA9F00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A1 01 9971A078E3051000 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A2 01 BF538FA113116D00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A3 01 D028080CD00F0700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A3 01 D07448EDD0E20700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A4 01 DAD06D00AE187600 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A5 01 D6FFFD6184C91300 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A6 01 DF4E07D7E1EB2900 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A7 01 8005CDDECE661B00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A8 01 E2CF78630B05DE00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06A9 01 1F3CEF98BDDAD000 ;IMG Asia (100.5°E) - 3700 V 30000 T 06AA 01 45BF4929CB5AA100 ;IMG Asia (100.5°E) - 3700 V 30000 T 06AB 01 76FAE104CC992700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06AC 01 131AF25142BCDF00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06AD 01 334E284293193E00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06AE 01 C59BE490A41A6D00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06AF 01 191547A11D534500 ;IMG Asia (100.5°E) - 3700 V 30000 T 06B0 01 3F76A21EBA443C00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06B1 01 5057B34A7111DF00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06B2 01 17A7D5868E5D6500 ;IMG Asia (100.5°E) - 3700 V 30000 T 06B3 01 9CF9F31197D74900 ;IMG Asia (100.5°E) - 3700 V 30000 T 06B4 01 6C186179163D1300 ;IMG Asia (100.5°E) - 3700 V 30000 T 06B5 01 BB0A1DB27E16E600 ;IMG Asia (100.5°E) - 3700 V 30000 T 06BA 01 75878DB5E6097E00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06BB 01 3AA5C5571DEA6800 ;IMG Asia (100.5°E) - 3700 V 30000 T 06BC 01 A82264A361B01C00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06BD 01 AF73935FEB51B100 ;IMG Asia (100.5°E) - 3700 V 30000 T 06BE 01 680E27BCD45A2C00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06BF 01 1BE03EA95364B600 ;IMG Asia (100.5°E) - 3700 V 30000 T 06C0 01 424265AB464A5400 ;IMG Asia (100.5°E) - 3700 V 30000 T 06CA 01 9785EB816CDF3300 ;IMG3 ASIA (100.5°E) - 3700 V 30000 T 06CB 01 3A895BA6C9821800 ;IMG3 ASIA (100.5°E) - 3700 V 30000 T 06CD 01 430B68C82A19F400 ;IMG3 ASIA (100.5°E) - 3700 V 30000 T 06CF 01 4B4395DA68E32C00 ;IMG3 ASIA (100.5°E) - 3700 V 30000 T 06D0 01 CD2EFB597E558000 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D1 01 364C9FC2F307DC00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D2 01 472AA83AF065E700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D4 01 148B1057D3C7B100 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D5 01 504517CE48271300 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D6 01 32A03B66435B8E00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D7 01 3087CCA158E35300 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D8 01 48ED360FA371FC00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06D9 01 D3216EC5F0CC0700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06DA 01 80D64B3567990700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06DB 01 A6B539A669827600 ;IMG Asia (100.5°E) - 3700 V 30000 T 06DC 01 B0E1E98275E6D100 ;IMG Asia (100.5°E) - 3700 V 30000 T 06DD 01 5EFF1C1EDB73C300 ;IMG Asia (100.5°E) - 3700 V 30000 T 06DE 01 083EC62B3DD2C800 ;IMG Asia (100.5°E) - 3700 V 30000 T 06DF 01 94A3C50960865200 ;IMG Asia (100.5°E) - 3700 V 30000 T 06E1 01 77856E84B31FF800 ;IMG Asia (100.5°E) - 3700 V 30000 T 06E2 01 77856E2442A49700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06E3 01 B1EB88562DFEE900 ;IMG Asia (100.5°E) - 3700 V 30000 T 06E5 01 901D56235A9B1600 ;IMG Asia (100.5°E) - 3700 V 30000 T 06E7 01 A682A0838B1ADE00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06E8 01 1BC827B4DD438800 ;IMG Asia (100.5°E) - 3700 V 30000 T 06EC 01 70AF5CBBE6AE3600 ;IMG Asia (100.5°E) - 3700 V 30000 T 06F4 01 C785192D37D34100 ;IMG Asia (100.5°E) - 3700 V 30000 T 06F5 01 FC8D04A0D08C6E00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06F7 01 29F6BFA4F194D700 ;IMG Asia (100.5°E) - 3700 V 30000 T 06F9 01 907BA1CDE77C3C00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06FC 01 42091073E1CEE300 ;IMG Asia (100.5°E) - 3700 V 30000 T 06FD 01 45E2D915B7761E00 ;IMG Asia (100.5°E) - 3700 V 30000 T 06FE 01 8279A503E28E4400 ;IMG Asia (100.5°E) - 3700 V 30000 T 06FF 01 4785D1D6183D8000 ;IMG Asia (100.5°E) - 3700 V 30000 T 0700 01 794171490CB43B00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0701 01 00EF34E7134C0000 ;IMG Asia (100.5°E) - 3700 V 30000 T 0702 01 0EA9D5125F21C800 ;IMG Asia (100.5°E) - 3700 V 30000 T 0703 01 2D4D640338D5E200 ;IMG Asia (100.5°E) - 3700 V 30000 T 0704 01 A511447B0092BE00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0705 01 5A4006C95B65BE00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0706 01 D53ACCC0A0A22F00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0707 01 E1A2FD0BB4962500 ;IMG Asia (100.5°E) - 3700 V 30000 T 0709 01 F10378E187746B00 ;IMG Asia (100.5°E) - 3700 V 30000 T 070A 01 3EC7AAFF76975400 ;IMG Asia (100.5°E) - 3700 V 30000 T 070B 01 1B2B5A63C8E8E300 ;IMG Asia (100.5°E) - 3700 V 30000 T 070C 01 388158C2FE107300 ;IMG Asia (100.5°E) - 3700 V 30000 T 070D 01 CBABBFAA84E6F800 ;IMG Asia (100.5°E) - 3700 V 30000 T 070E 01 CBABBFFA1A3C1B00 ;IMG Asia (100.5°E) - 3700 V 30000 T 070F 01 BCBFB1035029C500 ;IMG Asia (100.5°E) - 3700 V 30000 T 0710 01 71C21288C9ED1C00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0711 01 14FE08A5B89D6C00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0712 01 971394EB7B550A00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0713 01 F4825CD9B20B0B00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0714 01 8FF9B482352D8200 ;IMG Asia (100.5°E) - 3700 V 30000 T 0715 01 B1A06954A54F3400 ;IMG Asia (100.5°E) - 3700 V 30000 T 0716 01 6E182D3D3B328F00 ;IMG Asia (100.5°E) - 3700 V 30000 T 0717 01 54A824DFF1305300 ;IMG Asia (100.5°E) - 3700 V 30000 T 0718 01 B271E187ED4DD300 ;IMG Asia (100.5°E) - 3700 V 30000 T 0719 01 8D21635CF99CE400 ;IMG Asia (100.5°E) - 3700 V 30000 T 071A 01 8E2208E28B115300 ;IMG Asia (100.5°E) - 3700 V 30000 T 071B 01 E8B1CF202D4D9100 ;IMG Asia (100.5°E) - 3700 V 30000 T 2706 01 D22D9D72FBB4B200 ;Wimbledon World Feed (100.5°E) - 3700 V 30000 T 2710 01 D35184AEEC8BE800 ;Wimbledon World Feed (100.5°E) - 3700 V 30000 T 1605 01 F384528231F80300 ;ADS 7 (100.5°E) - 3720 H 30000 T 1606 01 677F3A34205E0500 ;ADS 8 (100.5°E) - 3720 H 30000 T 1607 01 DB445F86ADC23800 ;ADS 9 (100.5°E) - 3720 H 30000 T 1608 01 F4C1ECFF64C9A700 ;ADS 10 (100.5°E) - 3720 H 30000 T 1609 01 C72CD9ABB6CC0800 ;ADS 11 (100.5°E) - 3720 H 30000 T 160A 01 5DECE324A52B2400 ;ADS 12 (100.5°E) - 3720 H 30000 T 0A26 01 B7D9C24C62827700 ;MDS09,10,11,12 50 (100.5°E) - 3860 V 30000 T 045B 01 32C718C11FF46D00 ;U21 (100.5°E) - 3869 H 7120 T 0A26 01 B7D9C24C62827700 ;MDS05,06,07,08 50 (100.5°E) - 3880 H 30000 T 0083 01 4DB639DF3C4A2D00 ;ARQ-PL7 GOALS (100.5°E) - 3915 V 7120 T 0084 01 EDB30CBA1EFB0500 ;ARQ-PL9 GOALS (100.5°E) - 3915 V 7120 T 1839 01 67392044053A9700 ;Service 01 (100.5°E) - 3918 H 22500 T 183A 01 70B5118415394400 ;Service 02 (100.5°E) - 3918 H 22500 T 183B 01 737AFC24357EE900 ;Service 03 (100.5°E) - 3918 H 22500 T 183C 01 9EE1C959DABDBB00 ;Service 04 (100.5°E) - 3918 H 22500 T 183D 01 5D243DE3E2934600 ;Service 05 (100.5°E) - 3918 H 22500 T 03E8 01 8BAD71EFB7A83C00 ;Service 1 (100.5°E) - 3920 H 30000 T 03E9 01 8BAD71EFB7A83C00 ;Service 2 (100.5°E) - 3920 H 30000 T 03EA 01 8BAD71EFB7A83C00 ;Service 3 (100.5°E) - 3920 H 30000 T 03EB 01 8BAD71EFB7A83C00 ;Service 4 (100.5°E) - 3920 H 30000 T 03EC 01 8BAD71EFB7A83C00 ;Service 5 (100.5°E) - 3920 H 30000 T 03ED 01 8BAD71EFB7A83C00 ;Service 6 (100.5°E) - 3920 H 30000 T 1603 01 BE363F46A0380400 ;ADS 5 (100.5°E) - 3924 H 7300 T 16E5 01 C33C139292471600 ;ONC50 (100.5°E) - 3954 V 7200 T 1959 01 405E18941A49DA00 :MDS01,02,03,04 50 (100.5°E) - 3954 V 7200 T 224A 01 7293AFF5D46C2D00 ;ONC 50 (100.5°E) - 3954 V 7200 T 0001 01 5FDB06AA1364E500 ;MDS01 50 (100.5°E) - 4080 H 30000 T 0A26 01 B7D9C24C62827700 ;MDS02,04 50 (100.5°E) - 4080 H 30000 T 2140 01 0660C5AFE5251800 ;MDS03 50 (100.5°E) - 4080 H 30000 ------------------------------------------------------ T 0002 01 CA138BF89FBE0E00 ;RTM 2 Malaysia (91.5°E) - 3918 H 18385 T 0004 01 345E9B5B97D5BC01 ;RTM 4 Malaysia (91.5°E) - 3918 H 18385 T 0005 01 9EFB52CDD0FBA101 ;RTM 5 Malaysia (91.5°E) - 3918 H 18385 ------------------------------------------------------ T 1FE1 01 9949B980E7C58200 ;Tandberg CAS T 1FE2 01 4EE1E799EFB4D100 ;Tandberg CAS T 1FE3 01 D1DA152B295BC400 ;Tandberg CAS T 1FE4 01 75BEB21A50820900 ;Tandberg CAS T 1FE5 01 9CB8C8C1ED2B0000 ;Tandberg CAS T 1FE6 01 58AC530EE1A5A400 ;Tandberg CAS T 1FE7 01 A04B3B54D990AA00 ;Tandberg CAS ------------------------------------------------------ T 07D7 01 EF35D1892E2FD000 ;U21 (10.0°E) - 11125 H 7120 T 07DE 01 332B97C503956200 ;PITCH TEST (10.0°E) - 11125 H 7120 T 03E8 01 8BAD71EFB7A83C00 ;MDS01,02,03,04,05 50 (10.0°E) - 11387 V 30000 T 1959 01 405E18941A49DA00 ;MDS01,02,03,04 50 (10.0°E) - 11387 V 30000 T 1ED5 01 67A8578D03D5C400 ;MDS01 50 (10.0°E) - 11387 V 30000 T 2140 01 0660C5AFE5251800 ;MDS01,02,03,04 50 (10.0°E) - 11387 V 30000 T 0084 01 EDB30CBA1EFB0500 ;ARQ-PL9 CLIPS (10.0°E) - 11605 H 7200 T 1839 01 67392044053A9700 ;SERVICE 1 (10.0°E) - 11637 V 22500 T 183A 01 70B5118415394400 ;SERVICE 2 (10.0°E) - 11637 V 22500 T 183B 01 737AFC24357EE900 ;SERVICE 3 (10.0°E) - 11637 V 22500 T 183C 01 9EE1C959DABDBB00 ;SERVICE 4 (10.0°E) - 11637 V 22500 T 183D 01 5D243DE3E2934600 ;SERVICE 5 (10.0°E) - 11637 V 22500 T 1839 01 67392044053A9700 ;SERVICE 1 (10.0°E) - 12634 H 15000 T 183A 01 70B5118415394400 ;SERVICE 2 (10.0°E) - 12634 H 15000 T 183B 01 737AFC24357EE900 ;SERVICE 3 (10.0°E) - 12634 H 15000 ------------------------------------------------------ T 2705 01 3AC4EAEA7CA2EC00 ;Wimbledon World Feed (7.0°E) - 10960 H 9875 3/4 T 2706 01 D22D9D72FBB4B200 ;WF50 Wimbledon (7.0°E) - 10960 H 9875 3/4 T 2710 01 D35184AEEC8BE800 ;Wimbledon World Feed (7.0°E) - 10960 H 9875 3/4 T 04FE 01 8E75452BFEBF3F00 ;IMG A Studio (7.0°E) - 11020 V 7200 T 0691 01 D6B8F64C9AD2C000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0692 01 D6B8F69CE5612200 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0693 01 E71E624D1EDB3B00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0694 01 EB62121C009B8A00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0695 01 8D4A0B4EEA27DE00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0696 01 559DBE62B3947A00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0697 01 B7ED31D476BA9000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0698 01 2BB8F2CD65578F00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0699 01 9BD67458CF5DA900 ;IMG3 EU (7.0°E) - 11020 V 7200 T 069A 01 800123885DA12500 ;IMG3 EU (7.0°E) - 11020 V 7200 T 069B 01 C6825C05FD5DC700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 069C 01 C122F250366C2F00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 069D 01 27904CA5A5A7D700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 069E 01 4618FCB0B03AAF00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 069F 01 428EBDA9392D9200 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A0 01 F61D2EA2C8AA9F00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A1 01 9971A078E3051000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A2 01 BF538FA113116D00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A3 01 D028080CD00F0700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A3 01 D07448EDD0E20700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A4 01 DAD06D00AE187600 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A5 01 D6FFFD6184C91300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A6 01 DF4E07D7E1EB2900 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A7 01 8005CDDECE661B00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A8 01 E2CF78630B05DE00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06A9 01 1F3CEF98BDDAD000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06AA 01 45BF4929CB5AA100 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06AB 01 76FAE104CC992700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06AC 01 131AF25142BCDF00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06AD 01 334E284293193E00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06AE 01 C59BE490A41A6D00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06AF 01 191547A11D534500 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B0 01 3F76A21EBA443C00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B1 01 5057B34A7111DF00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B2 01 17A7D5868E5D6500 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B3 01 9CF9F31197D74900 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B4 01 6C186179163D1300 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B5 01 BB0A1DB27E16E600 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B6 01 502A1B329BEB8C00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B7 01 3026040327ACB200 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B8 01 DE94751062D35400 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06B9 01 E50266791A663A00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06BA 01 75878DB5E6097E00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06BB 01 3AA5C5571DEA6800 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06BC 01 A82264A361B01C00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06BD 01 AF73935FEB51B100 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06BE 01 680E27BCD45A2C00 ;IMG A Europe (7.0°E) - 11020 V 7200 T 06BF 01 1BE03EA95364B600 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06C0 01 424265AB464A5400 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06C1 01 7C777A9034296800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06C2 01 7C777A7043D18A00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06C3 01 1EE30D0192026500 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06C4 01 93BB7B743EE6A800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06C5 01 C4A334C1D814FB00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06CD 01 4ABC1224FAEF5800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06CC 01 2538600B17D90A00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06CE 01 4ABC12242A9AB300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06CF 01 CD2EFBD98E0CC000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D0 01 CD2EFB597E558000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D1 01 364C9FC2F307DC00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D2 01 472AA83AF065E700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D4 01 148B1057D3C7B100 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D5 01 504517CE48271300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D6 01 32A03B66435B8E00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D7 01 3087CCA158E35300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D8 01 48ED360FA371FC00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06D9 01 D3216EC5F0CC0700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06DA 01 80D64B3567990700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06DB 01 A6B539A669827600 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06DC 01 B0E1E98275E6D100 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06DD 01 5EFF1C1EDB73C300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06DE 01 083EC62B3DD2C800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06DF 01 94A3C50960865200 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06E1 01 10213703B7097E00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06E2 01 102137F3E2294500 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06E3 01 B1EB88562DFEE900 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06E5 01 901D56235A9B1600 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06E7 01 A682A0838B1ADE00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06E8 01 1BC827B4DD438800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06EC 01 70AF5CBBE6AE3600 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06F4 01 C785192D37D34100 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06F5 01 FC8D04A0D08C6E00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06F7 01 29F6BFA4F194D700 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06F9 01 907BA1CDE77C3C00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06FC 01 42091073E1CEE300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06FD 01 45E2D915B7761E00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06FE 01 8279A503E28E4400 ;IMG3 EU (7.0°E) - 11020 V 7200 T 06FF 01 4785D1D6183D8000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0700 01 794171490CB43B00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0701 01 00EF34E7134C0000 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0702 01 0EA9D5125F21C800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0703 01 2D4D640338D5E200 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0704 01 A511447B0092BE00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0705 01 5A4006C95B65BE00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0706 01 D53ACCC0A0A22F00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0707 01 E1A2FD0BB4962500 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0709 01 F10378E187746B00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 070A 01 3EC7AAFF76975400 ;IMG3 EU (7.0°E) - 11020 V 7200 T 070B 01 1B2B5A63C8E8E300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 070C 01 388158C2FE107300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 070D 01 CBABBFAA84E6F800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 070E 01 CBABBFFA1A3C1B00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 070F 01 BCBFB1035029C500 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0710 01 71C21288C9ED1C00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0711 01 14FE08A5B89D6C00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0712 01 971394EB7B550A00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0713 01 F4825CD9B20B0B00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0714 01 8FF9B482352D8200 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0715 01 B1A06954A54F3400 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0716 01 6E182D3D3B328F00 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0717 01 54A824DFF1305300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0718 01 B271E187ED4DD300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0719 01 8D21635CF99CE400 ;IMG3 EU (7.0°E) - 11020 V 7200 T 071A 01 8E2208E28B115300 ;IMG3 EU (7.0°E) - 11020 V 7200 T 071B 01 E8B1CF202D4D9100 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0E91 01 C31DADBCBB72D800 ;IMG3 EU (7.0°E) - 11020 V 7200 T 0A26 01 B7D9C24C62827700 ;MDS05 50 & MDS08 50 (7.0°E) - 11055 V 30000 T 1959 01 405E18941A49DA00 ;MDS05,06,07,08,09,10,11,12 50 - 11055 V 30000 T 1600 01 37C82448CE4F2000 ;ONC 50 (7.0°E) - 11087 H 7200 T 16E5 01 C33C139292471600 ;ONC 50 (7.0°E) - 11087 H 7200 T 2140 01 0660C5AFE5251800 ;MDS09,10,11,12 50 (7.0°E) - 11092 V 30000 T 07E8 01 ED5151642DD1D300 ;FA Cup FEED (7.0°E) - 11144 V 7120 T 07E7 01 8EFD3EA3A5F9FD00 ;FA Cup FEED (7.0°E) - 11163 V 7120 T 07ED 01 FCA4C1A310581000 ;FA Cup FEED (7.0°E) - 11163 V 7120 T 0083 01 4DB639DF3C4A2D00 ;ARQ-PL7 CLIPS (7.0°E) - 12555 H 7120 T 0084 01 EDB30CBA1EFB0500 ;ARQ-PL9 CLIPS (7.0°E) - 12555 H 7120 ------------------------------------------------------ T 0001 01 5FDB06AA1364E500 ;Arena Sport 1 (1.9°E) - 12380 H 30000 T 0002 01 CA138BF89FBE0E00 ;Arena Sport 2 (1.9°E) - 12380 H 30000 T 0003 01 52614F2CB05D3801 ;Arena Sport 3 (1.9°E) - 12380 H 30000 T 0004 01 345E9B5B97D5BC01 ;Arena Sport 4 (1.9°E) - 12380 H 30000 ------------------------------------------------------ T 0001 01 5FDB06AA1364E500 ;America TV HD (40.5°W) - 3923 L 7000 T 0002 01 CA138BF89FBE0E00 ;America TV HD (40.5°W) - 3923 L 7000 T 0003 01 52614F2CB05D3801 ;America TV HD (40.5°W) - 3923 L 7000 T 0001 01 5FDB06AA1364E500 ;RCN TV (40.5°W) - 4021 R 3200 T 0001 01 5FDB06AA1364E500 ;RCN Telenovelas (40.5°W) - 4028 R 8000 ------------------------------------------------------ T 0084 01 EDB30CBA1EFB0500 ;ARQ-PL8-10 Clips/Goals (47.5°W) - 3766 H 7200 ------------------------------------------------------ T 000C 01 E326D5546DD03E01 ;Caracol TV Alterno (58.0°W) - 3785 H 5200 T 0001 01 5FDB06AA1364E500 ;Band Internacional (58.0°W) - 4156 V 4300 T 0002 01 CA138BF89FBE0E00 ;Band News (58.0°W) - 4156 V 4300 ------------------------------------------------------ T 000B 01 8913EDA56DE5BC00 ;Univision East (103.0°W) - 4120 H 30000 T 000C 01 E326D5546DD03E00 ;Univision West(103.0°W) - 4120 H 30000 T 000D 01 B7A28B41A38C9500 ;Univision Mountain (103.0°W) - 4120 H 30000 T 0015 01 0517DC6537166F00 ;Unimas EastHD (103.0°W) - 4120 H 30000 T 0016 01 235751D97F32C201 ;Unimas West HD (103.0°W) - 4120 H 30000 T 0017 01 6DC7ECD00BCD2301 ;Unimas Mountain HD (103.0°W) - 4120 H 30000 T 00CF 01 5B70F00700000000 ;GetTV (103.0°W) - 4120 H 30000 ------------------------------------------------------ T 0009 01 5FDB06AA1364E500 ;TeleXitos (105.0°W) - 3940 H 30000 T 0014 01 5FDB06AA1364E500 ;Telemundo Este (105.0°W) - 3940 H 30000 T 0015 01 5FDB06AA1364E500 ;Telemundo Oeste (105.0°W) - 3940 H 30000 T 0016 01 5FDB06AA1364E500 ;Telemundo feeds (105.0°W) - 3940 H 30000 T 0018 01 5FDB06AA1364E500 ;Telemundo feeds (105.0°W) - 3940 H 30000 ############################################# #_______________POWERVU KEYS________________# ############################################# P 0014 00 064B9E34F3A287 ;Coral TV1 PVU4, 4.8E, 12149 P 0014 01 98A4C6FF291C1D ;Coral TV1 PVU4, 4.8E, 12149 P 0017 00 064B9E34F3A287 ;Coral TV2 PVU6, 4.8E, 12149 P 0017 01 98A4C6FF291C1D ;Coral TV2 PVU6, 4.8E, 12149 P 001D 00 064B9E34F3A287 ;Coral TV1 SIS Data -PVU4, 4.8E, 12149 P 001D 01 98A4C6FF291C1D ;Coral TV1 SIS Data -PVU4, 4.8E, 12149 P 0042 00 064B9E34F3A287 ;Ladbrokes 1 PVU 3, 4.8E, 12149 P 0042 01 98A4C6FF291C1D ;Ladbrokes 1 PVU 3, 4.8E, 12149 P 0058 00 064B9E34F3A287 ;Ladbrokes Extra PVU5, 4.8E, 12149 P 0058 01 98A4C6FF291C1D ;Ladbrokes Extra PVU5, 4.8E, 12149 P 005C 00 064B9E34F3A287 ;SIS Spanish PVU2, 4.8E, 12149 P 005C 01 98A4C6FF291C1D ;SIS Spanish PVU2, 4.8E, 12149 P 006C 00 064B9E34F3A287 ;SIS MK Test PVU 8, 4.8E, 12149 P 006C 01 98A4C6FF291C1D ;SIS MK Test PVU 8, 4.8E, 12149 P 0070 00 064B9E34F3A287 ;PPTV2, 4.8E, 12149 P 0070 01 98A4C6FF291C1D ;PPTV2, 4.8E, 12149 P 0071 00 064B9E34F3A287 ;PPTV1-IE, 4.8E, 12149 P 0071 01 98A4C6FF291C1D ;PPTV1-IE, 4.8E, 12149 P 0072 00 064B9E34F3A287 ;PPTV1-UK, 4.8E, 12149 P 0072 01 98A4C6FF291C1D ;PPTV1-UK, 4.8E, 12149 P 0074 00 064B9E34F3A287 ;PPTV3, 4.8E, 12149 P 0074 01 98A4C6FF291C1D ;PPTV3, 4.8E, 12149 P 0078 00 064B9E34F3A287 ;Alphameric Studio and SIS+(PVU1), 4.8E, 12149 P 0078 01 98A4C6FF291C1D ;Alphameric Studio and SIS+(PVU1), 4.8E, 12149 P 0082 00 064B9E34F3A287 ;Alphameric Studio with BTC Audio, 4.8E, 12149 P 0082 01 98A4C6FF291C1D ;Alphameric Studio with BTC Audio, 4.8E, 12149 P 0088 00 064B9E34F3A287 ;SIS+ with BTC Audio, 4.8E, 12149 P 0088 01 98A4C6FF291C1D ;SIS+ with BTC Audio, 4.8E, 12149 P 00C9 00 064B9E34F3A287 ;MK Test, 4.8E, 12149 P 00C9 01 98A4C6FF291C1D ;MK Test, 4.8E, 12149 P 00CB 00 064B9E34F3A287 ;VBI Test, 4.8E, 12149 P 00CB 01 98A4C6FF291C1D ;VBI Test, 4.8E, 12149 P 00FA 00 064B9E34F3A287 ;SIS BarOne Indep, 4.8E, 12149 P 00FA 01 98A4C6FF291C1D ;SIS BarOne Indep, 4.8E, 12149 P 0190 00 064B9E34F3A287 ;SIS+ (PVU1), 4.8E, 12149 P 0190 01 98A4C6FF291C1D ;SIS+ (PVU1), 4.8E, 12149 P 0004 00 064B9E34F3A287 ;VBC TEMP, 4.8E, 12418 P 0004 01 98A4C6FF291C1D ;VBC TEMP, 4.8E, 12418 P 000B 00 064B9E34F3A287 ;SIS Racing, 4.8E, 12418 P 000B 01 98A4C6FF291C1D ;SIS Racing, 4.8E, 12418 P 0021 00 064B9E34F3A287 ;Ladbrokes SIS LES2 CISCO 1, 4.8E, 12418 P 0021 01 98A4C6FF291C1D ;Ladbrokes SIS LES2 CISCO 1, 4.8E, 12418 P 0027 00 064B9E34F3A287 ;Ladbrokes SIS DATA, 4.8E, 12418 P 0027 01 98A4C6FF291C1D ;Ladbrokes SIS DATA, 4.8E, 12418 P 0031 00 064B9E34F3A287 ;Betfred TOTE 2 CISCO 1, 4.8E, 12418 P 0031 01 98A4C6FF291C1D ;Betfred TOTE 2 CISCO 1, 4.8E, 12418 P 0035 00 064B9E34F3A287 ;WILLIAM HILL IP CLEAR-CISCO 6, 4.8E, 12418 P 0035 01 98A4C6FF291C1D ;WILLIAM HILL IP CLEAR-CISCO 6, 4.8E, 12418 P 0036 00 064B9E34F3A287 ;WILLIAM HILL 2, 4.8E, 12418 P 0036 01 98A4C6FF291C1D ;WILLIAM HILL 2, 4.8E, 12418 P 003B 00 064B9E34F3A287 ;WILLIAM HILL SIS DATA-CISCO 6, 4.8E, 12418 P 003B 01 98A4C6FF291C1D ;WILLIAM HILL SIS DATA-CISCO 6, 4.8E, 12418 P 0046 00 064B9E34F3A287 ;SIS VISION BTC AUDIO (Ch11), 4.8E, 12418 P 0046 01 98A4C6FF291C1D ;SIS VISION BTC AUDIO (Ch11), 4.8E, 12418 P 004B 00 064B9E34F3A287 ;ALPHAMERIC UK WITH BTC, 4.8E, 12418 P 004B 01 98A4C6FF291C1D ;ALPHAMERIC UK WITH BTC, 4.8E, 12418 P 004F 00 064B9E34F3A287 ;SIS UK WITH BTC, 4.8E, 12418 P 004F 01 98A4C6FF291C1D ;SIS UK WITH BTC, 4.8E, 12418 P 0057 00 064B9E34F3A287 ;SIS 2 GFX - ENC9, 4.8E, 12418 P 0057 01 98A4C6FF291C1D ;SIS 2 GFX - ENC9, 4.8E, 12418 P 005A 00 064B9E34F3A287 ;SIS Euro Racing, 4.8E, 12418 P 005A 01 98A4C6FF291C1D ;SIS Euro Racing, 4.8E, 12418 P 005B 00 064B9E34F3A287 ;SIS Europe (NO DATA) CISCO 2, 4.8E, 12418 P 005B 01 98A4C6FF291C1D ;SIS Europe (NO DATA) CISCO 2, 4.8E, 12418 P 005F 00 064B9E34F3A287 ;RTVi, 4.8E, 12418 P 005F 01 98A4C6FF291C1D ;RTVi, 4.8E, 12418 P 006F 00 064B9E34F3A287 ;PPTV1, 4.8E, 12418 P 006F 01 98A4C6FF291C1D ;PPTV1, 4.8E, 12418 P 0073 00 064B9E34F3A287 ;Test Channel CISCO 1, 4.8E, 12418 P 0073 01 98A4C6FF291C1D ;Test Channel CISCO 1, 4.8E, 12418 P 007A 00 064B9E34F3A287 ;Alphameric UK CISCO 1, 4.8E, 12418 P 007A 01 98A4C6FF291C1D ;Alphameric UK CISCO 1, 4.8E, 12418 P 0093 00 064B9E34F3A287 ;New Boyles Sports CISCO 1, 4.8E, 12418 P 0093 01 98A4C6FF291C1D ;New Boyles Sports CISCO 1, 4.8E, 12418 P 0098 00 064B9E34F3A287 ;SIS UK with 2DB, 4.8E, 12418 P 0098 01 98A4C6FF291C1D ;SIS UK with 2DB, 4.8E, 12418 P 0099 00 064B9E34F3A287 ;SIS UK with BTC and 2DB, 4.8E, 12418 P 0099 01 98A4C6FF291C1D ;SIS UK with BTC and 2DB, 4.8E, 12418 P 00A0 00 064B9E34F3A287 ;Betfred TOG CISCO 3, 4.8E, 12418 P 00A0 01 98A4C6FF291C1D ;Betfred TOG CISCO 3, 4.8E, 12418 P 00A2 00 064B9E34F3A287 ;Betfred TV (TTV) CISCO 4, 4.8E, 12418 P 00A2 01 98A4C6FF291C1D ;Betfred TV (TTV) CISCO 4, 4.8E, 12418 P 00A3 00 064B9E34F3A287 ;Betfred TV Virtual CISCO 5, 4.8E, 12418 P 00A3 01 98A4C6FF291C1D ;Betfred TV Virtual CISCO 5, 4.8E, 12418 P 00A8 00 064B9E34F3A287 ;Betfred SIS CISCO 1, 4.8E, 12418 P 00A8 01 98A4C6FF291C1D ;Betfred SIS CISCO 1, 4.8E, 12418 P 00A9 00 064B9E34F3A287 ;ALT VC 168, 4.8E, 12418 P 00A9 01 98A4C6FF291C1D ;ALT VC 168, 4.8E, 12418 P 00C8 00 064B9E34F3A287 ;MCUK Test, 4.8E, 12418 P 00C8 01 98A4C6FF291C1D ;MCUK Test, 4.8E, 12418 P 012E 00 064B9E34F3A287 ;SIS UK CISCO 1, 4.8E, 12418 P 012E 01 98A4C6FF291C1D ;SIS UK CISCO 1, 4.8E, 12418 P 00558020 BFC4EF57666AC9 ;EMM Key P 002B8EF7 B7F1C5CBCD1867 ;EMM Key P 00595C6A 9A724EA38306C3 ;EMM Key P 004042D8 D70A0BD206B274 ;EMM Key P 004D61BC 850F8ECDA2D356 ;EMM Key P 004D6864 7EA4FAA3A09FE3 ;EMM Key P 00530ABD ECF4B073C7F8A4 ;EMM Key --------------------------------------------- P 0001 00 96365F795B54FC ;Bootstrap Master, 4.8E, 12303 P 0001 01 01104AD73016C3 ;Bootstrap Master, 4.8E, 12303 P 0005 00 96365F795B54FC ;Software Update, 4.8E, 12303 P 0005 01 01104AD73016C3 ;SoftwareUpdate, 4.8E, 12303 P 01F5 00 96365F795B54FC ;Diva Universal Romania, 4.8E, 12303 P 01F5 01 01104AD73016C3 ;Diva Universal Romania, 4.8E, 12303 P 01F6 00 96365F795B54FC ;Diva Balkans, 4.8E, 12303 P 01F6 01 01104AD73016C3 ;Diva Balkans, 4.8E, 12303 P 0262 00 96365F795B54FC ;Diva Romania, 4.8E, 12303 P 0262 01 01104AD73016C3 ;Diva Romania, 4.8E, 12303 P 026C 00 96365F795B54FC ;Diva Balkans, 4.8E, 12303 P 026C 01 01104AD73016C3 ;Diva Balkans, 4.8E, 12303 P 026D 00 96365F795B54FC ;Universal Hungary, 4.8E, 12303 P 026D 01 01104AD73016C3 ;Universal Hungary, 4.8E, 12303 P 026F 00 96365F795B54FC ;Universal Hungary, 4.8E, 12303 P 026F 01 01104AD73016C3 ;Universal Hungary, 4.8E, 12303 P 0024B5A6 159F14C861263F ;EMM Key --------------------------------------------- P 0064 00 61396394BD36A6 ;Animal Planet Europe, 4.8E, 12322 P 0064 01 541C56ABA95BB2 ;Animal Planet Europe, 4.8E, 12322 P 0065 00 61396394BD36A6 ;Animal Planet Europe, 4.8E, 12322 P 0065 01 541C56ABA95BB2 ;Animal Planet Europe, 4.8E, 12322 P 0066 00 61396394BD36A6 ;Animal Planet Europe, 4.8E, 12322 P 0066 01 541C56ABA95BB2 ;Animal Planet Europe, 4.8E, 12322 P 00C8 00 61396394BD36A6 ;Discovery Central Europe, 4.8E, 12322 P 00C8 01 541C56ABA95BB2 ;Discovery Central Europe, 4.8E, 12322 P 00C9 00 61396394BD36A6 ;Discovery Central Europe, 4.8E, 12322 P 00C9 01 541C56ABA95BB2 ;Discovery Central Europe, 4.8E, 12322 P 0190 00 61396394BD36A6 ;Investigation Discovery Xtra, 4.8E, 12322 P 0190 01 541C56ABA95BB2 ;Investigation Discovery Xtra, 4.8E, 12322 P 0191 00 61396394BD36A6 ;ID Xtra Europe, 4.8E, 12322 P 0191 01 541C56ABA95BB2 ;ID Xtra Europe, 4.8E, 12322 P 01F4 00 61396394BD36A6 ;Discovery Channel Europe, 4.8E, 12322 P 01F4 01 541C56ABA95BB2 ;Discovery Channel Europe, 4.8E, 12322 P 0384 00 61396394BD36A6 ;Discovery Science, 4.8E, 12322 P 0384 01 541C56ABA95BB2 ;Discovery Science, 4.8E, 12322 P 0385 00 61396394BD36A6 ;Science Europe, 4.8E, 12322 P 0385 01 541C56ABA95BB2 ;Science Europe, 4.8E, 12322 P 0386 00 61396394BD36A6 ;Science Europe, 4.8E, 12322 P 0386 01 541C56ABA95BB2 ;Science Europe, 4.8E, 12322 P 03E8 00 61396394BD36A6 ;Discovery World, 4.8E, 12322 P 03E8 01 541C56ABA95BB2 ;Discovery World, 4.8E, 12322 P 03E9 00 61396394BD36A6 ;Discovery World, 4.8E, 12322 P 03E9 01 541C56ABA95BB2 ;Discovery World, 4.8E, 12322 P 03EA 00 61396394BD36A6 ;Discovery World, 4.8E, 12322 P 03EA 01 541C56ABA95BB2 ;Discovery World, 4.8E, 12322 P 044C 00 61396394BD36A6 ;Discovery Channel Turkey HD, 4.8E, 12322 P 044C 01 541C56ABA95BB2 ;Discovery Channel Turkey HD, 4.8E, 12322 P 0514 00 61396394BD36A6 ;Animal Planet Turkey HD, 4.8E, 12322 P 0514 01 541C56ABA95BB2 ;Animal Planet Turkey HD, 4.8E, 12322 P 05DC 00 61396394BD36A6 ;Discovery Science Turkey HD, 4.8E, 12322 P 05DC 01 541C56ABA95BB2 ;Discovery Science Turkey HD, 4.8E, 12322 P 0060DA46 800C6A38D4765C ;EMM Key P 00622ACE 64E07EC76FF416 ;EMM Key P 00622EE5 B80EA84B841E29 ;EMM Key --------------------------------------------- P 0258 00 D0B11BD8B1B43F ;Discovery Turbo Xtra Poland, 4.8E, 12360 P 0258 01 96181B21DC0F47 ;Discovery Turbo Xtra Poland, 4.8E, 12360 P 0320 00 D0B11BD8B1B43F ;TLC Balkans, 4.8E, 12360 P 0320 01 96181B21DC0F47 ;TLC Balkans, 4.8E, 12360 P 03E8 00 D0B11BD8B1B43F ;TLC Hungary, 4.8E, 12360 P 03E8 01 96181B21DC0F47 ;TLC Hungary, 4.8E, 12360 P 04B0 00 D0B11BD8B1B43F ;Discovery Channel Polska, 4.8E, 12360 P 04B0 01 96181B21DC0F47 ;Discovery Channel Polska, 4.8E, 12360 P 0640 00 D0B11BD8B1B43F ;Investigation Discovery Sweden, 4.8E, 12360 P 0640 01 96181B21DC0F47 ;Investigation Discovery Sweden, 4.8E, 12360 P 06A4 00 D0B11BD8B1B43F ;Animal Planet Poland HD, 4.8E, 12360 P 06A4 01 96181B21DC0F47 ;Animal Planet Poland HD, 4.8E, 12360 P 0708 00 D0B11BD8B1B43F ;Discovery Science Poland HD, 4.8E, 12360 P 0708 01 96181B21DC0F47 ;Discovery Science Poland HD, 4.8E, 12360 P 0834 00 D0B11BD8B1B43F ;Investigation Discovery Polska, 4.8E, 12360 P 0834 01 96181B21DC0F47 ;Investigation Discovery Polska, 4.8E, 12360 P 0898 00 D0B11BD8B1B43F ;Discovery Channel Sweden, 4.8E, 12360 P 0898 01 96181B21DC0F47 ;Discovery Channel Sweden, 4.8E, 12360 P 0B54 00 D0B11BD8B1B43F ;TLC Europe, 4.8E, 12360 P 0B54 01 96181B21DC0F47 ;TLC Europe, 4.8E, 12360 P 0B55 00 D0B11BD8B1B43F ;TLC Pan Regional Portuguese, 4.8E, 12360 P 0B55 01 96181B21DC0F47 ;TLC Pan Regional Portuguese, 4.8E, 12360 P 0C1C 00 D0B11BD8B1B43F ;TLC Poland HD, 4.8E, 12360 P 0C1C 01 96181B21DC0F47 ;TLC Poland HD, 4.8E, 12360 P 0053C199 6DAF8122F475F8 ;EMM Key P 005615CE 3413710D15C765 ;EMM Key P 0061CB56 DF1FA983F1986E ;EMM Key P 00623910 D6795F87CC1CBC ;EMM Key --------------------------------------------- P 0001 00 CF8F8EBA3286A4 ;Unire TV 1, 16E, 12654 P 0001 01 8C0993635C22EA ;Unire TV 1, 16E, 12654 P 0002 00 CF8F8EBA3286A4 ;Unire TV 2, 16E, 12654 P 0002 01 8C0993635C22EA ;Unire TV 2, 16E, 12654 P 000A 00 CF8F8EBA3286A4 ;Unire Blu, 16E, 12654 P 000A 01 8C0993635C22EA ;Unire Blu, 16E, 12654 P 004F1DF6 28D3FD510949EB ;EMM Key --------------------------------------------- P 0004 00 0123456789ABCD ;Snai Sat, 16E, 12699 P 0004 01 97D6968EEC34A3 ;Snai Sat, 16E, 12699 P 0007 00 0123456789ABCD ;SNAI TV Virtuali1, 16E, 12699 P 0007 01 97D6968EEC34A3 ;SNAI TV Virtuali1, 16E, 12699 P 002C 00 0123456789ABCD ;SNAI TV Virtuali1, 16E, 12699 P 002C 01 97D6968EEC34A3 ;SNAI TV Virtuali1, 16E, 12699 P 004D 00 0123456789ABCD ;Radio Unico, 16E, 12699 P 004D 01 97D6968EEC34A3 ;Radio Unico, 16E, 12699 P 004E8EC0 C574482270F77E ;EMM Key --------------------------------------------- P 0384 00 D0B11BD8B1B43F ;Discovery Channel Hungary HD, 1W, 12303 P 0384 01 96181B21DC0F47 ;Discovery Channel Hungary HD, 1W, 12303 P 044C 00 D0B11BD8B1B43F ;Discovery Central Europe HD, 1W, 12303 P 044C 01 96181B21DC0F47 ;Discovery Central Europe HD, 1W, 12303 P 044D 00 D0B11BD8B1B43F ;Discovery Central Europe HD, 1W, 12303 P 044D 01 96181B21DC0F47 ;Discovery Central Europe HD, 1W, 12303 P 044E 00 D0B11BD8B1B43F ;Discovery Central Europe HD, 1W, 12303 P 044E 01 96181B21DC0F47 ;Discovery Central Europe HD, 1W, 12303 P 0514 00 D0B11BD8B1B43F ;Discovery Historia Polska, 1W, 12303 P 0514 01 96181B21DC0F47 ;Discovery Historia Polska, 1W, 12303 P 0578 00 D0B11BD8B1B43F ;Discovery Iberia, 1W, 12303 P 0578 01 96181B21DC0F47 ;Discovery Iberia, 1W, 12303 P 0579 00 D0B11BD8B1B43F ;Discovery Spain, 1W, 12303 P 0579 01 96181B21DC0F47 ;Discovery Spain, 1W, 12303 P 057A 00 D0B11BD8B1B43F ;Discovery Portugal, 1W, 12303 P 057A 01 96181B21DC0F47 ;Discovery Portugal, 1W, 12303 P 08FC 00 D0B11BD8B1B43F ;Discovery Turbo Xtra, 1W, 12303 P 08FC 01 96181B21DC0F47 ;Discovery Turbo Xtra, 1W, 12303 P 09C4 00 D0B11BD8B1B43F ;Discovery HD Showcase, 1W, 12303 P 09C4 01 96181B21DC0F47 ;Discovery HD Showcase, 1W, 12303 P 09C5 00 D0B11BD8B1B43F ;Discovery HD Czech/Hun, 1W, 12303 P 09C5 01 96181B21DC0F47 ;Discovery HD Czech/Hun, 1W, 12303 P 09C6 00 D0B11BD8B1B43F ;Discovery HD Russia, 1W, 12303 P 09C6 01 96181B21DC0F47 ;Discovery HD Russia, 1W, 12303 P 09C7 00 D0B11BD8B1B43F ;Discovery HD Czech, 1W, 12303 P 09C7 01 96181B21DC0F47 ;Discovery HD Czech, 1W, 12303 P 09C8 00 D0B11BD8B1B43F ;Discovery HD Turkish, 1W, 12303 P 09C8 01 96181B21DC0F47 ;Discovery HD Turkish, 1W, 12303 P 09C9 00 D0B11BD8B1B43F ;Discovery HD Hungarian, 1W, 12303 P 09C9 01 96181B21DC0F47 ;Discovery HD Hungarian, 1W, 12303 P 09CA 00 D0B11BD8B1B43F ;Discovery HD Showcase Europe, 1W, 12303 P 09CA 01 96181B21DC0F47 ;Discovery HD Showcase Europe, 1W, 12303 P 0A28 00 D0B11BD8B1B43F ;Animal Planet HD, 1W, 12303 P 0A28 01 96181B21DC0F47 ;Animal Planet HD, 1W, 12303 P 0A29 00 D0B11BD8B1B43F ;Animal Planet HD Polish, 1W, 12303 P 0A29 01 96181B21DC0F47 ;Animal Planet HD Polish, 1W, 12303 P 0A2A 00 D0B11BD8B1B43F ;Animal Planet HD Russian, 1W, 12303 P 0A2A 01 96181B21DC0F47 ;Animal Planet HD Russian, 1W, 12303 P 0A2B 00 D0B11BD8B1B43F ;Animal Planet HD Czech, 1W, 12303 P 0A2B 01 96181B21DC0F47 ;Animal Planet HD Czech, 1W, 12303 P 0A2C 00 D0B11BD8B1B43F ;Animal Planet HD Turkish, 1W, 12303 P 0A2C 01 96181B21DC0F47 ;Animal Planet HD Turkish, 1W, 12303 P 0A2D 00 D0B11BD8B1B43F ;Animal Planet HD Hungarian, 1W, 12303 P 0A2D 01 96181B21DC0F47 ;Animal Planet HD Hungarian, 1W, 12303 P 0A2E 00 D0B11BD8B1B43F ;Animal Planet HD, 1W, 12303 P 0A2E 01 96181B21DC0F47 ;Animal Planet HD, 1W, 12303 P 0A8C 00 D0B11BD8B1B43F ;ID Xtra Europe HD, 1W, 12303 P 0A8C 01 96181B21DC0F47 ;ID Xtra Europe HD, 1W, 12303 P 0A8D 00 D0B11BD8B1B43F ;ID Xtra Europe HD, 1W, 12303 P 0A8D 01 96181B21DC0F47 ;ID Xtra Europe HD, 1W, 12303 P 0A8E 00 D0B11BD8B1B43F ;ID Xtra Europe HD, 1W, 12303 P 0A8E 01 96181B21DC0F47 ;ID Xtra Europe HD, 1W, 12303 P 0AF0 00 D0B11BD8B1B43F ;Discovery Poland HD, 1W, 12303 P 0AF0 01 96181B21DC0F47 ;Discovery Poland HD, 1W, 12303 P 0BB8 00 D0B11BD8B1B43F ;Discovery Turbo Xtra HD, 1W, 12303 P 0BB8 01 96181B21DC0F47 ;Discovery Turbo Xtra HD, 1W, 12303 P 0BB9 00 D0B11BD8B1B43F ;Discovery Turbo Xtra, 1W, 12303 P 0BB9 01 96181B21DC0F47 ;Discovery Turbo Xtra, 1W, 12303 P 0BBA 00 D0B11BD8B1B43F ;Discovery Turbo Xtra, 1W, 12303 P 0BBA 01 96181B21DC0F47 ;Discovery Turbo Xtra, 1W, 12303 P 0C80 00 D0B11BD8B1B43F ;Discovery Science Europe HD, 1W, 12303 P 0C80 01 96181B21DC0F47 ;Discovery Science Europe HD, 1W, 12303 P 0C81 00 D0B11BD8B1B43F ;Science Europe HD Hungarian, 1W, 12303 P 0C81 01 96181B21DC0F47 ;Science Europe HD Hungarian, 1W, 12303 P 0C82 00 D0B11BD8B1B43F ;Science Europe HD Turkish, 1W, 12303 P 0C82 01 96181B21DC0F47 ;Science Europe HD Turkish, 1W, 12303 P 0C83 00 D0B11BD8B1B43F ;Science Europe HD Russian, 1W, 12303 P 0C83 01 96181B21DC0F47 ;Science Europe HD Russian, 1W, 12303 P 0C84 00 D0B11BD8B1B43F ;Science Europe HD Czech, 1W, 12303 P 0C84 01 96181B21DC0F47 ;Science Europe HD Czech, 1W, 12303 P 0C85 00 D0B11BD8B1B43F ;Discovery Science Europe HD, 1W, 12303 P 0C85 01 96181B21DC0F47 ;Discovery Science Europe HD, 1W, 12303 P 0053C199 6DAF8122F475F8 ;EMM Key P 005615CE 3413710D15C765 ;EMM Key P 0061CB56 DF1FA983F1986E ;EMM Key P 00623910 D6795F87CC1CBC ;EMM Key --------------------------------------------- P 01FE 00 B07EC58F412BD7 ;The Fight Network, 15W, 12707 H P 01FE 01 A52E79D341F87F ;The Fight Network, 15W, 12707 H P 005D8013 22C3627C45D633 ;EMM Key P 0060A424 6C01ECC7ADC342 ;EMM Key P 0060AF19 723F737A57370E ;EMM Key P 00612C35 A800B5CF633602 ;EMM Key P 00612C62 F5003FD8BE08A2 ;EMM Key --------------------------------------------- P 0002 00 56596630737AE2 ;BYU TV, 15W, 11568 H P 0002 01 5D52F62E082733 ;BYU TV, 15W, 11568 H P 0000 00648E11 D8E6985B24D02C ;EMM Key --------------------------------------------- P 00CC 00 191F1B713B6777 ;Agencia EFE, 30W, 12563 H P 00CC 01 1D1BE37186BEA0 ;Agencia EFE, 30W, 12563 H P 00CD 00 191F1B713B6777 ;EFE Radio, 30W, 12563 H P 00CD 01 1D1BE37186BEA0 ;EFE Radio, 30W, 12563 H P 005B5030 8FF6FBD0AF7218 ;EMM Key ############################################# #______________BISS KEYS RADIO______________# ############################################# F 056F1FFF 00 DEDE00BC00000000 ;SERVICE 1 (42.0°E) F 056F1FFF 01 DEDE00BC00000000 ;SERVICE 1 (42.0°E) F 05711FFF 00 DEDE00BC00000000 ;SERVICE 2 (42.0°E) F 05711FFF 01 DEDE00BC00000000 ;SERVICE 2 (42.0°E) F 05731FFF 00 DEDE00BC00000000 ;SERVICE 3 (42.0°E) F 05731FFF 01 DEDE00BC00000000 ;SERVICE 3 (42.0°E) F 05751FFF 00 DEDE00BC00000000 ;SERVICE 4 (42.0°E) F 05751FFF 01 DEDE00BC00000000 ;SERVICE 4 (42.0°E) F 291A1FFF 00 1000001000000000 ;INTERCOM (42.0°E) F 291A1FFF 01 1000001000000000 ;INTERCOM (42.0°E) F 2A9A1FFF 00 FDFDCFC9CFABBA34 ;INTERCOMM (42.0°E) F 2A9A1FFF 01 FDFDCFC9CFABBA34 ;INTERCOMM (42.0°E) F 2B5D1FFF 00 002123441361188C ;INTERCOM (42.0°E) F 2B5D1FFF 01 002123441361188C ;INTERCOM (42.0°E) F 2BC31FFF 00 002123441361188C ;INTERCOM (42.0°E) F 2BC31FFF 01 002123441361188C ;INTERCOM (42.0°E) F 2BC41FFF 00 002123441361188C ;INTERCOM HT (42.0°E) F 2BC41FFF 01 002123441361188C ;INTERCOM HT (42.0°E) F 2BC51FFF 00 002123441361188C ;INTERCOM BL (42.0°E) F 2BC51FFF 01 002123441361188C ;INTERCOM BL (42.0°E) ############################################# #_________________BISS KEYS_________________# ############################################# F 00011FFF 00 0327022C106251C3 ;Russian Channels (90.0°E) F 00011FFF 01 0327022C106251C3 ;Russian Channels (90.0°E) F 00071FFF 00 C12345006789AB00 ;STS +4h (90.0°E) F 00071FFF 01 C12345006789AB00 ;STS +4h (90.0°E) F 00081FFF 00 ABC1238F45678935 ;Telekanal Che +4h (90.0°E) F 00081FFF 01 ABC1238F45678935 ;Telekanal Che +4h (90.0°E) F 00091FFF 00 D12345006789AB00 ;Domashnij Telekanal +4h (90.0°E) F 00091FFF 01 D12345006789AB00 ;Domashnij Telekanal +4h (90.0°E) F 00091FFF 00 6BA1E5F174BBCAF9 ;Kanal Disney +7h (90.0°E) F 00091FFF 01 6BA1E5F174BBCAF9 ;Kanal Disney +7h (90.0°E) F 000E1FFF 00 C12345006789AB00 ;STS +7h (90.0°E) F 000E1FFF 01 C12345006789AB00 ;STS +7h (90.0°E) F 000F1FFF 00 ABC1238F45678935 ;Telekanal Che +7h (90.0°E) F 000F1FFF 01 ABC1238F45678935 ;Telekanal Che +7h (90.0°E) F 00101FFF 00 D12345006789AB00 ;Domashnij Telekanal +7h (90.0°E) F 00101FFF 01 D12345006789AB00 ;Domashnij Telekanal +7h (90.0°E) F 00111FFF 00 2608396712043811 ;Match! (90.0°E) F 00111FFF 01 2608396712043811 ;Match! (90.0°E) --------------------------------------------- F 000B1FFF 00 02BE5A1ABC67F81B ;BTV National (76.0°E) F 000B1FFF 01 02BE5A1ABC67F81B ;BTV National (76.0°E) --------------------------------------------- F 06401FFF 00 6BA1E5F174BBCAF9 ;Kanal Disney (75.0°E) F 06401FFF 01 6BA1E5F174BBCAF9 ;Kanal Disney (75.0°E) F 06A41FFF 00 EFC065145D2E8611 ;MIR Service (75.0°E) F 06A41FFF 01 EFC065145D2E8611 ;MIR Service (75.0°E) --------------------------------------------- F 00011FFF 00 1234599F8761230B ;Palestine Today (70.5°E) F 00011FFF 01 1234599F8761230B ;Palestine Today (70.5°E) --------------------------------------------- F 00031FFF 00 1111113311111133 ;IRIB TV 3 (62.0°E) F 00031FFF 01 1111113311111133 ;IRIB TV 3 (62.0°E) F 00CB1FFF 00 1010101010101010 ;IRIB feed (62.0°E) F 00CB1FFF 01 1010101010101010 ;IRIB feed (62.0°E) --------------------------------------------- F 00011FFF 00 1234569C7890ABB3 ;Armenia Public TV (60.0°E) F 00011FFF 01 1234569C7890ABB3 ;Armenia Public TV (60.0°E) F 00021FFF 00 1234569C7890ABB3 ;Shoghakat TV (60.0°E) F 00021FFF 01 1234569C7890ABB3 ;Shoghakat TV (60.0°E) F 00031FFF 00 1234569C7890ABB3 ;Armenia TV Satellite (60.0°E) F 00031FFF 01 1234569C7890ABB3 ;Armenia TV Satellite (60.0°E) F 00041FFF 00 1234569C7890ABB3 ;Shant TV (60.0°E) F 00041FFF 01 1234569C7890ABB3 ;Shant TV (60.0°E) F 00051FFF 00 1234569C7890ABB3 ;H2 (60.0°E) F 00051FFF 01 1234569C7890ABB3 ;H2 (60.0°E) F 00061FFF 00 1234569C7890ABB3 ;Kentron (60.0°E) F 00061FFF 01 1234569C7890ABB3 ;Kentron (60.0°E) F 00071FFF 00 1234569C7890ABB3 ;Yerkir Media TV (60.0°E) F 00071FFF 01 1234569C7890ABB3 ;Yerkir Media TV (60.0°E) F 00081FFF 00 1234569C7890ABB3 ;RTR Planeta (60.0°E) F 00081FFF 01 1234569C7890ABB3 ;RTR Planeta (60.0°E) F 01011FFF 00 1234569C7890ABB3 ;Artsakh TV HD (60.0°E) F 01011FFF 01 1234569C7890ABB3 ;Artsakh TV HD (60.0°E) --------------------------------------------- F 00051FFF 00 12340046ABCD0078 ;Varzish Sport HD (57.0°E) F 00051FFF 01 12340046ABCD0078 ;Varzish Sport HD (57.0°E) F 00081FFF 00 12340046ABCD0078 ;Football HD (57.0°E) F 00081FFF 01 12340046ABCD0078 ;Football HD (57.0°E) F 000A1FFF 00 1278008AABCD0078 ;TV Khatlon (57.0°E) F 000A1FFF 01 1278008AABCD0078 ;TV Khatlon (57.0°E) F 000B1FFF 00 12560068ABCD0078 ;TV Badakhshon (57.0°E) F 000B1FFF 01 12560068ABCD0078 ;TV Badakhshon (57.0°E) F 000C1FFF 00 129900ABABCD0078 ;TV Kulob (57.0°E) F 000C1FFF 01 129900ABABCD0078 ;TV Kulob (57.0°E) --------------------------------------------- F 00021FFF 00 62696E39676F7349 ;Kanal Disney +2 (54.9°E) F 00021FFF 01 62696E39676F7349 ;Kanal Disney +2 (54.9°E) F 00011FFF 00 62696E39676F7349 ;Bingo Boom HD 1 (54.9°E) F 00011FFF 01 62696E39676F7349 ;Bingo Boom HD 1 (54.9°E) F 00021FFF 00 62696E39676F7349 ;Bingo Boom HD 2 (54.9°E) F 00021FFF 01 62696E39676F7349 ;Bingo Boom HD 2 (54.9°E) F 00031FFF 00 62696E39676F7349 ;Bingo Boom HD 3 (54.9°E) F 00031FFF 01 62696E39676F7349 ;Bingo Boom HD 3 (54.9°E) F 00041FFF 00 62696E39676F7349 ;Bingo Boom HD 4 (54.9°E) F 00041FFF 01 62696E39676F7349 ;Bingo Boom HD 4 (54.9°E) F 00051FFF 00 62696E39676F7349 ;Bingo Boom HD 5 (54.9°E) F 00051FFF 01 62696E39676F7349 ;Bingo Boom HD 5 (54.9°E) F 00081FFF 00 ABC1238F45678935 ;Telekanal Che 0h (54.9°E) F 00081FFF 01 ABC1238F45678935 ;Telekanal Che 0h (54.9°E) F 00091FFF 00 C12345296789AB9B ;STS +2h (54.9°E) F 00091FFF 01 C12345296789AB9B ;STS +2h (54.9°E) F 000A1FFF 00 D12345396789AB9B ;Domashnij Telekanal +2h (54.9°E) F 000A1FFF 01 D12345396789AB9B ;Domashnij Telekanal +2h (54.9°E) F 000B1FFF 00 ABC1238F45678935 ;Telekanal Che 0h (54.9°E) F 000B1FFF 01 ABC1238F45678935 ;Telekanal Che 0h (54.9°E) F 000C1FFF 00 1234569C789ABCCE ;STS Love 0h (54.9°E) F 000C1FFF 01 1234569C789ABCCE ;STS Love 0h (54.9°E) F 000D1FFF 00 C12345296789AB9B ;STS 0h (54.9°E) F 000D1FFF 01 C12345296789AB9B ;STS 0h (54.9°E) F 000E1FFF 00 D12345396789AB9B ;Domashnij Telekanal 0h (54.9°E) F 000E1FFF 01 D12345396789AB9B ;Domashnij Telekanal 0h (54.9°E) --------------------------------------------- F 00011FFF 00 135790FAAABBCC31 ;Fox Life HD (52.5°E) F 00011FFF 01 135790FAAABBCC31 ;Fox Life HD (52.5°E) F 00051FFF 00 2020ABEBCD0103D1 ;Varzish Sport HD (52.5°E) F 00051FFF 01 2020ABEBCD0103D1 ;Varzish Sport HD (52.5°E) F 06141FFF 00 786AF4D632ABC5A2 ;Tolo TV HD (52.5°E) F 06141FFF 01 786AF4D632ABC5A2 ;Tolo TV HD (52.5°E) F 06151FFF 00 312DBA18741F55E8 ;Lemar TV HD (52.5°E) F 06151FFF 01 312DBA18741F55E8 ;Lemar TV HD (52.5°E) F 064C1FFF 00 ABABAB011234569C ;Maiwand TV (52.5°E) F 064C1FFF 01 ABABAB011234569C ;Maiwand TV (52.5°E) F 064E1FFF 00 ABABAB011234569C ;Tamadon TV (52.5°E) F 064E1FFF 01 ABABAB011234569C ;Tamadon TV (52.5°E) F 06561FFF 00 A9F8E788B1C2D346 ;Arezo TV (52.5°E) F 06561FFF 01 A9F8E788B1C2D346 ;Arezo TV (52.5°E) F 06591FFF 00 ABCDEF671234569C ;Rah-e-Farda TV (52.5°E) F 06591FFF 01 ABCDEF671234569C ;Rah-e-Farda TV (52.5°E) F 065B1FFF 00 1256D73F5D01AC0A ;ATN (52.5°E) F 065B1FFF 01 1256D73F5D01AC0A ;ATN (52.5°E) F 14C91FFF 00 12AA12CEBB12CC99 ;Rotana HD (52.5°E) F 14C91FFF 01 12AA12CEBB12CC99 ;Rotana HD (52.5°E) F 14CA1FFF 00 12AA12CEBB12CC99 ;Rotana Aflam+ HD (52.5°E) F 14CA1FFF 01 12AA12CEBB12CC99 ;Rotana Aflam+ HD (52.5°E) F 14CB1FFF 00 12AA12CEBB12CC99 ;Rotana HD (52.5°E) F 14CB1FFF 01 12AA12CEBB12CC99 ;Rotana HD (52.5°E) --------------------------------------------- F 00021FFF 00 123ABD09456ABD6C ;RTA Afghanistan HD (52.0°E) F 00021FFF 01 123ABD09456ABD6C ;RTA Afghanistan HD (52.0°E) --------------------------------------------- F 000A1FFF 00 407150015A0160BB ;VTV HD (51.5°E) F 000A1FFF 01 407150015A0160BB ;VTV HD (51.5°E) --------------------------------------------- F 00011FFF 00 0327022C106251C3 ;Russian Channels (49.0°E) F 00011FFF 01 0327022C106251C3 ;Russian Channels (49.0°E) F 00021FFF 00 0327022C106251C3 ;Telekanal Rossiya Tyumen (49.0°E) F 00021FFF 00 0327022C106251C3 ;Telekanal Rossiya Tyumen (49.0°E) --------------------------------------------- F 00010025 00 0020050000195600 ;1TV Georgia (46.0°E) F 00010025 01 0020050000195600 ;1TV Georgia (46.0°E) F 00011BB2 00 1234560065432100 ;Az TV 1 (46.0°E) F 00011BB2 01 1234560065432100 ;Az TV 1 (46.0°E) F 00041F9A 00 1212121212121212 ;Ictimai TV (46.0°E) F 00041F9A 01 1212121212121212 ;Ictimai TV (46.0°E) F 000B17CA 00 1001102110017081 ;Idman TV (46.0°E) F 000B17CA 01 1001102110017081 ;Idman TV (46.0°E) F 00151FFF 00 A9E746D68358E5C0 ;Topaz 1 (46.0°E) F 00151FFF 01 A9E746D68358E5C0 ;Topaz 1 (46.0°E) F 08011FFF 00 1313133913131339 ;CBC Sport HD (46.0°E) F 08011FFF 01 1313133913131339 ;CBC Sport HD (46.0°E) --------------------------------------------- F 00011FFF 00 1001102110017081 ;Idman Azerbaycan (45.0°E) F 00011FFF 01 1001102110017081 ;Idman Azerbaycan (45.0°E) F 00021FFF 00 1313133913131339 ;CBC Sport HD (45.0°E) F 00021FFF 01 1313133913131339 ;CBC Sport HD (45.0°E) --------------------------------------------- F 00011FFF 00 1000001000000000 ;TRT 1 (42.0°E) F 00011FFF 01 1000001000000000 ;TRT 1 (42.0°E) F 00051FFF 00 1000001000000000 ;TRT Haber (42.0°E) F 00051FFF 01 1000001000000000 ;TRT Haber (42.0°E) F 00191FFF 00 0100000101201839 ;TRT(feed) Müzik HD (42E) F 00191FFF 01 0100000101201839 ;TRT(feed) Müzik HD (42E) F 001B1FFF 00 D78D7FE375CB4080 ;STD-A (42E) F 001B1FFF 01 D78D7FE375CB4080 ;STD-A (42E) F 001C1FFF 00 D78D7FE375CB4080 ;TRT(feed) Spor HD (42E) F 001C1FFF 01 D78D7FE375CB4080 ;TRT(feed) Spor HD (42E) F 00191FFF 00 1000001000000000 ;TRT Spor (42.0°E) F 00191FFF 01 1000001000000000 ;TRT Spor (42.0°E) F 001C1FFF 00 1000001000000000 ;TRT 3-Spor (42.0°E) F 001C1FFF 01 1000001000000000 ;TRT 3-Spor (42.0°E) F 29041FFF 00 1000001000000000 ;TRT 1 (42.0°E) F 29041FFF 01 1000001000000000 ;TRT 1 (42.0°E) F 29051FFF 00 1000001000000000 ;TRT Haber (42.0°E) F 29051FFF 01 1000001000000000 ;TRT Haber (42.0°E) F 29071FFF 00 1000001000000000 ;TRT 3-Spor (42.0°E) F 29071FFF 01 1000001000000000 ;TRT 3-Spor (42.0°E) F 29681FFF 00 1000001000000000 ;TRT HD (42.0°E) F 29681FFF 01 1000001000000000 ;TRT HD (42.0°E) F 29691FFF 00 1000001000000000 ;TRT 1 HD (42.0°E) F 29691FFF 01 1000001000000000 ;TRT 1 HD (42.0°E) F 296A1FFF 00 1000001000000000 ;TRT Haber HD (42.0°E) F 296A1FFF 01 1000001000000000 ;TRT Haber HD (42.0°E) F 296B1FFF 00 1000001000000000 ;TRT Spor HD (42.0°E) F 296B1FFF 01 1000001000000000 ;TRT Spor HD (42.0°E) F 296D1FFF 00 0100000101201839 ;TRT(feed) World HD (42E) F 296D1FFF 01 0100000101201839 ;TRT(feed) World HD (42E) F 39D11FFF 00 1000001000000000 ;Tivibu Spor HD (42.0°E) F 39D11FFF 01 1000001000000000 ;Tivibu Spor HD (42.0°E) F 39D81FFF 00 1000001000000000 ;Tivibu Spor HD (42.0°E) F 39D81FFF 01 1000001000000000 ;Tivibu Spor HD (42.0°E) F 3E811FFF 00 1000001000000000 ;Tivibu Spor SD (42.0°E) F 3E811FFF 01 1000001000000000 ;Tivibu Spor SD (42.0°E) F C41D1FFF 00 AF1913DB2371BC50 ;TRT Avaz HD (42.0°E) F C41D1FFF 01 AF1913DB2371BC50 ;TRT Avaz HD (42.0°E) --------------------------------------------- F 00011FFF 00 0327022C106251C3 ;Russian Channels (40.0°E) F 00011FFF 01 0327022C106251C3 ;Russian Channels (40.0°E) F 00641FFF 00 0327022C106251C3 ;GTRK Nizhny Novgorod (40.0°E) F 00641FFF 01 0327022C106251C3 ;GTRK Nizhny Novgorod (40.0°E) --------------------------------------------- F 00011FFF 00 1181982A2ABCDEC4 ;The Media Office HD (39.0°E) F 00011FFF 01 1181982A2ABCDEC4 ;The Media Office HD (39.0°E) F 000A1FFF 00 A1B2C316D4E5F8B1 ;ERT 1 (39.0°E) F 000A1FFF 01 A1B2C316D4E5F8B1 ;ERT 1 (39.0°E) F 00141FFF 00 A1B2C316D4E5F8B1 ;ERT 2 (39.0°E) F 00141FFF 01 A1B2C316D4E5F8B1 ;ERT 2 (39.0°E) F 00281FFF 00 A1B2C316D4E5F8B1 ;ERT HD (39.0°E) F 00281FFF 01 A1B2C316D4E5F8B1 ;ERT HD (39.0°E) F 00011FFF 00 E876F04E8BA51141 ;Eurofootball 1 (39.0°E) F 00011FFF 01 E876F04E8BA51141 ;Eurofootball 1 (39.0°E) F 00021FFF 00 E876F04E8BA51141 ;Eurofootball 2 (39.0°E) F 00021FFF 01 E876F04E8BA51141 ;Eurofootball 2 (39.0°E) F 00031FFF 00 E876F04E8BA51141 ;Eurofootball 3 (39.0°E) F 00031FFF 01 E876F04E8BA51141 ;Eurofootball 3 (39.0°E) --------------------------------------------- F 00011FFF 00 BEFA27DF0117BCD4 ;A-Plus Europe (38.0°E) F 00011FFF 01 BEFA27DF0117BCD4 ;A-Plus Europe (38.0°E) F 00011FFF 00 D29965D056F4A1EB ;Dunya TV International (38.0°E) F 00011FFF 01 D29965D056F4A1EB ;Dunya TV International (38.0°E) F 000B1FFF 00 308410C476BEC9FD ;Geo Middle East (38.0°E) F 000B1FFF 01 308410C476BEC9FD ;Geo Middle East (38.0°E) --------------------------------------------- F 00011FFF 00 121233575733129C ;LPC (36.0°E) F 00011FFF 01 121233575733129C ;LPC (36.0°E) F 00011FFF 00 169845F373001285 ;Focus TV (36.0°E) F 00011FFF 01 169845F373001285 ;Focus TV (36.0°E) F 00011FFF 00 1111113311111133 ;Imedi TV (36.0°E) F 00011FFF 01 1111113311111133 ;Imedi TV (36.0°E) F 00021FFF 00 2222226622222266 ;GDS TV (36.0°E) F 00021FFF 01 2222226622222266 ;GDS TV (36.0°E) F 00061FFF 00 1111113311111133 ;Mesame (36.0°E) F 00061FFF 01 1111113311111133 ;Mesame (36.0°E) F 21391FFF 00 002005250019566F ;1TV Georgia (36.0°E) F 21391FFF 01 002005250019566F ;1TV Georgia (36.0°E) F 213A1FFF 00 002005250019566F ;2TV Georgia (36.0°E) F 213A1FFF 01 002005250019566F ;2TV Georgia (36.0°E) --------------------------------------------- F 20121FFF 00 B155454BE520191E ;STS Kids (31.5°E) F 20121FFF 01 B155454BE520191E ;STS Kids (31.5°E) --------------------------------------------- F 00391FFF 00 12AB34F1CD56EF12 ;MBC Masr (26.0°E) F 00391FFF 01 12AB34F1CD56EF12 ;MBC Masr (26.0°E) F 003A1FFF 00 12AB34F1CD56EF12 ;MBC Masr2 (26.0°E) F 003A1FFF 01 12AB34F1CD56EF12 ;MBC Masr2 (26.0°E) F 003B1FFF 00 11122245333444AB ;MBC Test 3 (26.0°E) F 003B1FFF 01 11122245333444AB ;MBC Test 3 (26.0°E) F 00671FFF 00 1111113311111133 ;IRIB TV3 (26.0°E) F 00671FFF 01 1111113311111133 ;IRIB TV3 (26.0°E) F 00751FFF 00 1111113311111133 ;IRIB Varzesh (26.0°E) F 00751FFF 01 1111113311111133 ;IRIB Varzesh (26.0°E) F 01A11FFF 00 1111113311111133 ;IRIB Varzesh (26.0°E) F 01A11FFF 01 1111113311111133 ;IRIB Varzesh (26.0°E) --------------------------------------------- F 00011FFF 00 2020206020202060 ;Gazzoul (21.6°E) F 00011FFF 01 2020206020202060 ;Gazzoul (21.6°E) F 00011FFF 00 12AB34F1CD56EF12 ;MBC Hotbird (21.6°E) F 00011FFF 01 12AB34F1CD56EF12 ;MBC Hotbird (21.6°E) F 00011FFF 00 BAEC27CD0320BCDF ;MBC Feed HD (21.6°E) F 00011FFF 01 BAEC27CD0320BCDF ;MBC Feed HD (21.6°E) F 00011FFF 00 BFDE24FD0715BCD8 ;MBC 1 North Africa (21.6°E) F 00011FFF 01 BFDE24FD0715BCD8 ;MBC 1 North Africa (21.6°E) F 00011FFF 00 12AB34F1CD56EF12 ;MBC Maser 1 (21.6°E) F 00011FFF 01 12AB34F1CD56EF12 ;MBC Maser 1 (21.6°E) F 00021FFF 00 12AB34F1CD56EF12 ;MBC Maser 2 (21.6°E) F 00021FFF 01 12AB34F1CD56EF12 ;MBC Maser 2 (21.6°E) F 07D01FFF 00 FEDCBA94198012AB ;Flowers International HD (21.6°E) F 07D01FFF 01 FEDCBA94198012AB ;Flowers International HD (21.6°E) --------------------------------------------- F 00011FFF 00 1111113311111133 ;ALB-007 RTSH (16.0°E) F 00011FFF 01 1111113311111133 ;ALB-007 RTSH (16.0°E) F 00011FFF 00 124578CF875421FC ;SIC International (16.0°E) F 00011FFF 01 124578CF875421FC ;SIC International (16.0°E) F 00011FFF 00 C48DAF008FDA9700 ;Kanal D Romania (16.0°E) F 00011FFF 01 C48DAF008FDA9700 ;Kanal D Romania (16.0°E) F 00011FFF 00 2B3C1A811A1A7EB2 ;SNAI Quad Race (16.0°E) F 00011FFF 01 2B3C1A811A1A7EB2 ;SNAI Quad Race (16.0°E) F 00011FFF 00 1B5C69E0AA08E99B ;Snai Live (16.0°E) F 00011FFF 01 1B5C69E0AA08E99B ;Snai Live (16.0°E) F 00021FFF 00 1B5C69E0AA08E99B ;Snai Live 2 (16.0°E) F 00021FFF 01 1B5C69E0AA08E99B ;Snai Live 2 (16.0°E) F 00071FFF 00 1111113311111133 ;RTRS (16.0°E) F 00071FFF 01 1111113311111133 ;RTRS (16.0°E) F 000A1FFF 00 458825F27453682F ;National TV (16.0°E) F 000A1FFF 01 458825F27453682F ;National TV (16.0°E) F 00161FFF 00 CDEF12CE5678905E ;N24 Plus (16.0°E) F 00161FFF 01 CDEF12CE5678905E ;N24 Plus (16.0°E) F 00C81FFF 00 C00C7E4A7D49E6AC ;SRTV Feed (16.0°E) F 00C81FFF 01 C00C7E4A7D49E6AC ;SRTV Feed (16.0°E) F 01101FFF 00 E876F04E8BA51141 ;EFB 1 (16.0°E) F 01101FFF 01 E876F04E8BA51141 ;EFB 1 (16.0°E) F 03FA1FFF 00 BC5896AA3DE12341 ;NHL Feed (16.0°E) F 03FA1FFF 01 BC5896AA3DE12341 ;NHL Feed (16.0°E) F 08841FFF 00 355147CD123898E2 ;SS Service 1 (16.0°E) F 08841FFF 01 355147CD123898E2 ;SS Service 1 (16.0°E) F 08A21FFF 00 355147CD241871AD ;SS Service 2 (16.0°E) F 08A21FFF 01 355147CD241871AD ;SS Service 2 (16.0°E) --------------------------------------------- F 00011FFF 00 ACE0018D0220193B ;Vida TV (10.0°E) F 00011FFF 01 ACE0018D0220193B ;Vida TV (10.0°E) F 00011FFF 00 0204757B6840751D ;ORTC (10.0°E) F 00011FFF 01 0204757B6840751D ;ORTC (10.0°E) F 00011FFF 00 AAAAAAFEAAAAABFF ;RTNC (10.0°E) F 00011FFF 01 AAAAAAFEAAAAABFF ;RTNC (10.0°E) F 00021FFF 00 AAAAAAFEAAAAABFF ;RTNC 3 (10.0°E) F 00021FFF 01 AAAAAAFEAAAAABFF ;RTNC 3 (10.0°E) F 00031FFF 00 1010103010101030 ;KaSat Event (10.0°E) F 00031FFF 01 1010103010101030 ;KaSat Event (10.0°E) F 00041FFF 00 486004AC2E838D3E ;AFP 2 HD Europe (10.0°E) F 00041FFF 01 486004AC2E838D3E ;AFP 2 HD Europe (10.0°E) F 00051FFF 00 AAAAAAFEAAAAABFF ;Télé 50 (10.0°E) F 00051FFF 01 AAAAAAFEAAAAABFF ;Télé 50 (10.0°E) F 00061FFF 00 AAAAAAFEAAAAABFF ;Digital Congo TV (10.0°E) F 00061FFF 01 AAAAAAFEAAAAABFF ;Digital Congo TV (10.0°E) --------------------------------------------- F 0DB71FFF 00 E876F04E8BA51141 ;Eurobet 11 (9.0°E) F 0DB71FFF 01 E876F04E8BA51141 ;Eurobet 11 (9.0°E) F 0DB81FFF 00 E876F04E8BA51141 ;Eurobet 12 (9.0°E) F 0DB81FFF 01 E876F04E8BA51141 ;Eurobet 12 (9.0°E) F 0DB91FFF 00 E876F04E8BA51141 ;Eurobet 13 (9.0°E) F 0DB91FFF 01 E876F04E8BA51141 ;Eurobet 13 (9.0°E) F 0DBA1FFF 00 E876F04E8BA51141 ;Eurobet 14 (9.0°E) F 0DBA1FFF 01 E876F04E8BA51141 ;Eurobet 14 (9.0°E) --------------------------------------------- F 00011FFF 00 A1AD2270BBBB9170 ;Simaye Azadi Iran National TV (7.0°E) F 00011FFF 01 A1AD2270BBBB9170 ;Simaye Azadi Iran National TV (7.0°E) F 00081FFF 00 555555FF444444CC ;Corallo Sat (7.0°E) F 00081FFF 01 555555FF444444CC ;Corallo Sat (7.0°E) F 000C1FFF 00 1234569C7890121A ;RTVGE (7.0°E) F 000C1FFF 01 1234569C7890121A ;RTVGE (7.0°E) --------------------------------------------- F 0B671FFF 00 A5EB22B2576F753B ;34 Telekanal (4.8°E) F 0B671FFF 01 A5EB22B2576F753B ;34 Telekanal (4.8°E) F 17ED1FFF 00 1A2B3C814D5E6F1A ;1+1 International (4.8°E) F 17ED1FFF 01 1A2B3C814D5E6F1A ;1+1 International (4.8°E) F 1CDE1FFF 00 1234ACF21234ACF2 ;Inter+ (4.8°E) F 1CDE1FFF 01 1234ACF21234ACF2 ;Inter+ (4.8°E) F 1EF61FFF 00 1234ACF21234ACF2 ;Inter+ (4.8°E) F 1EF61FFF 01 1234ACF21234ACF2 ;Inter+ (4.8°E) --------------------------------------------- F 00641FFF 00 DD5AACE3B667708D ;Alpha TV (3.0°E) F 00641FFF 01 DD5AACE3B667708D ;Alpha TV (3.0°E) F 00651FFF 00 201302352EAD01DC ;2M National (3.0°E) F 00651FFF 01 201302352EAD01DC ;2M National (3.0°E) F 00671FFF 00 201302352EAD03DE ;2M MENA (3.0°E) F 00671FFF 01 201302352EAD03DE ;2M MENA (3.0°E) F 012C1FFF 00 1111113311111133 ;ANT 1 (3.0°E) F 012C1FFF 01 1111113311111133 ;ANT 1 (3.0°E) F 01901FFF 00 1111113311111133 ;Macedonia TV (3.0°E) F 01901FFF 01 1111113311111133 ;Macedonia TV (3.0°E) F 02581FFF 00 1111113311111133 ;Skai (3.0°E) F 02581FFF 01 1111113311111133 ;Skai (3.0°E) F 02BC1FFF 00 1111113311111133 ;Star Channel (3.0°E) F 02BC1FFF 01 1111113311111133 ;Star Channel (3.0°E) F 03201FFF 00 1111113311111133 ;Open Beyond TV (3.0°E) F 03201FFF 01 1111113311111133 ;Open Beyond TV (3.0°E) F 03841FFF 00 1111113311111133 ;Mega Channel (3.0°E) F 03841FFF 01 1111113311111133 ;Mega Channel (3.0°E) --------------------------------------------- F 00011FFF 00 1122336633221166 ;X Sport (4.0°W) F 00011FFF 01 1122336633221166 ;X Sport (4.0°W) F 00091FFF 00 1006102611071229 ;Culture (4.0°W) F 00091FFF 01 1006102611071229 ;Culture (4.0°W) F 000D1FFF 00 1006102611071129 ;Pershiy Nacionalniy (4.0°W) F 000D1FFF 01 1006102611071129 ;Pershiy Nacionalniy (4.0°W) --------------------------------------------- F 00011FFF 00 1100000000000000 ;ENTV (7.0°W) F 00011FFF 01 1100000000000000 ;ENTV (7.0°W) --------------------------------------------- F 00021FFF 00 80DBE03B8424F59D ;TV1 (11.0°W) F 00021FFF 01 80DBE03B8424F59D ;TV1 (11.0°W) --------------------------------------------- F 03851FFF 00 124395EA4683AD76 ;ESPN Caribbean 901 (15.0°W) F 03851FFF 01 124395EA4683AD76 ;ESPN Caribbean 901 (15.0°W) F 03861FFF 00 4456851F3267BC55 ;ESPN Syndication 902 (15.0°W) F 03861FFF 01 4456851F3267BC55 ;ESPN Syndication 902 (15.0°W) --------------------------------------------- F 00011FFF 00 1100000000000000 ;ENTV & ENTV HD (24.5°W) F 00011FFF 01 1100000000000000 ;ENTV & ENTV HD (24.5°W) --------------------------------------------- F 10441FFF 00 D581F94F24112D62 ;BBC One London (27.5°W) F 10441FFF 01 D581F94F24112D62 ;BBC One London (27.5°W) F 107C1FFF 00 D581F94F24112D62 ;BBC One Scotland (27.5°W) F 107C1FFF 01 D581F94F24112D62 ;BBC One Scotland (27.5°W) F 107D1FFF 00 D581F94F24112D62 ;BBC One Northern Ireland (27.5°W) F 107D1FFF 01 D581F94F24112D62 ;BBC One Northern Ireland (27.5°W) F 107E1FFF 00 D581F94F24112D62 ;BBC One Wales (27.5°W) F 107E1FFF 01 D581F94F24112D62 ;BBC One Wales (27.5°W) F 10BF1FFF 00 D581F94F24112D62 ;BBC Two England (27.5°W) F 10BF1FFF 01 D581F94F24112D62 ;BBC Two England (27.5°W) F 11001FFF 00 D581F94F24112D62 ;BBC News (27.5°W) F 11001FFF 01 D581F94F24112D62 ;BBC News (27.5°W) F 11C01FFF 00 D581F94F24112D62 ;BBC Four (27.5°W) F 11C01FFF 01 D581F94F24112D62 ;BBC Four (27.5°W) F 12001FFF 00 D581F94F24112D62 ;CBBC (27.5°W) F 12001FFF 01 D581F94F24112D62 ;CBBC (27.5°W) F 12401FFF 00 D581F94F24112D62 ;CBeebies UK (27.5°W) F 12401FFF 01 D581F94F24112D62 ;CBeebies UK (27.5°W) F 12801FFF 00 D581F94F24112D62 ;BBC Parliament (27.5°W) F 12801FFF 01 D581F94F24112D62 ;BBC Parliament (27.5°W) F 1C001FFF 00 D581F94F24112D62 ;BBC Red Button (27.5°W) F 1C001FFF 01 D581F94F24112D62 ;BBC Red Button (27.5°W) F 44401FFF 00 D581F94F24112D62 ;BBC Two HD (27.5°W) F 44401FFF 01 D581F94F24112D62 ;BBC Two HD (27.5°W) F 44841FFF 00 D581F94F24112D62 ;BBC One HD (27.5°W) F 44841FFF 01 D581F94F24112D62 ;BBC One HD (27.5°W) F 44C81FFF 00 D581F94F24112D62 ;ITV 1 HD (27.5°W) F 44C81FFF 01 D581F94F24112D62 ;ITV 1 HD (27.5°W) F 45001FFF 00 D581F94F24112D62 ;Channel 4 HD (27.5°W) F 45001FFF 01 D581F94F24112D62 ;Channel 4 HD (27.5°W) F 45401FFF 00 D581F94F24112D62 ;Channel 5 HD (27.5°W) F 45401FFF 01 D581F94F24112D62 ;Channel 5 HD (27.5°W) F 46C01FFF 00 D581F94F24112D62 ;CBBC HD (27.5°W) F 46C01FFF 01 D581F94F24112D62 ;CBBC HD (27.5°W) F 4F801FFF 00 D581F94F24112D62 ;Film 4+1 UK (27.5°W) F 4F801FFF 01 D581F94F24112D62 ;Film 4+1 UK (27.5°W) --------------------------------------------- F 00031FFF 00 6F5E4D1A3C2B1A81 ;RTP 3 (30.0°W) F 00031FFF 01 6F5E4D1A3C2B1A81 ;RTP 3 (30.0°W) F 00051FFF 00 1234569C78998798 ;Feeds 2 TSA (30.0°W) F 00051FFF 01 1234569C78998798 ;Feeds 2 TSA (30.0°W) F 0AF01FFF 00 441CC323AA2BB388 ;Feeds HD (30.0°W) F 0AF01FFF 01 441CC323AA2BB388 ;Feeds HD (30.0°W) F 07D01FFF 00 12481670326412A8 ;TVI Internacional (30.0°W) F 07D01FFF 01 12481670326412A8 ;TVI Internacional (30.0°W) F 03E91FFF 00 2E4E9511A3155C14 ;ABERTIS 8001 (30.0°W) F 03E91FFF 01 2E4E9511A3155C14 ;ABERTIS 8001 (30.0°W) F 03EA1FFF 00 DBCEC36CA05806FE ;ABERTIS 8002 (30.0°W) F 03EA1FFF 01 DBCEC36CA05806FE ;ABERTIS 8002 (30.0°W) F 03EB1FFF 00 C53AF0EFB178FC25 ;ABERTIS 8003 (30.0°W) F 03EB1FFF 01 C53AF0EFB178FC25 ;ABERTIS 8003 (30.0°W) F 03EC1FFF 00 759EC4D7AA7F658E ;ABERTIS 8004 (30.0°W) F 03EC1FFF 01 759EC4D7AA7F658E ;ABERTIS 8004 (30.0°W) F 03ED1FFF 00 759EC4D7AA7F658E ;ABERTIS 8005 (30.0°W) F 03ED1FFF 01 759EC4D7AA7F658E ;ABERTIS 8005 (30.0°W) F 03EE1FFF 00 C53AF0EFB178FC25 ;ABERTIS 8006 (30.0°W) F 03EE1FFF 01 C53AF0EFB178FC25 ;ABERTIS 8006 (30.0°W) F 05151FFF 00 254AA110F3CFDB9D ;ABERTIS 301 (30.0°W) F 05151FFF 01 254AA110F3CFDB9D ;ABERTIS 301 (30.0°W) F 05171FFF 00 254AA110F3CFDB9D ;ABERTIS 303 (30.0°W) F 05171FFF 01 254AA110F3CFDB9D ;ABERTIS 303 (30.0°W) F 058C1FFF 00 19103C655FDC9CD7 ;ABERTIS 420 (30.0°W) F 058C1FFF 01 19103C655FDC9CD7 ;ABERTIS 420 (30.0°W) F 058D1FFF 00 19103C655FDC9CD7 ;ABERTIS 421 (30.0°W) F 058D1FFF 01 19103C655FDC9CD7 ;ABERTIS 421 (30.0°W) F 058F1FFF 00 FCF5190A9481A4B9 ;ABERTIS 423 (30.0°W) F 058F1FFF 01 FCF5190A9481A4B9 ;ABERTIS 423 (30.0°W) F 0BD11FFF 00 2A1F90D961EA97E2 ;ABERTIS 2025 (30.0°W) F 0BD11FFF 01 2A1F90D961EA97E2 ;ABERTIS 2025 (30.0°W) F 0BD21FFF 00 2A1F90D961EA97E2 ;ABERTIS 2026 (30.0°W) F 0BD21FFF 01 2A1F90D961EA97E2 ;ABERTIS 2026 (30.0°W) F 0BD31FFF 00 2A1F90D961EA97E2 ;ABERTIS 2027 (30.0°W) F 0BD31FFF 01 2A1F90D961EA97E2 ;ABERTIS 2027 (30.0°W) F 0BD41FFF 00 081C62868233A75C ;ABERTIS 2028 (30.0°W) F 0BD41FFF 01 081C62868233A75C ;ABERTIS 2028 (30.0°W) F 0CC61FFF 00 19103C655FDC9CD7 ;ABERTIS 2270 (30.0°W) F 0CC61FFF 01 19103C655FDC9CD7 ;ABERTIS 2270 (30.0°W) F 0CC71FFF 00 19103C655FDC9CD7 ;ABERTIS 2271 (30.0°W) F 0CC71FFF 01 19103C655FDC9CD7 ;ABERTIS 2271 (30.0°W) F 0CC81FFF 00 19103C655FDC9CD7 ;ABERTIS 2272 (30.0°W) F 0CC81FFF 01 19103C655FDC9CD7 ;ABERTIS 2272 (30.0°W) F 0CC91FFF 00 19103C655FDC9CD7 ;ABERTIS 2273 (30.0°W) F 0CC91FFF 01 19103C655FDC9CD7 ;ABERTIS 2273 (30.0°W) F 0CCA1FFF 00 19103C655FDC9CD7 ;ABERTIS 2274 (30.0°W) F 0CCA1FFF 01 19103C655FDC9CD7 ;ABERTIS 2274 (30.0°W) F 0CE51FFF 00 71FD58C6E72F93A9 ;ABERTIS 2301 (30.0°W) F 0CE51FFF 01 71FD58C6E72F93A9 ;ABERTIS 2301 (30.0°W) F 0CE61FFF 00 71FD58C6E72F93A9 ;ABERTIS 2302 (30.0°W) F 0CE61FFF 01 71FD58C6E72F93A9 ;ABERTIS 2302 (30.0°W) F 0CE71FFF 00 71FD58C6E72F93A9 ;ABERTIS 2303 (30.0°W) F 0CE71FFF 01 71FD58C6E72F93A9 ;ABERTIS 2303 (30.0°W) F 0CE81FFF 00 71FD58C6E72F93A9 ;ABERTIS 2304 (30.0°W) F 0CE81FFF 01 71FD58C6E72F93A9 ;ABERTIS 2304 (30.0°W) F 0CE91FFF 00 71FD58C6E72F93A9 ;ABERTIS 2305 (30.0°W) F 0CE91FFF 01 71FD58C6E72F93A9 ;ABERTIS 2305 (30.0°W) F 0CEA1FFF 00 71FD58C6E72F93A9 ;ABERTIS 2306 (30.0°W) F 0CEA1FFF 01 71FD58C6E72F93A9 ;ABERTIS 2306 (30.0°W) F 0CEB1FFF 00 71FD58C6E72F93A9 ;ABERTIS 2307 (30.0°W) F 0CEB1FFF 01 71FD58C6E72F93A9 ;ABERTIS 2307 (30.0°W) F 125D1FFF 00 71FD58C6E72F93A9 ;ABERTIS 3701 (30.0°W) F 125D1FFF 01 71FD58C6E72F93A9 ;ABERTIS 3701 (30.0°W) F 0DC01FFF 00 EB86E152E78C6DE0 ;ABERTIS 2520 (30.0°W) F 0DC01FFF 01 EB86E152E78C6DE0 ;ABERTIS 2520 (30.0°W) F 0DC11FFF 00 EB86E152E78C6DE0 ;ABERTIS 2521 (30.0°W) F 0DC11FFF 01 EB86E152E78C6DE0 ;ABERTIS 2521 (30.0°W) F 0DC21FFF 00 EB86E152E78C6DE0 ;ABERTIS 2522 (30.0°W) F 0DC21FFF 01 EB86E152E78C6DE0 ;ABERTIS 2522 (30.0°W) F 0DC31FFF 00 EB86E152E78C6DE0 ;ABERTIS 2523 (30.0°W) F 0DC31FFF 01 EB86E152E78C6DE0 ;ABERTIS 2523 (30.0°W) F 0DC41FFF 00 EB86E152E78C6DE0 ;ABERTIS 2524 (30.0°W) F 0DC41FFF 01 EB86E152E78C6DE0 ;ABERTIS 2524 (30.0°W) --------------------------------------------- F 00011FFF 00 3011206117301158 ;TV Brasil (40.5°W) F 00011FFF 01 3011206117301158 ;TV Brasil (40.5°W)
AgoraIO-Community / Unity Virtual Camera PrefabAn open source prefab that makes it easy to live video streaming from a Unity virtual camera into an Agora live video chat or live video streaming channel.
Imamachi-n / Virtual Youtuber APIVirtual Youtuber (VTuber) API: The data collection of 700+ Virtual TouTuber channels
theredrad / UdpsocketA simple UDP server to make a virtual secure channel with the clients
