Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 842. (Read 2761626 times)

hero member
Activity: 808
Merit: 1011
>>>>>>>>>>>>>>> PLEASE VOTE! <<<<<<<<<<<<<<<

Unregistered users are allowed up to 3 votes per hour, whilst registered users are allowed 6 votes per hour!

Please quote me, share on Twitter, Facebook, Reddit... thanks!

Go, go, go! Please share the link with all big websites / admins / social groups you know. 6 votes per hour = ~36 votes per day per NXT'r. 100 NXT'rs = 3600 votes per day. Let's go!
member
Activity: 112
Merit: 10
I'm a nobody here, but I also kindly ask you to calm down.
Don't befoul this thread with your aggressive wording...


Go get bossed around by Graviton & Drexme then... LEAVE ME THE FUCK ALONE!!!    Shocked

I'm beginning to think you're just a troll
member
Activity: 98
Merit: 10
Did not find it within forum, were there any suggestions how to implement anonymous payments (transactions and balances not visible in blockchain)?
sr. member
Activity: 952
Merit: 253
So, when an account leases forging power to a node, what should prevent that node to mis-use that power?

Fear that the leaser will take the power back.

That should not suffice. There could be a business model made on top of this:

1) bad node tells forgers 'u get a bigger slice of the profit when u support me'
2) bad node does only accept transactions with big fees
3) people will pay

You could argue that in that case people will cash out and move on to another crypto-currency or NXT clone. That is true if NXT is young and nobody depends on it as it is the case right now.

However, if NXT is mature and a lot of services depend on it, nobody can cash out that easily and will feed the scheme

Will work only if a lot of power is owned by bad nodes. This is unlikely if Nxt is mature.

Don't other nodes see the block so know what should be in the forged block - if the forging is faulty couldn't the other nodes reject the block and the transactions then get added into the next block.
So a bad node could risk its block being rejected and the work being given to the next forging node to get the fees.
sr. member
Activity: 294
Merit: 250
Anyone got 0.7.5 successfully running on a RasPi?
Mine is crashing everytime because of memory issues.

Mine is running!
legendary
Activity: 2142
Merit: 1010
Newbie
So, when an account leases forging power to a node, what should prevent that node to mis-use that power?

Fear that the leaser will take the power back.

That should not suffice. There could be a business model made on top of this:

1) bad node tells forgers 'u get a bigger slice of the profit when u support me'
2) bad node does only accept transactions with big fees
3) people will pay

You could argue that in that case people will cash out and move on to another crypto-currency or NXT clone. That is true if NXT is young and nobody depends on it as it is the case right now.

However, if NXT is mature and a lot of services depend on it, nobody can cash out that easily and will feed the scheme

Will work only if a lot of power is owned by bad nodes. This is unlikely if Nxt is mature.
sr. member
Activity: 364
Merit: 250
☕ NXT-4BTE-8Y4K-CDS2-6TB82
sr. member
Activity: 312
Merit: 254
Can someone send me some testNXT to 14399955396619943263 thanks Smiley
hero member
Activity: 910
Merit: 1000
Work done on messaging area for http://nxtra.org/nxt-client

Eventually once completed, your client should be distributed as part of NRS package

+1

Something, I really do not understand is why the NRS is consider bad?

Because you don't understand marketing? Wink
sr. member
Activity: 364
Merit: 250
☕ NXT-4BTE-8Y4K-CDS2-6TB82
Work done on messaging area for http://nxtra.org/nxt-client

Eventually once completed, your client should be distributed as part of NRS package

+1

Something, I really do not understand is why the NRS is consider bad?
hero member
Activity: 910
Merit: 1000
Work done on messaging area for http://nxtra.org/nxt-client

Eventually once completed, your client should be distributed as part of NRS package

+1
hero member
Activity: 644
Merit: 500
Work done on messaging area for http://nxtra.org/nxt-client

Not done yet, but done for the day...



Eventually once completed, your client should be distributed as part of NRS package
full member
Activity: 196
Merit: 100
HEY! does this look like I only have 448180k physical ?!?!?!?! That will be something to check up on!

How much RAM you can effectively use depends on the ARM/GPU memory split.

Either run raspi-config or edit /boot/config.txt (gpu_mem) to set the actual memory chunk that the GPU gets.

With the minimum amount of 16MB for the GPU, which makes sense because I never use the Pi with a display, I can effectively use 496948 KiB of RAM.
sr. member
Activity: 364
Merit: 250
☕ NXT-4BTE-8Y4K-CDS2-6TB82
HEY! does this look like I only have 448180k physical ?!?!?!?! That will be something to check up on!

Have a look at here:

http://hubcitylabs.org/unlocking-your-new-raspberry-pis-512mb-of-memory/
sr. member
Activity: 364
Merit: 250
☕ NXT-4BTE-8Y4K-CDS2-6TB82
So, when an account leases forging power to a node, what should prevent that node to mis-use that power?

Fear that the leaser will take the power back.

That should not suffice. There could be a business model made on top of this:

