 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
Hi all,
Can one of you tell me how to backup my wallet in a secure manner ?
Is backing up the wallet folder enough or is backing up the seed enough ?
What's the best practice according to you guys.
I want to store everything offline preferrably on an encrypted memory stick.
What are your recommendations.
Thanks.
The good thing about Qora is that everything is stored on Blockchain, so nothing will ever be lost, and no backup is needed. As vbcs has already mentioned, all you need is the "seed" and the "password" that go along with it, then you will be able to recover all your wallets & accounts on any computer/device you wish.  PS: You can do an experiment yourself, on a 2nd computer, download the qora client, enter your seed, and enter the number of wallets you had created (all your wallets with funds in them), let the client sync... as soon as it finishes syncing, all your funds should be available for your use. Just a note - the password is only used to encrypt the local wallet folder so you dont have to keep it. When restoring from seed you can choose whatever password you like. |
|
|
|
Hi all,
Can one of you tell me how to backup my wallet in a secure manner ?
Is backing up the wallet folder enough or is backing up the seed enough ?
What's the best practice according to you guys.
I want to store everything offline preferrably on an encrypted memory stick.
What are your recommendations.
Thanks.
You only have to keep the master seed somewhere safe. Maybe on a piece of paper. You can get the master seed from there: http://127.0.0.1:9085/wallet/seed |
|
|
|
When you install S7 miner without a firewall, router or something you should at least: 1. Change the UI password 2. Change the ssh password 3. Prohibit access to cgminers API (! this will keep out btcpool.loredo.tv or any other hack) 1. Change the UI password  2. Change the ssh password Connect to S7 using ssh (default pass will be admin or root ): Then type: Now enter you new ssh password 3. Prohibit access to cgminers API from ssh command line type: Modify line (press i to enable modification in vi ): "api-allow" : "W:0/0" to "api-allow" : "W:127.0.0.1" (press ESC then :x to save the changes) Then go back to UI and reboot the miner. |
|
|
|
Great job Ian. I will code the equivalent AT script and GUI for the AT enabled coins ( qora, burst ). I thought the secret could be handled by the exchange software itself ... so this problem could be solved, once the exchange itself is decentral?!
The time issue is bad for day trading ... but i guess it is acceptable considering the benefits of beeing decentral.
Thanks again for your work and efford!
For sure we don't expect it to be a replacement for normal day trading via exchanges, but you could think it more this way: "Shapeshift meets localbitcoin"  |
|
|
|
|
Great job Ian! Congrats! I will try to write a howto tutorial about this in the following days. Many folks here are not aware how to run CIYAM.
|
|
|
|
Hey, you can find the tool mentioned below here: http://expirebox.com/download/4aa42809baca7a440fd502ed861ac14e.htmlYou should put the acct.html file under html/ui and biginteger.js under html/ui/js/util in order to work. If you need any further help just drop me a message. I have a little Burst and Qora. Is there some instructions where I can try ACCT?
Very good question! I also want to know that! For the QORA part there is a GUI in the Wallet, the BURST part has to be done via Transactions->Create AT?! I saw the Press-Release: https://drive.google.com/file/d/0B4vYMJwBtRGLLVQ0OElQRzJackE/viewAnd the general docs: http://ciyam.org/at/at_atomic.html... The below tool has been used that simplifies the entire process.  ... Sooo, it seams the there is a tool for that ... was that released somewhere? I could not find a download. @Vrontis, vcbs, CIYAM ... please help, were can we find that tool?! Or is there a AT example for ACCT somewere, i was looking at http://smartcontr.actor/ but didn't find something. |
|
|
|
There are also some tools and examples available at http://smartcontr.actor/EDIT: For some running examples go to smartcontr.actor -> Examine ATs and add the following Ids to inspect them: - Lottery -> 9192603983782913483 - Crowdfund -> 5080866903808682902 - ACCT -> 13682371899618102560 Also you can check the ATs running on QORA blockchain here: qora.co.in:9090 ATs programmed for BURST, if they are programmed in generic way, could be also used in QORA and vice versa |
|
|
|
Iīve been here, with BURST comunity from the early september 14. I write infrequently because Iīm spanish and Iīve a very bad english, but I read the BURST treath every week. Iīve been mining BURST with some Tb from then and I buy some others BURST. Nowadays I own about 4 million BURST, but I spend much more than the actual value.
Iīve just read Crowetic document and I DONīT agree in some of the questions.
i) I canīt understand the reason to change the reward schema. I, like many others, think that if the BURST provided is unlimited, BURST will have in a not very long term a zero value.
ii)Iīll, also, not change the reward scheme for creating a donation fund, it would be created for the pool administrators and major solo miners, giving the 5% or 10% to that fund for each block found.
iii) and the most important, I DO NOT AGREE that the person who has been blackmailing us over the last six months and is the main cause of the lower price of the BURST, will become the maindev. He has not shown at any time has the capabilities to perform the job.
BUSRT wallet and BURST blockchain has no problems to be cahnged, the maindev must be someone with high capacities in Smart Contracts (AT) that is the great diference of this coin with all the other ones. We need to improve ATīs and generate enthusiasm in people to use this currency, because BURST itīs one of the most disruptive and high-tech coins and those are our most valuable asset.
I give my vote for maindev to vbcs, helped for someone with java and/or NTX skill.
Thatīs my opinon
I agree 100% I spoke with vbcs by PM but unfortunatelly he is not able to fully work on burst. I continue to mining burst on dev v2 pool. In near future i will buy more storage to secure blokchain and "borrow" some space from IT department where i work. Uh, don't you think that vbcs would've been one of the first people I contacted? Since he's on the team? You think I chose the most likely person to cause complete disagreement in the community as a first choice? Get real man seriously. As I said, I will still support and maintain the AT part of burst, but working full time as core dev is something I can not handle atm. But I would gladly help and guide any new devs willing to contribute. The first "easy" task would be to port the new features of nxt ( at least the ones the community wants ) into burst. |
|
|
|
|
Each op code (instruction) consumes a fee, so an infinite loop will need "infinite" amount, but even so there is a hardcoded max number of steps (op codes) each AT program could run on each block.
|
|
|
|
Qora was not the first integrating AT into the core and is not a NXT clone. BURST from the other hand which is a NXT clone ( using different proof, called proof of work ) is the first platform with AT. I am not sure about the latest commits of NXT but for sure it would be very easy to port it from BURST. ( https://github.com/BurstProject/burstcoin/tree/master/src/java/nxt/ ) |
|
|
|
this is what I get when I try to start the client today:  can anyone help me? Can you please try to run the .exe as admin (right click / Run As Admin) and tell me if it worked? did not work, same error java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)
Caused by: java.io.IOError: java.io.IOException: Checksum does not match, data broken
at org.mapdb.StoreWAL.get(StoreWAL.java:322)
at org.mapdb.Caches$HashTable.get(Caches.java:246)
at org.mapdb.EngineWrapper.get(EngineWrapper.java:58)
at org.mapdb.BTreeMap.<init>(BTreeMap.java:541)
at org.mapdb.DB.getTreeMap(DB.java:798)
at org.mapdb.DB$BTreeMapMaker.makeOrGet(DB.java:660)
at database.ATMap.openMap(ATMap.java:89)
at database.ATMap.getMap(ATMap.java:71)
at database.DBMap.<init>(DBMap.java:42)
at database.ATMap.<init>(ATMap.java:51)
at database.DBSet.<init>(DBSet.java:105)
at database.DBSet.reCreateDatabase(DBSet.java:70)
at database.DBSet.getInstance(DBSet.java:50)
at controller.Controller.start(Controller.java:142)
at Start.main(Start.java:37)
... 5 more
Caused by: java.io.IOException: Checksum does not match, data broken
at org.mapdb.Store.deserialize(Store.java:261)
at org.mapdb.StoreDirect.get2(StoreDirect.java:475)
at org.mapdb.StoreWAL.get2(StoreWAL.java:336)
at org.mapdb.StoreWAL.get(StoreWAL.java:320)
... 19 more
I was getting similar errors usually when I was not closing the QORA app properly. Did QORA closed properly the first time you got the error |
|
|
|
Hello
If I initate ACCT, it's possible cancel it? (I try test with 1000 qora)
In which exact step of the process you would like to cancel it? By initiating an ACCT, your funds are locked to this ACCT till the expiration or till the ACCT receive the key. So, one way to cancel it is to not proceed furthermore with this (after the initiation) and wait for the ACCT to expire. The key will not be revealed to nobody and the funds will be returned back to the initiator. thanks for explain, how long expiration time? If we are currently after the expiration block, you will have to send a small tx to the ACCT (with at least 20 qora) to activate it and the funds will be sent back to the creator of the ACCT |
|
|
|
1. What's the development ongoing?
2. What's the next big thing in development?
We are currently preparing the next release, so be patient . vbcs mentioned he was working on a mixer for qora. Is there a possibility it could be included in the next release? I will start working on mixer AT which will provide a "layer of anonymity" after the ACCT takes place between BURST and QORA.
......
That feature will not be in the next release. Also just to note, that this feature will be based on AT, so there is no need for a "new release" when we have it ready. AT offers smart contracts functionality without the need to update the core or anything else. |
|
|
|
Very interesting! I'm trying to wrap my head around this. I see a potential security issue with the "refund timeouts". What if Alice post her tx just before the timeout elapses, resulting in Bob never get the chance to receive his BURST? Could you elaborate on that?
Bob's AT must have have less length (expiration) than Alice's AT.So in case Alice sends the TX with the key to Bob's AT just before the expiration, Bob will have time to send the key to Alice's AT afterwards. Can this be enforced by the AT code or must the trade participants agree on the timeouts? No it cannot be enforced by the AT code itself as the AT on one side is not aware of the other AT. When user A initiates the ACCT then user B can see the timeout and use a proper one when creating the response ACCT. |
|
|
|
|
I will start working on mixer AT which will provide a "layer of anonymity" after the ACCT takes place between BURST and QORA.
Qora with AT inside will be enabled at block 99000, which will be probably in 2-4 days.
|
|
|
|
Hi qora team. What about new wallet with AT entegrated ? We are close ?
Hey, AT is almost done and doing tests these days. It was delayed due to the need of transactions with messages, which QORA did not had, so I had to implement also such functionality. So with the new qora version, you will also be able to send message txs. |
|
|
|
Great then. If you need anything else regarding AT just drop me a message
What's exactly an AT ? AT stands for Automated Transactions and is the Smart Contract technology Burst uses. |
|
|
|
I added the fixes to my "Simple Term Deposit AT" and I tested it on my local testnet - seems working. It blocks the funds for N months When the goal is met, it starts re-paying 1/N each 30 days. ^declare state
^declare interest_decision
^declare target_amount
^declare months
^declare month_in_blocks
SLP $interest_decision
FUN @current_amount get_Current_Balance
BGE $current_amount $target_amount :repayment
FUN @timestamp get_Creation_Timestamp
refund_loop:
FUN A_to_Tx_after_Timestamp $timestamp
FUN @tx_info check_A_Is_Zero
BZR $tx_info :not_funded
FUN @tx_amount get_Amount_for_Tx_in_A
FUN @timestamp get_Timestamp_for_Tx_in_A
FUN B_to_Address_of_Tx_in_A
FUN send_to_Address_in_B $tx_amount
JMP :refund_loop
repayment:
FUN @monthly_payout get_Current_Balance
DIV @monthly_payout $months
FUN B_to_Address_of_Creator
SET @state #0000000000000002
repayment_loop:
SLP $month_in_blocks
FUN @current_amount get_Current_Balance
BGE $monthly_payout $current_amount :end
FUN send_to_Address_in_B $monthly_payout
JMP :repayment_loop
not_funded:
SET @state #0000000000000001
FUN B_to_Address_of_Creator
JMP :end_loop
end:
FUN B_to_Address_of_Creator
SET @state #0000000000000003
end_loop:
FUN send_All_to_Address_in_B
JMP :end_loop
Assembly 250100000035000405000000210500000002000000423501030600000033040306000000352501070000001b07000000653506030800000035070306000000320a03330204080000001a1d00000035000409000000090900000003000000320b03010000000002000000000000002504000000350004050000002109000000050000002b330204090000001a6e00000001000000000100000000000000320b031ab5000000320b03010000000003000000000000003203041ab5000000
Data 0000000000000000DDDDDDDDDDDDDDDDTTTTTTTTTTTTTTTTMMMMMMMMMMMMMMMM302a000000000000
D - Interest decision time in blocks
T - Target amount
M - number of months to run
Example:
For blocking 1,000,000 five years for 5% per year (1000000*1.05^5 = 1276281)
0000000000000000a01700000000000080e101b5137400003c00000000000000302a000000000000
Please, who can, recheck it. Currently I don't have now time to change the crowdfund.html for this script. I have also tested the code in both burst and qora and in both platform works as expected. The only "mistake" I found is the amount. 1000000*1.05^5 = 1276281.5625 but the hex you have ( 80e101b513740000 -> 00007413b501e180 ) equals with 1276279 and not 1276281 Nice work Its because SLP $interest_decision
FUN @current_amount get_Current_Balance
Costs 1,1 BURST so when in the decision time would the balance exactly 1276281 the condition would not met. (If I understand the cost-per-instruction correctly) Thanks for recheck :-) Great then. If you need anything else regarding AT just drop me a message |
|
|
|
I added the fixes to my "Simple Term Deposit AT" and I tested it on my local testnet - seems working. It blocks the funds for N months When the goal is met, it starts re-paying 1/N each 30 days. ^declare state
^declare interest_decision
^declare target_amount
^declare months
^declare month_in_blocks
SLP $interest_decision
FUN @current_amount get_Current_Balance
BGE $current_amount $target_amount :repayment
FUN @timestamp get_Creation_Timestamp
refund_loop:
FUN A_to_Tx_after_Timestamp $timestamp
FUN @tx_info check_A_Is_Zero
BZR $tx_info :not_funded
FUN @tx_amount get_Amount_for_Tx_in_A
FUN @timestamp get_Timestamp_for_Tx_in_A
FUN B_to_Address_of_Tx_in_A
FUN send_to_Address_in_B $tx_amount
JMP :refund_loop
repayment:
FUN @monthly_payout get_Current_Balance
DIV @monthly_payout $months
FUN B_to_Address_of_Creator
SET @state #0000000000000002
repayment_loop:
SLP $month_in_blocks
FUN @current_amount get_Current_Balance
BGE $monthly_payout $current_amount :end
FUN send_to_Address_in_B $monthly_payout
JMP :repayment_loop
not_funded:
SET @state #0000000000000001
FUN B_to_Address_of_Creator
JMP :end_loop
end:
FUN B_to_Address_of_Creator
SET @state #0000000000000003
end_loop:
FUN send_All_to_Address_in_B
JMP :end_loop
Assembly 250100000035000405000000210500000002000000423501030600000033040306000000352501070000001b07000000653506030800000035070306000000320a03330204080000001a1d00000035000409000000090900000003000000320b03010000000002000000000000002504000000350004050000002109000000050000002b330204090000001a6e00000001000000000100000000000000320b031ab5000000320b03010000000003000000000000003203041ab5000000
Data 0000000000000000DDDDDDDDDDDDDDDDTTTTTTTTTTTTTTTTMMMMMMMMMMMMMMMM302a000000000000
D - Interest decision time in blocks
T - Target amount
M - number of months to run
Example:
For blocking 1,000,000 five years for 5% per year (1000000*1.05^5 = 1276281)
0000000000000000a01700000000000080e101b5137400003c00000000000000302a000000000000
Please, who can, recheck it. Currently I don't have now time to change the crowdfund.html for this script. I have also tested the code in both burst and qora and in both platform works as expected. The only "mistake" I found is the amount. 1000000*1.05^5 = 1276281.5625 but the hex you have ( 80e101b513740000 -> 00007413b501e180 ) equals with 1276279 and not 1276281 Nice work |
|
|
|
I modified the crowdfund AT, to expect 1,050,000 BURST after 4 day after creation. 1,000,000 will be provided by the owner ow the script. 5% will be provided by anyone who wants to block the amount for the next year. When the target is not met, BURSTs will be sent back (same as in crowdfund) If the amount will be greater or equal it starts sending BURST to the owner of the script. 1/12 each 30 days (10800 blocks). It can be modified by adding delay before first sending (optional $blocks_before_first_repayment) DISCLAIMER: Its my first script, so take it only as proof of concept. Can someone who understands ATs check it for mistakes? Thanks :-) SET @months #0000000000000012
SET @interest_decision #0000000000001440
SET @month_in_blocks #0000000000010800
SET @target_amount #0105000000000000
FUN @block_height get_Block_Timestamp
SLP $interest_decision
FUN @amount get_Current_Balance
BGE $amount $target_amount :repayment
FUN @timestamp get_Creation_Timestamp
refund_loop:
FUN A_to_Tx_after_Timestamp $timestamp
FUN @tx_info check_A_Is_Zero
BZR $tx_info :end_loop
FUN @tx_amount get_Amount_for_Tx_in_A
FUN @timestamp get_Timestamp_for_Tx_in_A
FUN B_to_Address_of_Tx_in_A
FUN send_to_Address_in_B $tx_amount
JMP :refund_loop
repayment:
FUN @monthly_payout get_Current_Balance
DIV @monthly_payout $months
FUN B_to_Address_of_Creator
(SLP $blocks_before_first_repayment)
repayment_loop:
SLP $month_in_blocks
FUN @current_ammount get_Current_Balance
BGE $monthly_payout $current_ammount :end_loop
FUN set_A1 $current_ammount
FUN send_A_to_Address_in_B
FUN @timestamp get_Last_Block_Timestamp
JMP :repayment_loop
end_loop:
FUN A_to_Tx_after_Timestamp $timestamp
FUN @tx_info check_A_Is_Zero
BZR $tx_info :end_loop
FUN @timestamp get_Timestamp_for_Tx_in_A
FUN B_to_Address_of_Creator
FUN send_All_to_Address_in_B
JMP :end_loop
Very nice! Nice to see someone is trying to write ATs . With a quick review I found these issues. I will check it later ( when I have more free time) for other issues . SET @months #0000000000000012 <- should be converted to hex f.e 12 -> #000000000000000c
SET @interest_decision #0000000000001440 <- should be converted to hex
SET @month_in_blocks #0000000000010800 <- should be converted to hex
SET @target_amount #0105000000000000 <- should be converted to hex
FUN @block_height get_Block_Timestamp
SLP $interest_decision
FUN @amount get_Current_Balance
BGE $amount $target_amount :repayment
FUN @timestamp get_Creation_Timestamp
refund_loop:
FUN A_to_Tx_after_Timestamp $timestamp
FUN @tx_info check_A_Is_Zero
BZR $tx_info :end_loop
FUN @tx_amount get_Amount_for_Tx_in_A
FUN @timestamp get_Timestamp_for_Tx_in_A
FUN B_to_Address_of_Tx_in_A
FUN send_to_Address_in_B $tx_amount
JMP :refund_loop
repayment:
FUN @monthly_payout get_Current_Balance
DIV @monthly_payout $months
FUN B_to_Address_of_Creator
(SLP $blocks_before_first_repayment)
repayment_loop:
SLP $month_in_blocks
FUN @current_ammount get_Current_Balance
BGE $monthly_payout $current_ammount :end_loop
FUN set_A1 $current_ammount // you want to do montly payments. Each payment's amount is monthly_payout? if yes then change $current_ammount -> $montly_payout
FUN send_A_to_Address_in_B
FUN @timestamp get_Last_Block_Timestamp
JMP :repayment_loop
end_loop:
FUN A_to_Tx_after_Timestamp $timestamp
FUN @tx_info check_A_Is_Zero
BZR $tx_info :end_loop
FUN @timestamp get_Timestamp_for_Tx_in_A
FUN B_to_Address_of_Creator
FUN send_All_to_Address_in_B
JMP :end_loop
end_loop:
FUN B_to_Address_of_Creator
FUN send_All_to_Address_in_B
JMP :end_loop
(I dont see a reason looping through the tx's. All you want is to send all the amount to the creator. ) |
|
|
|
|
