Bağımlılıkların yüklenmesi

Marmara Reposunun Kaynağından İndirilmesi

cd ~
git clone https://github.com/marmarachain/marmara komodo --branch master --single-branch

Swap (Takas) Alanının 4 GB şeklinde ayarlanması (isteğe bağlı)

Swap (Takas) Alanı, işletim sistemi tarafından sabit diskinizde ayrılmış olan bir bölümdür. Eğer kullanılan sistemde 4 GB'lik RAM mevcutsa, RAM boyutunun tamamen dolup, cevap verememesi durumuna karşılık bu alanın ayarlanması tavsiye edilir.

Zcash parametrelerinin çekilmesi ve Derleme
cd komodo

./zcutil/fetch-params.sh

Bu adım tamamlandıktan sonra, komodod ve komodo-cli dosyalarını src klasörünün içerisinde bulunacaktır.
Windows işletim sisteminde derleme için komodod.exe ve komodo-cli.exe dosyalarını src klasörünün içerisinde bulunacaktır.

cd src

Marmara Zincirini Pubkey ile Başlatma*

Zİnciri parametrelerle başlatın, başlatma parametrelerine pubkey adresinizi eklemeyi unutmayınız. Örneğin:

Parametreler ile ilgili detaylı bilgi için burada yer alan linke bakınız.

(*) Zincir kurulumunuzda oluşan wallet.dat dosyası içerisinde bulunan pubkey ile zincirinizi başlatmak önemlidir. Eğer bir cüzdan adresi veya pubkey oluşturmadıysanız bunun için Cüzdan ve privkey başlığına bakınız.

getnewaddress

The getnewaddress method returns a new address for receiving payments.

validateaddress

The validateaddress method returns information about the given address.

convertpassphrase

This command is used to create a privkey from one's own seeds. Make sure that the 12 set of keywords have no special characters in them. For instance using seeds: "can create your own keywords and generate privkey from these whenever needed".

importprivkey

The importprivkey method adds a private key to one's wallet. The command may take several arguments as described in burada yer alan linke bakınız. The simplest form of command for this is given below for demo purposes.

dumpprivkey

The dumpprivkey method reveals the private key corresponding to the indicated address. The command for this is given below for demo purposes.

Backup wallet.dat

Backing up the wallet.dat file is very essential as it holds the assets of one. One method to backup this file is to archive a copy of the file.

setpubkey

It is very important to intiate the Marmara node by setting the pubkey. The chain can be launched with the parameters extended with the pubkey or the setpubkey command could be used after starting the marmara chain to by indicating the pubkey.

getinfo

getinfo command returns important details such as

• the version of MARMARA through "version";

• synchronization status of your node through synced (this parameter's value is true if the parameters "blocks" and "longestchain" are equal );

• difficulty of the chain through "difficulty";

• number of nearest connected nodes to the chain through "connections";

• the pubkey with which you are connected to the chain through "pubkey":
  

marmarainfo

marmarainfo command returns important details such as

• the normal amount in the pubkey through "myPubkeyNormalAmount";

• the activated amount through "myActivatedAmount";

• the details of credit loops made through "Loops";

• the total amount locked in credit loops through "TotalLockedInLoop";

• the number of credit loops closed through "numclosed"; and

• the details of credit loops closed through "closed".
  

marmaralock

marmaralock is used to activate the coins. The entire command is given below and the amount is to be replaced by the amount of coins such as 1000.

To see the activated coins, use marmarainfo command provided earlier and search for the value across the "myActivatedAmount" parameter.

In order to confirm marmaralock transaction, copy the hex returned through the JSON object and validate it through the sendrawtransaction command.

marmaraunlock

marmaraunlock is used deactivate the coins i.e. turn them into normal amount.

The amount parameter in the command is to be replaced by the amount of coins to be deactivated such as 500.

In order to confirm marmaraunlock transaction, copy the hex returned through the JSON object and validate it through the sendrawtransaction command.

sendrawtransaction

sendrawtransction method submits raw transaction (serialized, hex-encoded) to local nodes and the network.

This method has to be executed after the following commands issued:

• marmaralock

• marmaraunlock

• marmarareceive

• marmaraissue
  

If the above command gets successfully executed in the blockchain, it gives out a transaction id in response. One may check if this transaction is verified by searching the respective id in the Marmara Explorer.

Note that the raw transactions are collected in the mempool and a few blocks may be needed to found to see the transaction recorded on the block.

setgenerate 

This method is used to set the node to mining or staking mode. The commands presented below changes the node to staking mode.

Note that "staking": true will not be of use if you have no activated coins (if you have not locked the coins)!

The mode of the node is checked using getgenerate method.

getgenerate

getgenerate command is used to check the mode of the node.

• "staking": false means that staking is off.

• "generate": true means that mining is active.

• "numthreads": 1 refers to the number of cores used for mining. In this case, this parameter was set to one earlier.
  

sendtoaddress

sendtoaddress command is used to send a payment to a given address. The amount is rounded to the nearest 0.00000001. A transaction fee is deducted for the transaction being made from one's Normal Amount.

This command directly sends payment to the specified address and should be used carefully. As, the payment sent through this method cannot be redeemed later.

getpeerinfo   

getpeerinfo command returns detailed information on nearest connected nodes to the chain around your node.

marmaraamountstat

marmaraamountstat command is used to get all the activated, normal and locked in loop amount of the Marmara blockchain irrespective of the owner. If the begin_height and end_height inputs are set to zero(0), it gets the entire set of data from blocks.

listaddressgroupings  

listaddressgroupings is used to list the pairs of wallet addresses and respective normal amounts in them.

getaddressesbyaccount  

getaddressesbyaccount is used to return the list of addresses for the given account.

Creating a Credit Loop

This is the case where two nodes are making a credit loop for the first time. This credit loop may be created for a sale of a good or service in the market. In such case, the holder (the one selling the product/service) should request for a credit from the issuer (the one paying the product/service) by writing down the marmarareceive command as indicated:

• senderpk is the pubkey address of the issuer (the one paying the product/service)

• amount is the payment amount. Please note that this amount should be available in activated fund of the issuer and if not then must be activated thru marmaralock command by th issuer.

• currency is MARMARA

• matures is the time that respective credit expires, 60 blocks an hour times 24 hours a day making 1440 blocks per day.

• {"avalcount":"n"} is the number of avalists i.e. '{"avalcount":"0"}' for protocol 1. Replace n with 0 for Protocol 1.
  

This marmarareceive call generates a hex code. This HEXCODE needs to be verified by the holder by executing the sendrawtransaction command:

Once this command is executed, a transaction id named txid gets generated. This txid along with the receiverpk needs to be communicated to the issuer to complete the credit loop. But, an alternative to this communication would be the use of marmarareceivelist method which could be used to see the receive requests made to the issuer himself/herself

marmarareceivelist

marmarareceivelist command is issued with a pubkey and a maxage parameter. This pubkey is the pubkey address of the issuer connected to the Marmara Chain and the max age by default is 24*60. The response of this command is a list of pair of txid's created by the respective pubkeys.

marmarareceivelist method would be executed by the issuer by using the following command. Replace the pubkey and maxage parameters with related inputs:

This marmarareceive call generates a hex code. This HEXCODE needs to be verified by the holder by executing the sendrawtransaction command.

marmaraissue

marmaraissue command is only used by issuer, the first node to create/issue a credit. By this, a credit is also transferred to the first holder, i.e. the second node. Many of the parameters for a credit loop is decided between the issuer and the first holder. marmaraissue method takes in the following arguments:

• receiverpk is the pubkey of the receiver which is the holder.

• "avalcount":"n" is the number of avalists i.e. '{"avalcount":"0"}' for protocol 1.

• "autosettlement":"true"|"false" AutoSettlement is true due to 100% collateralization in Protocol 1.
  

• "autoinsurance":"true"|"false" Autoinsurance is true due to 100% collateralization in Protocol 1.

• "disputeexpires":"offset" Dispute expiry is set to 0 due to 100 collateralization in Protocol 1.

• "EscrowOn":"true"|"false" EscrowOn is set to false due to 100% collateralization in Protocol 1.

• "BlockageAmount":"amount blockage amount is set to 0 due to 100 collateralization in Protocol 1.

• requesttxid is the txid generated by the holder communicated to the issuer.
  

This marmaraissue command in turn returns a hex code response, and now the issuer has to execute the sendrawtransaction method to get the transaction executed on the blockchain.

This creates a credit loop between the issuer and the holder. The credits locked in a loop can be circulated to buy things during shopping. The issuer and the holder get 3 times of chances of staking on the MCL funds until the maturity of the credit loop.

marmaracreditloop

To display the credit loop between the issuer and the holder, the marmaracreditloop command may be executed:

txid is the baton transfer id of the Marmara Credit Loop.

marmaraholderloops

This command returns the bearer's open and closed loops which can be constrainted by setting the first and last height and the minimum and maximum amount. The method returns all the available data if all the parameters are set to zero.

Transfering a Credit Loop

This is the case where a holder wishes to utilize the coins locked in loop by buying goods/services on the same credit loop created earlier. For such case, when the holder transfers a credit in a loop, that node immediately becomes an endorser. And in such way, the last node in a credit loop is always called the bearer (holder).

In other words, all endorsers are previously holders. One should bear in mind that endorsers lose the 3x staking power when a credit is transferred to a new holder.

The new holder makes a marmarareceive request to the endorser to get the credit for selling the goods/services by the marmarareceive command.

• senderpk is the pubkey address of the endorser (the one buying the product/service)

• batontxid is the baton transaction id of the previously created credit loop

• {"avalcount":"n"} is the number of avalists i.e. {"avalcount":"0"} for protocol 1.
  

This marmarareceive call generates a hex code. This HEXCODE needs to be verified by the new holder by executing the sendrawtransaction command.

Once this sendrawtransaction command is executed, a transaction id named txid gets generated.

This txid along with the receiverpk needs to be communicated to the endorser to complete the credit loop.

But, an alternative to this communication would be the use of marmarareceivelist method which could be used by the endorser to see the receive requests made to himself/herself.

Then, the endorser executes the following marmaratransfer command to get the credits transferred to the new holder:

• receiverpk is the pubkey of the receiver which is the new holder.

• "avalcount":"n" is the number of avalists i.e. '{"avalcount":"0"}' for protocol 1 (n=0).

• requesttxid is the txid generated by the new holder communicated to the endorser.
  

Then, the endorser executes the sendrawtransaction command with the hex code resulting from marmaratransfer command.

In this way, the credit loops can circulate up to 1000th node within the maturity time to buy goods/services.