1) bad node tells forgers 'u get a bigger slice of the profit when u support me'
2) bad node does only accept transactions with big fees
3) people will pay

You could argue that in that case people will cash out and move on to another crypto-currency or NXT clone. That is true if NXT is young and nobody depends on it as it is the case right now.

However, if NXT is mature and a lot of services depend on it, nobody can cash out that easily and will feed the scheme
legendary
Activity: 1181
Merit: 1018
Anyone got 0.7.5 successfully running on a RasPi?
Mine is crashing everytime because of memory issues.

I have RasPI running with 0.7.5. Starting with java -Xmx150m.... "Scanning Blockchain" take ~8-9 minutes. Opening acount works also, forging too.

So it should work with model A and B.

Code:
Every 1,0s: echo -n "cpu:\t$"; vcgencmd measure_temp; echo -n "arm:\t$"; vcgencmd measure_clock arm; echo -...  Sun Feb 16 20:21:39 2014

cpu:    $temp=49.8'C
arm:    $frequency(45)=250000000
core:   $frequency(1)=250000000
sdcard: $frequency(47)=250000000
core:   $volt=1.05V
ram:    $volt=1.13V

Resouces:
top - 20:21:40 up 11 min,  1 user,  load average: 0,41, 0,81, 0,60
Tasks:  73 total,   1 running,  72 sleeping,   0 stopped,   0 zombie
%Cpu(s):  3,9 us,  2,9 sy,  9,8 ni, 83,3 id,  0,0 wa,  0,0 hi,  0,0 si,  0,0 st
KiB Mem:    249244 total,   226288 used,    22956 free,     3420 buffers
KiB Swap:   102396 total,        0 used,   102396 free,    21020 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
 2328 pi        39  19  284m 177m 5328 S  10,7 72,9   8:00.08 java
 3066 pi        20   0  4540 1316 1028 R   4,9  0,5   0:00.12 top
    1 root      20   0  2144  712  608 S   0,0  0,3   0:02.42 init

Device:            tps    MB_read/s    MB_wrtn/s    MB_read    MB_wrtn
mmcblk0           0,00         0,00         0,00          0          0
sda               0,00         0,00         0,00          0          0

Last 10 lines of nxt.log:
[2014-02-16 20:10:55.663] "allowedBotHosts" = "127.0.0.1; localhost; 0:0:0:0:0:0:0:1; 192.168.1.20; 192.168.1.113;"
[2014-02-16 20:10:55.716] "blacklistingPeriod" = "300000"
[2014-02-16 20:10:55.719] "communicationLoggingMask" = "0"
[2014-02-16 20:10:55.818] "sendToPeersLimit" = "10"
[2014-02-16 20:10:55.952] DEBUG: Database cache size set to 74240 kB
[2014-02-16 20:11:06.485] Database is at level 15
[2014-02-16 20:11:06.586] Updated database is at level 15
[2014-02-16 20:11:06.853] Scanning blockchain...
[2014-02-16 20:18:48.795] ...Done
[2014-02-16 20:18:48.952] NRS 0.7.5 started successfully.

114M    /home/pi/nxt/nxt_db


Greets,
eb

Hey eb,

got a MASSIVE stacktrace with out of memory an hour ago - raspi

#  Out of Memory Error (os_linux.cpp:2718), pid=2025, tid=2157327472
#
# JRE version: Java(TM) SE Runtime Environment (7.0_40-b43) (build 1.7.0_40-b43)
# Java VM: Java HotSpot(TM) Client VM (24.0-b56 mixed mode linux-arm )
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#

---------------  T H R E A D  ---------------

..
.
.
.


CPU:total 1 (ARMv6), vfp

/proc/cpuinfo:
processor   : 0
model name   : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS   : 2.00
Features   : swp half thumb fastmult vfp edsp java tls
CPU implementer   : 0x41
CPU architecture: 7
CPU variant   : 0x0
CPU part   : 0xb76
CPU revision   : 7

Hardware   : BCM2708
Revision   : 000e
Serial      : 00000000cbe0fa5f


Memory: 4k page, physical 448180k(29320k free), swap 102396k(3032k free)

vm_info: Java HotSpot(TM) Client VM (24.0-b56) for linux-arm-vfp-hflt JRE (1.7.0_40-b43), built on Aug 26 2013 21:44:37 by "java_re" with gcc 4.7.2 20120910 (prerelease)

time: Sun Feb 16 20:55:06 2014
elapsed time: 74742 seconds

pi@raspberrypi ~/nxt $


HEY! does this look like I only have 448180k physical ?!?!?!?! That will be something to check up on!




sr. member
Activity: 308
Merit: 250
Work done on messaging area for http://nxtra.org/nxt-client

Not done yet, but done for the day...

legendary
Activity: 2142
Merit: 1010
Newbie
So, when an account leases forging power to a node, what should prevent that node to mis-use that power?

Fear that the leaser will take the power back.
sr. member
Activity: 336
Merit: 250
AKA jefdiesel
I bought some shares, but now I want to issue my own, only have 899, can someone send 5k so i can mess around?

15265031083387211287

thanks
Jump to: