You really need to explain what you're trying to figure out or what you're trying to do, because the question doesn't really make much sense.
I was asking if there is anything lower-level
Lower level?
Sure. There's hex codes. And even lower than that there are binary digits. Below that there is polarity in the magnetic domains on magnetic storage media, or charge states in capacitor-transistor pairs in DRAM.
The blockchain itself is made up of block headers and transaction lists. The block header has no OP_CODES in it at all. Just 80 bytes of hashes, timestamp, version number, difficulty, and nonce.
The transaction list is made up of transactions, which in turn have version, input counts, inputs, output counts, outputs, and a locktime.
Inputs consist of hashes, length, indexes, a sequence number, and a Txin-script (also known as a scriptSig).
Outputs consist of a value, length, and Txout-script (also known as a scriptPubKey).
The two scripts (Txout and Txin) consist of 0 or more OP_CODES and data elements.
All of these values are represented as binary numbers:
- hashes
- versions
- timestamps
- difficulties
- nonces
- counts
- locktimes
- indices
- sequence numbers
- lengths
- values
- OP_CODES
- data elements
and if they have a place with partial clients like Electrum.
Yes. Every piece of client software needs to be able to interpret the blocks and transactions that it receives to be able to determine what it should do with that data.
In addition there are communications protocols implemented for peer nodes to be able to communicate all the necessary information between each other.
Yes I was asking if it was some form of intermediate language and if there was another instruction set maybe with more features. I already know how data is stored..
I was under the impression that Electrum only allowed console scripts without modifying client defaults in source code where they may be filtered by the servers.
