Curious why my "thanks" message to jamoes was deleted. Not complaining, just want to avoid objectionable content.
|
|
|
as i already posted some month ago exactly this (to have the passphrase in a clipboard) is what i dislike most with the burst wallet. Use a passphrase manager like lastpass with 2FA.
|
|
|
Advance block will run ats if they should be run(sufficient balance, not in sleep status, etc). Run/step into/step over are controls for when it breaks mid-advance.
if you put a large number in balance and hit enter it should stick. (balances are represented as they are internally, so 1 coin is 100000000). send tx dialogue message field is optional and expects any input to be hex.
Thanks, hitting return in the Balance field was the key thing I was missing.
|
|
|
How do I get the debugger to run the ATs? The "Add AT" button seems to work, and I've dragged the assembly from the two examples into the resulting windows. The "Run" etc. buttons are grayed out, and stay that way no matter what I've tried so far. Advance block seems to have no effect, and anything I put in the "Balance" field gets zeroed out when I advance or undo the blockchain. The "Send Tx" dialogs don't seem to do anything. No errors are reported in the terminal I launch the debugger from, but there are some "Vector" messages, which I assume result from the assembly of the machine code. Running on ubuntu trusty, with jdk1.8.0_25
|
|
|
I want to play with the debugger. Where can I get the machine code for the lottery and cf ATs?
|
|
|
I received a transaction from mininghere. Anyone know what they're about? Also, I just noticed the following error in my burst mining logs. Looks like an AT might have broken something? 2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found 2015-01-25 11:21:25 INFO: get timestamp for tx with id -4762078490203704075 found nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching at nxt.at.AT_Controller.validateATs(AT_Controller.java:404) at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682) at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51) at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
|
|
|
Also it should be noted that if we get GCC to do AT then you'll have every fancy tool you could ever want at your disposal. That would be awesome. Is anyone working on that? I was looking at the feasibility of an LLVM backend today, but decided it was probably too awkward because it's claimed here that the binary it produces for a minimal program is 10KB, and the current maximum code size for a burst AT (if I'm reading correctly from MAX_MACHINE_CODE_PAGES in AT_Constants.java) is 2.5K. I am pretty clueless about compiler technology, though, would love to be wrong. Does the machine code size depend on the backend you use?
|
|
|
there is no intention to make ATs "too hard" but we are at the very start of creating tools to make that easier so I hope people can be tolerant while we work on making it more accessible The competition sets a very high bar.
|
|
|
Is there an easy way to run AT code independently of the blockchain?
|
|
|
Although I haven't played with that assembler tool myself perhaps try this instead: Thanks, that worked and produced matching output.
|
|
|
Oh, it's the way I'm invoking it. You have to compile the file first, or it does something inscrutable with stdout. Still not sure it's behaving correctly, though. lap% ~/alien/scala-2.11.2/bin/scalac ATAssembler.scala lap% ~/alien/scala-2.11.2/bin/scala ATAssembler tst.s Unknown: ADD @00000000 @00000001 Unknown: ADD @00000001 @00000002 Unknown: ADD @00000002 @00000003 Unknown: ADD @00000003 @00000004 Unknown: ADD @00000004 @00000005 Unknown: ADD @00000005 @00000006 Unknown: ADD @00000006 @00000007 Unknown: ADD @00000007 @00000008 Unknown: ADD @00000008 @00000009 Unknown: ADD @00000009 @0000000a Unknown: ADD @0000000a @0000000b Unknown: ADD @0000000b @0000000c Unknown: ADD @0000000c @0000000d Unknown: ADD @0000000d @0000000e Unknown: ADD @0000000e @0000000f 01000000000000000000000000010100000001000000000000000102000000020000000000000001030000000300000000000000010400000004000000000000000105000000050000000000000001060000000600000000000000010700000007000000000000000108000000080000000000000001090000000900000000000000010a0000000a00000000000000010b0000000b00000000000000010c0000000c00000000000000010d0000000d00000000000000010e0000000e00000000000000010f0000000f0000000000000028
|
|
|
The code is correct. But if you want to pass it through the assembler to get the final machine code you need to remove the first column ( 00000000*, 0000000d etc )
Oh, I tried it that way too. Same result. % ~/alien/scala-2.11.2/bin/scala ATAssembler.scala tst.s % ls -a . .. ATAssembler.scala tst.s % head -5 tst.s SET @00000000 #0000000000000000 SET @00000001 #0000000000000001 SET @00000002 #0000000000000002 SET @00000003 #0000000000000003 SET @00000004 #0000000000000004 % Thought it might be an interaction with the system-installed 2.9 version, but removing that didn't help.
|
|
|
2.9.2 was released April 2012. might want to try a newer version. I've been using 2.11.2.
Thanks. It runs without error with 2.11.2 (and .4, the latest version) but produces no output, even with garbage files. Here is what I was testing it on recently. Is it correct? 00000000* SET @00000000 #0000000000000000 0000000d SET @00000001 #0000000000000001 0000001a SET @00000002 #0000000000000002 00000027 SET @00000003 #0000000000000003 00000034 SET @00000004 #0000000000000004 00000041 SET @00000005 #0000000000000005 0000004e SET @00000006 #0000000000000006 0000005b SET @00000007 #0000000000000007 00000068 SET @00000008 #0000000000000008 00000075 SET @00000009 #0000000000000009 00000082 SET @0000000a #000000000000000a 0000008f SET @0000000b #000000000000000b 0000009c SET @0000000c #000000000000000c 000000a9 SET @0000000d #000000000000000d 000000b6 SET @0000000e #000000000000000e 000000c3 SET @0000000f #000000000000000f 000000d0 ADD @00000000 @00000001 000000d9 ADD @00000001 @00000002 000000e2 ADD @00000002 @00000003 000000eb ADD @00000003 @00000004 000000f4 ADD @00000004 @00000005 000000fd ADD @00000005 @00000006 00000106 ADD @00000006 @00000007 0000010f ADD @00000007 @00000008 00000118 ADD @00000008 @00000009 00000121 ADD @00000009 @0000000a 0000012a ADD @0000000a @0000000b 00000133 ADD @0000000b @0000000c 0000013c ADD @0000000c @0000000d 00000145 ADD @0000000d @0000000e 0000014e ADD @0000000e @0000000f 00000157 FIN
|
|
|
By the way, are there any tests for the AT stuff? Or for burst generally? Are these kept out of the repository to help keep cloners at bay?
|
|
|
Does it throw that error for any input, or just that example, and what version of scala are you using?
Any input: Same error on a couple of assembly files, and random files. Scala version 2.9.2.
|
|
|
There's a create AT button in the ui in the AT tab under transactions Thanks. When I try to run the assembly code from the lottery example through your assembler, I get the following error: fivebells@hostname:~/alien/burstcoin/at/ATAssembler/src/scala$ scala ATAssembler.scala tst.s /home/fivebells/alien/burstcoin/at/ATAssembler/src/scala/ATAssembler.scala:151: error: Sanity check failed: over 25000 symbols created for pattern match. for (line <- lines) { ^ tst.s contains the contents of the "Assembly Code" section of the ciyam.org lottery page. Tried it with and without the asterix after the initial "00000000". Running on ubuntu 14.04, using the ubuntu "scala" package. Also, scala stinks. :-)
|
|
|
So what's the best way to launch an AT, using the just-released Burst?
|
|
|
Since I started mining a year ago, no form of mining has required as much work and attention as Burst. I am mining on twelve external drives using two machines. Mining restarts on reboot. I log in and check on it a couple of times a day. It's no trouble at all. I guess it was a fair bit of work getting to that point, though.
|
|
|
Thanks! Something to read on the plane.
|
|
|
Oh, I wrote a lot of 6809 assembly when I was a kid. I still want to know what the best tools are.
|
|
|
|