Aion The Third Generation Blockchain Network
The Aion network is a multi-tier blockchain network designed to support a future where many blockchains exist to solve unique industry problems...
Home » Semua posting
The Aion network is a multi-tier blockchain network designed to support a future where many blockchains exist to solve unique industry problems and to power the services of the modern world. Aion will become the common protocol used for these blockchains, enabling more efficient and decentralized systems to be built. The Aion protocol enables the development of a federated blockchain network, making it possible to seamlessly integrate dissimilar blockchain systems in a multi-tier hub-and-spoke model, similar to the internet. For more information visit aion.network
Aion? What Is It?
Today, there are hundreds of blockchains. In the coming years, those hundreds will become thousands and—with widespread adoption by mainstream business and government—millions. Blockchains don’t talk to each other at all right now; they are like the PCs of the 1980s.
In the future, blockchains will federate data and value in a hub and spoke model similar to the internet. The future of mainstream blockchain adoption will be achieved by the development of a networked, federated blockchain to integrate these separate spokes. That integrated blockchain network is Aion.
Problematic.
Currently, there is intense interest in blockchain technologies for enterprise and other use cases in both the public and private sectors. In addition to the new mainstream attention being placed on Bitcoin, Ethereum, and the broader ICO market, IBM and other companies have many public and secret blockchain projects; and companies as diverse as Disney and Microsoft have put their name on enterprise blockchain projects. As of July 2017, over 150 companies in various industries are members of the Enterprise Ethereum Alliance (EEA). In addition, over US$400M has been invested in VC (CBInsight) and US$900M through token-generating events since November 2016 (Smith and Crown).
Currently, there is intense interest in blockchain technologies for enterprise and other use cases in both the public and private sectors. In addition to the new mainstream attention being placed on Bitcoin, Ethereum, and the broader ICO market, IBM and other companies have many public and secret blockchain projects; and companies as diverse as Disney and Microsoft have put their name on enterprise blockchain projects. As of July 2017, over 150 companies in various industries are members of the Enterprise Ethereum Alliance (EEA). In addition, over US$400M has been invested in VC (CBInsight) and US$900M through token-generating events since November 2016 (Smith and Crown).
However, the widespread adoption of blockchain technology is constrained by unsolved questions of scalability, privacy, and interoperability. Previous enterprise blockchain innovation has been ineffective at addressing these core concerns. Large amounts of resources have been spent trying to build the next perfect blockchain instead of working to integrate existing systems into an interoperable blockchain network.
Solution
Aion is a third-generation blockchain network that will enable any private or public sector organization to:
• Federate: Send data and value between any Aion-compliant blockchain and Ethereum.
• Scale: Provide fast transaction processing and increased data capacity to all Aion blockchains.
• Spoke: Allow the creation of customized public or private blockchains that maintain interoperability with other blockchains, but allow publishers to choose governance, consensus mechanisms, issuance, and participation. At the root of the Aion network is a purpose-built, public, third-generation blockchain called Aion-1. Designed to connect other blockchains and manage its own robust applications, Aion-1 also provides the economic system that incentivizes interoperability in the ecosystem.
• Federate: Send data and value between any Aion-compliant blockchain and Ethereum.
• Scale: Provide fast transaction processing and increased data capacity to all Aion blockchains.
• Spoke: Allow the creation of customized public or private blockchains that maintain interoperability with other blockchains, but allow publishers to choose governance, consensus mechanisms, issuance, and participation. At the root of the Aion network is a purpose-built, public, third-generation blockchain called Aion-1. Designed to connect other blockchains and manage its own robust applications, Aion-1 also provides the economic system that incentivizes interoperability in the ecosystem.
AION tokens are the fuel used to create new blockchains, monetize inter-chain bridges, and secure the overall network.
Roadmap (Business & Technical)
Aion-1 will be executed in three separate phases, with each phase focusing on different aspects of the technology and assembling the building blocks while progressing towards the finalization of the network (phase 3). The exact deadlines for each phase will be announced in due course.
Phase 1 The focus of the first phase in the Aion release schedule is the interchain communication and bridging infrastructure. With this in mind, phase 1 functionality will include:
- Modified, high-performance EVM
- Functioning bridging and interchain communication
- Modified proof-of-work consensus algorithm
Phase 2 The second phase of the Aion release plan is targeted towards the migration from our modified EVM architecture towards the proposed AVM architecture. Development priorities of this phase include:
- Aion Virtual Machine
- The Aion scripting language
- EVM legacy codebase continued support
Phase 3 The third phase finalizes the envisioned network infrastructure, providing infrastructure for fast, efficient interchain communication and interchain applications. In addition to the interchain functionalities from Phase 1, and the VM implementation from Phase 2, this phase will introduce our representative consensus including the representative consensus algorithm
Token Economics:
- Hard cap:US$45 million (ICO is 50% of total token supply)
- Conversion rate: 1 AION = $1 USD
- Maximum Market Cap: ~US$225 Million if hard cap is reached (to be confirmed)
- ERC20 token: Yes
- Crowdsale date: October 3rd
- Token distribution date: When pre-sale ends
z 1:50 AM Admin Bandung Indonesia
Kembali ke topik kita sesuai judul
"Saya coba jabarkan strateginya.
- Konten : yap, ini sangat penting. bagaimana kita bisa menghasilkan traffic yang bagus buat blog kita, kalau blog kita hanya dipenuhi konten - konten hasil cloningan dari website lain. Naturalitas dalam konten sangat diperlukan, karena search engine juga perlu keunikan dari sebuah konten.
- Konsistensi : Banyak orang yang bisa buat blog, yang jadi pertanyaan berapa banyak sih yang bisa memaintenance blog, bisa dilihatkan banyak blog yang hanya berisi 1 atau 2 postingan. bosan datang. blog pun ditinggalkan, saya punya teknik " One day, One Post", apakah susah, nggak kok, dan kalaupun anda bisa membuat postingan lebih dari satu artikel dalam satu hari. anggap saja itu usaha lebih anda untuk blog anda, bayangkan ketika blog anda menerapkan teknik tersebut dalam 1000 hari, blog anda sudah memiliki 1000 artikel, jika tiap artikel terdapat 3 keyword, kalian bisa hitung jumlah keyword yang ada diblog anda. dan proses untuk Optimasi Search engine semakin mudah.
- Kemampuan : Terus asah kemampuan anda dalam memaintenance blog, baik itu dari segi scripting, maupun penulisan artikel yang dipengaruhi bagaimana anda menjual konten tersebut.
setelah itu dilakukan baru anda mencoba program - program yang mendatangkan pundi - pundi uang dari blog anda :
- Kontes SEO : Ini adalah salah satu cara untuk mendapatkan uang dari blog anda. jadi peserta kontes SEO yang diselengarakan lembaga atau badan usaha. sekalian menguji kekuatan Optimasi SEO diblog anda.
- Program PPC (Pay Per Click) : sampai sa'at ini program ini masih sangat diminati para blogger, dan yang paling terkenal adalah googleadsense, cuma tidak ada salahnya untuk mencoba Program PPC yang lain yang banyak tersebar di internet.
- Affiliasi : Program ini juga terbukti bisa mendatangkan pundi - pundi dolar dari blog kita. program affiliasi seperti amazon, lazada, dll bisa menjadi alternatif buat anda yang ingin mencoba.
Postingan : Blog Monetization Strategies, dapat uang dari blog, kenapa tidak sudah terbukti diblog saya yang terdahulu yang bisa mendatangkan pundi - pundi dolar. yang perlu di ingat adalah Blog itu Investasi jangka Panjang. jadi untuk mendapatkan uang dari blog ada tahapan - tahapan yang harus dilakukan dan butuh waktu
Blog Monetization Strategies, dapat uang dari blog, kenapa tidak
Otodidak learner - rasanya masih terlalu awam saya untuk menjabarkan strategi mendapatkan uang dari blog. dengan konten blog saya yang terindeks...
Otodidak learner - SEO adalah optimasi mesin pencari atau search engine optimization (SEO) adalah sebuah kegiatan untuk mempengaruhi tingkat keterlihatan (visibilitas) sebuah website atau halaman web dihalaman pencarian alami dari sebuah mesin pencari.
"membuat sebuah rancangan proses berupa langkah - langkah terhadap website atau blog anda agar ketika para pengguna internet mencari sesuatu yang berhubungan dengan isi dari website atau blog kita itu, halaman website atau blog anda tersebut ditampilkan dihalaman 1 daftar hasil pencarian alami/tak-berbayar/tanpa-iklan/organik".
Ilustrasi SEO :
Rasanya saya masih terlalu awam untuk menjabarkan apakah itu SEO, cuma disini saya akan coba memberikan ilustrasi tentang SEO, semoga dapat dimengerti, Misalnya anda memiliki sebuah website. disitu dijabarkan mengenai produk - produk yang anda jual. maka dengan melakukan SEO dan Optimasi dengan baik, ketika pengguna internet mencari salah satu dari jenis produk yang anda jual. dengan bantuan mesin pencari seperti google atau pun mesin pencarian lainnya website anda akan berada dihalaman pertama daftar hasil pencarian mesin pencarian tersebut. nah semakin atas posisi website anda dihalaman pertama mesin pencarian. berarti semakin bagus dan bisa dibilang berhasil teknik SEO yang anda terapkan.
Istilah - Istilah Dalam Teknik SEO
Dalam teknik SEO ada istilah - istilah yang biasa digunakan. sebagai pemain baru didalam SEO kita harus lebih dahulu mengenal istilah - istilah tersebut.
- Keyword Planner : salah satu tool milik google yang membantu kita dalam melakukan riset untuk kata kunci dari website atau blog kita
- Exact match types : tipe pencarian kata kunci yang menampilkan kata kunci yang ada pada title tanpa menambahkan kata kunci yang lain, hasil ini adalah yang paling realistis dan sering digunakan para blogger ketika melakukan Keyword Research.
- Montly Searches : adalah akumulasi dari jumlah pencarian sebuah kata kunci dalam hitungan bulan.
Istilah dalam SEO Offpage
- Dofollow : Jenis link yang poinnya akan diteruskan oleh google ke halaman rujukan link tersebut.
- Nofollow : itu antonim dari Dofollow, yaitu google tidak akan meneruskan poin halamannya ke halaman rujukan
- Link Building : Proses membangun link umpan balik yang akan diarahkan ke blog atau website anda.
- Backlink : Adalah link umpan balik dari situs orang lain yang mengarahkan ke blog kita.
- Footprint : Catatan kaki yang anda masukkan ke query pencarian google untuk mencari blog - blog untuk dijadikan tempat menanamkan backlink.
- Keyword : Adalah kata kunci atau kata - kata utama yang ditekankan dalam sebuah halaman website
- Outbound link : link luar yang ada disebuah page ke page lain. dalam mencari backlink sebaiknya anda menanam backlink ditempat yang sedikit outbound link.
- Social Bookmark : situs dimana kita bisa mempublish dan membookmark artikel kita
- Blog Comment : adalah teknik mencari backlink dengan berkomentar pada website lain. terutama website yang memiliki traffic bagus.
- Link Baiting : adalah backlink yang kita dapat secara gratis dari blogger lain yang menanamkan link diblog atau websitenya yang mengarah ke website kita. ataupun bisa didapat dengan cara bertukaran link
Istilah - Istilah dalam SEO Onpage
- Title Tag : adalah barisan kode html yang mengatur tampilan judul halaman dibagian tab browser biasanya kode ini berada di area <head>
- Crawl : adalah proses google merayapi sebuah blog atau website, semakin sering sebuah website dicrawl oleh google berarti semakin bagus blog itu menurut google
- Meta Description : Adalah teks atau kalimat yang mendeskripsikan sebuah website pada mesin pencarian google.
- Relevansi : Tingkat kesamaan sebuah website atau blog yang ditentukan oleh google sebagai penentu peringkat mesin pencari
- Permalink : URL yang ada setelah URL Home page
contoh : http://blogotodidak.blogspot.com/2016/12/apa-itu-seo-pengertian-dan-implementasi.html yang berwarna merah inilah yang disebut permalink dan ini bisa dirubah sesuai kebutuhan. - Authority : Otoritas sebuah blog atau website menurut google. semakin Authority blog atau website kamu. maka semakin bagus rating nya menurut google.
Authority dibagi beberapa :
Page authority : Otoritas untuk halaman website / blog
Domain Authority : Otoritas untuk domain website / blog - Alt Tag : keterangan Alt pada gambar untuk menginformasikan ke google nama sebuah gambar karena google sendiri tidak bisa mengcrawl gambar.
- Long Tail Keyword : kata kunci yang panjang yang berfungsi agar kita lebih mudah rank tinggi digoogle karena kompetitornya sedikit.
Istilah - Istilah dalam Blackhat SEO
- Hidden Text : Teknik menyembunyikan sebuah text yang berisi link. didalam website / blog biasanya warna text tersebut akan disamarkan sesuai dengan warna background website.
- Cloacking : Teknik membuat search engine menampilkan hasil yang berbeda dengan hasil yang diliat pengunjung, teknik ini salah satu yang paling dibenci oleh google dan punishment berupa deindex.
- Penumpukan keyword : Meletakkan kata kunci yang banyak didalam halaman website atau page agar kata kuncinya dapat dicerna oleh mesin pencari. namun terkadang. penempatan keyword terlalu memaksa. sehingga kalimat terlihat sedikit rancu.
- Link spam : menanam backlink disembarang tempat, teknik ini menurut google akan mengurangi kualitas konten dari website atau blog tersebut dari segi kenyamanan.
Demikianlah posting kali ini yang membahas : Apa itu seo? Pengertian dan Istilah - istilah dasar SEO Semoga bermanfaat bagi kita semua.
Apa itu seo? Pengertian dan Istilah - istilah dasar SEO
Otodidak learner - SEO adalah optimasi mesin pencari atau search engine optimization (SEO) adalah sebuah kegiatan untuk mempengaruhi tingkat...
Implementing a Drop Rule
We now have four separate rules that explicitly accept packets based on certain criteria. However, our firewall currently is not blocking anything.
If a packet enters the INPUT chain and doesn't match one of the four rules that we made, it is being passed to our default policy, which is to accept the packet anyways. We need to change this.
There are two different ways that we can do this, with some pretty important differences.
The first way we could do this is to modify the default policy of our INPUT chain. We can do this by typing:
· sudo iptables -P INPUT DROP
This will catch any packets that fall through our INPUT chain, and drop them. This is what we call a default drop policy. One of the implications of this type of a design is that it falls back on dropping packets if the rules are flushed.
This may be more secure, but also can have serious consequences if you don't have another way of accessing your server. With DigitalOcean, you can log in through our web console to get access to your server if this happens. The web console acts as a virtual local connection, so iptables rules will not affect it.
You may like your server to automatically drop all connections in the event that the rules are dumped. This would prevent your server from being left wide open. This also means that you can easily append rules to the bottom of the chain easily while still dropping packets as you'd like.
The alternative approach is to keep the default policy for the chain as accept and add a rule that drops every remaining packet to the bottom of the chain itself.
If you changed the default policy for the INPUT chain above, you can set it back to follow along by typing:
· sudo iptables -P INPUT ACCEPT
Now, you can add a rule to the bottom of the chain that will drop any remaining packets:
· sudo iptables -A INPUT -j DROP
The result under normal operating conditions is exactly the same as a default drop policy. This rule works by matching every remaining packet that reaches it. This prevents a packet from ever dropping all of the way through the chain to reach the default policy.
Basically, this is used to keep the default policy to accept traffic. That way, if there are any problems and the rules are flushed, you will still be able to access the machine over the network. This is a way of implementing a default action without altering the policy that will be applied to an empty chain.
Of course, this also means that any rule that any additional rule that you wish to add to the end of the chain will have to be added before the drop rule. You can do this either by temporarily removing the drop rule:
· sudo iptables -D INPUT -j DROP
· sudo iptables -A INPUT new_rule_here
· sudo iptables -A INPUT -j DROP
Or, you can insert rules that you need at the end of the chain (but prior to the drop) by specifying the line number. To insert a rule at line number 4, you could type:
· sudo iptables -I INPUT 4 new_rule_here
If you are having trouble knowing which line number each rule is, you can tell iptables to number the rules by typing:
· sudo iptables -L --line-numbers
Output:
Chain INPUT (policy DROP)
num target prot opt source destination
1 ACCEPT all -- anywhere anywhere
2 ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
3 ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
4 ACCEPT tcp -- anywhere anywhere tcp dpt:http
Chain FORWARD (policy ACCEPT)
num target prot opt source destination
Chain OUTPUT (policy ACCEPT)
num target prot opt source destination
This can be helpful to make sure you are adding your rule at the appropriate position.
Listing and Deleting Iptables Rules
If you want to learn the details about listing and deleting iptables rules, check out this tutorial: How To List and Delete Iptables Firewall Rules.
Saving your Iptables Configuration
By default, the rules that you add to iptables are ephemeral. This means that when you restart your server, your iptables rules will be gone.
This is actually a feature for some user because it gives them an avenue to get back in if they have accidentally locked themselves out of the server. However, most users will want a way to automatically save the rules you have created and to load them when the server starts.
There are a few ways to do this, but the easiest way is with the iptables-persistent package. You can download this from Ubuntu's default repositories:
· sudo apt-get update
· sudo apt-get install iptables-persistent
During the installation, you will be asked if you would like to save your current rules to be automatically loaded. If you are happy with your current configuration (and you have tested your ability to create independent SSH connections, you can select to save your current rules.
It will also ask you if you want to save the IPv6 rules that you have configured. These are configured through a separate utility called ip6tables which controls the flow of IPv6 packets in almost the same way.
Once the installation is complete, you will have a new service called iptables-persistent that is configured to run at boot. This service will load in your rules and apply them when the server is started.
Saving Updates
If you ever update your firewall and want to preserve the changes, you must save your iptables rules for them to be persistent.
Save your firewall rules with this command:
· sudo invoke-rc.d iptables-persistent save
z
9:53 PM
Admin
Bandung Indonesia
Set Up Firewall Using Iptables On Ubuntu Part 3 (Finished)
Part of the Post Set Up Firewall Using Iptables On Ubuntu Part 2 :
Implementing a Drop Rule
We now have four separate rules...
A INPUT: The -A flag adds a rule at the end of the chain. This part of the IP tables commands explained we wanted to add a new rule, we want that the rules are added to the end of the chain, and the chain we want to operate is the INPUT chain
-m conntrak: IP tables which have a set of core functionality, and also has a set of extensions or modules that have the extra ability to command part of this, we want to have access to the functionality provided by the conntrack module, mpdul It provides access to commands that are used to make decisions based on packet to the previous connection.
--ctstate: This is the command to invoke module available conntrak. the command allows us to match the packet with the previous packet
j ACCEPT: determining a target packet from which, here we say that the IP tables packet matching the previous criteria should be accepted and allowed through
we can see the changes if we make a list of rules
· sudo iptables -L
·
Output:
Chain INPUT (policy ACCEPT)
target port opt source destination
ACCEPT all -- anywhere anywhere ctstate RELATED, ESTABLISHED
Chain FORWARD (policy ACCEPT)
target port opt source destination
Chain OUTPUT (policy ACCEPT)
target port opt source destination
Now that you know the general syntax, let's continue by adding some more cases where we want to accept the connection.
Accept Other Necessary Connections
we have been told to keep open connection IP Tables that are already open and allow new connections associated with the connection,
we wanted to keep the two specific ports open, we want to keep the ssh port open (default port is port 22 if you have to change it in the ssh configuration, then you must change it here), we will also assume that the computer is running a web server on the default port 80
two lines of command that we will use in this rule
· sudo iptables -A INPUT -p tcp --dport 22 -j ACCEPT
· sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT
As we have seen, this is very similar to the first, but it might be simpler
-p tcp: This option is suitable packet if the protocol being used is TCP, it is a connection-based protocol that will be used by most applications because it is reliable in communication
-dport: This option is available if -p tcp flag awarded. This provides further requirement of matching the destination port for the packet that matches, the first rule is suitable for TCP packet addressed to port 22 while the second rule matches TCP traffic heading toward the port 80
No one else accepts the rules that we need to make sure that the server can function properly, because often the computer services communicate between client by sending a packet. they do this by utilizing a network interface called a loopback that direct traffic to themselves instead of to other clients. so if one service wants to communicate with other services listening on port 4555 connections, it can send a packet to port 4555 of the loopback device, we want this to be allowed, because it is very important for correct operation for many programs
rules that we need to add
· sudo iptables -I INPUT 1 -i lo -j ACCEPT
This looks a bit different than our other commands. Let's go over what it is doing:
I INPUT 1: The -I flag Tells IP tables to insert a rule.
this is different from the -A flag adds a rule to the end flag-I took the chain from the rule position where you want to insert the new rule.
in this case we add this rule as the first rule from the INPUT chain. This will meet under the rule, we want the top for fundamental and will not be affected by the following rules.
-i lo: This component of emergency rules that match the interface packet use interface "lo". "Lo" interface is another name for the loopback device, this means that all the interfaces that communicate using a packet (packet generated on our servers) must be accepted
to see our current rules, we must use the -S flag. this is because the -l flag does not include some information, such as the interface associated with the rule, which is an important part of the rule we just added
· sudo iptables -S
·
Output:
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
To be Continue...... z 9:46 PM Admin Bandung Indonesia
Set Up Firewall Using Iptables On Ubuntu Part 2
Part of the Post Set Up Firewall Using Iptables On Ubuntu Part 1
A INPUT: The -A flag adds a rule at the end of the chain. This part of the IP...
