Bitcoin Forum
December 08, 2019, 09:14:10 PM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 [1772] 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 ... 2565 »
  Print  
Author Topic: NXT :: descendant of Bitcoin - Updated Information  (Read 2756318 times)
italovers
Full Member
***
Offline Offline

Activity: 252
Merit: 100


View Profile
February 19, 2014, 04:19:20 PM
 #35421

NXT-E.COM is the best NXT exchange web site.

[NXT]<---> BTC[LTC][Doge][Flappy]

auto deposit/withdraw all coin ~~~~  fast ~~~~  and free !!!
Low Fee: Only as low as 0.15%;
we are promoting our exchange to every famous community in china!


Nxt-e.com has the following features:     

1. Excellent UI. Fast response and great user experience.
2. Strong extension ability. We are able to add many types of coins in the future easily.
3. Low Fee: Only as low as 0.15%;
4. Auto deposit/withdraw.  Deposit/withdraw are automatically processed and got confirmed as quickly as networks. We do not change fee for deposit or withdraw. But networks do.
5. Mobile supported. Full responsive pages get you monitor/trade coins anywhere anytime.
6. Security. We use SSL for the whole site, and have employ Amazon servers to run our web site. Web site, database and password protected wallets are separated on different server to make sure that any server that is hacked will not breach the whole security and steal the coins.


We have 10+ years full-time developers to develop and maintain the web site as well as 2+ years cryptocoins managers to run the web site.

more: https://bitcointalk.org/index.php?topic=453580.0     Grin Smiley


In China BTC38
http://www.nxt-e.com NXT交易所震撼登陆!
http://btc38bbs.gotoip55.com/forum.php?mod=viewthread&tid=1147
(出处: 虚拟币时代)


1575839650
Hero Member
*
Offline Offline

Posts: 1575839650

View Profile Personal Message (Offline)

Ignore
1575839650
Reply with quote  #2

1575839650
Report to moderator
1575839650
Hero Member
*
Offline Offline

Posts: 1575839650

View Profile Personal Message (Offline)

Ignore
1575839650
Reply with quote  #2

1575839650
Report to moderator
1575839650
Hero Member
*
Offline Offline

Posts: 1575839650

View Profile Personal Message (Offline)

Ignore
1575839650
Reply with quote  #2

1575839650
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1575839650
Hero Member
*
Offline Offline

Posts: 1575839650

View Profile Personal Message (Offline)

Ignore
1575839650
Reply with quote  #2

1575839650
Report to moderator
1575839650
Hero Member
*
Offline Offline

Posts: 1575839650

View Profile Personal Message (Offline)

Ignore
1575839650
Reply with quote  #2

1575839650
Report to moderator
italovers
Full Member
***
Offline Offline

Activity: 252
Merit: 100


View Profile
February 19, 2014, 04:20:39 PM
 #35422

Promotion in China
allwelder pretty dry
bitcoinpaul
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000



View Profile
February 19, 2014, 04:21:35 PM
 #35423

you left out: I just hope that TF can be proven to have no attack vector (beyond a 90% one). Grin

An important qualification - and I hope we are going to employ someone with the appropriate ability and reputation to audit this (I have already said I would contribute 5 BTC towards this).


speaking of, are we still searching?

Still searching auditor for

1. Curve+Sign implementaion
2. crypto class
?. what is it ciyam wants again?
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 19, 2014, 04:28:01 PM
 #35424

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.7.6

http://download.nxtcrypto.org/nxt-client-0.7.6.zip

sha256: c219d6a13c870ea7f454fe1e91efe6c6098bed767156aa8921aad0bebe9fe79a


Change log:

Compact the database at every shutdown. This should help reduce the size
of the nxt_db directory after the first run, check the before and after
disk usage.

Prevent duplicate peer listings in the known peers and blacklisted peers
frames.

Prevent a potential duplicate account key attack, of the type described
here:
https://bitcointalk.org/index.php?topic=397183.msg4569817#msg4569817

Added Voting System, not yet enabled.

Some refactoring of the Block and Transaction classes.

Asset exchange bugfixes from the test network and more API requests.

Improved validation of transactions to prevent wrong blacklisting of
peers, and to better enforce transaction validity.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJTBNkwAAoJEFOhyXc7+e2AziEQAJuy9YMEnIfXjaEipm68EklP
XSMWVWBZt1bUsIMZiY7Gu20xV0OxZU68QBIhfFJqX/ZN+grn78pSdQeuOU/gMYdk
YIqZDh2qr7TAVd+On7cMJZ1a41V8av9Xqk/Uy1ydj3A+ZXb3jO0aNzb/f/VvlbGb
DWvO1s7KBA1yghdFQvy/0zxD7hYWcjm2rWe/3UvSTv+qhQCsPQDbdNTg+uUFwvof
SgnnW6NiOaKWrMDc0YFAFMbCDt7LjeY5+Ek1lW3Z0ZZtIJuTuMHWYRo7MoMj1aXO
zEIUOAYGxRbZLClBEFxtIwwF+Kfi75xYlK9pcchl7Wo0a9ooPG9EjqJy+H7f6bmk
xW3frfdIKPy5lZx0H05YnuU9ttUPr0snbWWuDtZQ9CeMzOSKyX/lYsiiUQdbNlGr
FrF4+uLIUXGhBULPNX7P88Om6FYNFVAbgtYxqZSLVIj+5ppZZJxo5rk1A+i2is3A
DKioarK9d7Vy2yMB+FGf3Se03cVmJsdPuqRylw66+PGj+48Ei1Uvzru7lbl8Rqag
guNN48NBm0xuXfBuakPfC7aa1+W2lllB3piJCW/hScbdHtEDsaBsDcYoDAC4CcBV
zpE60AgLClhAinwM4VEkZ7ntSTk83ImR3Ii5HRG7Ip0bzp/MdPcGZ4ifzI/VUH01
DeQ2cjfsCSNbOD61QK/W
=MadH
-----END PGP SIGNATURE-----

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 04:31:03 PM
 #35425

News about TaPoS: https://docs.google.com/document/d/1RLcjSXWuU9vBJzzqLEXVACSCdn8zXKTTJRN_LfoCjNY/edit?pli=1

The author suggests a real penalty for accounts not mining within a year or so: they pay a fee.

Somehow, I like that.

Would be great if we could get this guy to help us with Nxt DAC.

I fear he has his own plan with BitShares.

Penalizing people for not forging with their accounts is detrimental.  There are many reasons people don't forge with their accounts.

If you want to drive people away from Nxt, implement this.

Well, if implemented correctly, the client/node of the person can do it automatically, because of TF.

Conceptually, I like the idea because I keeps the system distributed over time.

How an correct implementation would look like is another question. One could also increase the fees for that account. Either, you pay more for a transaction because you are not helping to stabilize the system or you stabilize the system yourself.

Don't see what's wrong with that if implemented correctly. It's more like an incentive.
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 19, 2014, 04:34:10 PM
 #35426

I checked this signature, it says "Signature made Sat 15 Feb 2014 12:30:29 AM CST"
but the post is made before that. did I miss something?
Something is wrong in your time or timezone settings. I checked the signature of the post you quoted again, and it is from Fri 14 Feb, same as my original post. All EU and US timezones were still in Friday at that time, the hour and minute match so it is a timezone issue.


lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 04:34:57 PM
 #35427

Come-from-Beyond, how difficult would it be to add a feature to the asset exchange allowing accounts to trust other accounts for a certain asset up to a specific amount?  The system would have to be able to handle shifting debt balances.

Why not trusting the person himself?

If you want to help a person, lend him some money. If he is trustworthy, he will give it back to you.

If you trust someone's account, you are trusting him.  The reason why this should be implemented via code in the AE is so the debt transference is automatic which allows for real-time accounting.

Why not implementing a smart contract for that?

In more tangible words: a specialized decentralized notary as I described it here: https://bitcointalk.org/index.php?topic=458036.msg5211090#msg5211090

That notary handles the low-level transaction stuff whereas the people can loan NXTs and other assets to somebody. As far as I can see, it's not a part of the core but a use-case implemented on top of AE and AT.
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 04:36:16 PM
 #35428

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.7.6

http://download.nxtcrypto.org/nxt-client-0.7.6.zip

sha256: c219d6a13c870ea7f454fe1e91efe6c6098bed767156aa8921aad0bebe9fe79a


Change log:

Compact the database at every shutdown. This should help reduce the size
of the nxt_db directory after the first run, check the before and after
disk usage.

Prevent duplicate peer listings in the known peers and blacklisted peers
frames.

Prevent a potential duplicate account key attack, of the type described
here:
https://bitcointalk.org/index.php?topic=397183.msg4569817#msg4569817

Added Voting System, not yet enabled.

Some refactoring of the Block and Transaction classes.

Asset exchange bugfixes from the test network and more API requests.

Improved validation of transactions to prevent wrong blacklisting of
peers, and to better enforce transaction validity.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJTBNkwAAoJEFOhyXc7+e2AziEQAJuy9YMEnIfXjaEipm68EklP
XSMWVWBZt1bUsIMZiY7Gu20xV0OxZU68QBIhfFJqX/ZN+grn78pSdQeuOU/gMYdk
YIqZDh2qr7TAVd+On7cMJZ1a41V8av9Xqk/Uy1ydj3A+ZXb3jO0aNzb/f/VvlbGb
DWvO1s7KBA1yghdFQvy/0zxD7hYWcjm2rWe/3UvSTv+qhQCsPQDbdNTg+uUFwvof
SgnnW6NiOaKWrMDc0YFAFMbCDt7LjeY5+Ek1lW3Z0ZZtIJuTuMHWYRo7MoMj1aXO
zEIUOAYGxRbZLClBEFxtIwwF+Kfi75xYlK9pcchl7Wo0a9ooPG9EjqJy+H7f6bmk
xW3frfdIKPy5lZx0H05YnuU9ttUPr0snbWWuDtZQ9CeMzOSKyX/lYsiiUQdbNlGr
FrF4+uLIUXGhBULPNX7P88Om6FYNFVAbgtYxqZSLVIj+5ppZZJxo5rk1A+i2is3A
DKioarK9d7Vy2yMB+FGf3Se03cVmJsdPuqRylw66+PGj+48Ei1Uvzru7lbl8Rqag
guNN48NBm0xuXfBuakPfC7aa1+W2lllB3piJCW/hScbdHtEDsaBsDcYoDAC4CcBV
zpE60AgLClhAinwM4VEkZ7ntSTk83ImR3Ii5HRG7Ip0bzp/MdPcGZ4ifzI/VUH01
DeQ2cjfsCSNbOD61QK/W
=MadH
-----END PGP SIGNATURE-----


Big thank you for that one.

Waiting for nxtcrypto to update accordingly.
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 04:37:30 PM
 #35429

Technical question:

When a node gets somebody's private key, it starts forging. That's for sure.

What happens if somebody else sends his private key to that very node? Will it start forging for that account, too? Will it stop forging for the first account? And last but not least, how many accounts can a node forge for?

bump for @JL
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 04:38:25 PM
 #35430

@JL

How come that disconnected peers (red flag icon) appear in the list of active peers?
pinarello
Full Member
***
Offline Offline

Activity: 266
Merit: 100


NXT is the future


View Profile
February 19, 2014, 04:42:34 PM
 #35431



Code:
[2014-02-19 17:34:46.143] Genesis block not in database, starting from scratch
[2014-02-19 17:34:46.185] Scanning blockchain...
[2014-02-19 17:34:46.235] DEBUG: block 0
[2014-02-19 17:34:46.235] ...Done
[2014-02-19 17:34:46.241] NRS 0.7.6 started successfully.
[2014-02-19 17:38:05.945] DEBUG: Generate block failed: Previous block id doesn'
t match
[2014-02-19 17:38:06.811] DEBUG: Account 12088507821025750338 generated an incor
rect block.
[2014-02-19 17:38:08.592] DEBUG: Account 12088507821025750338 generated block 18
179236451186264783
[2014-02-19 17:38:49.529] DEBUG: Invalid transaction attachment:
{"message":""}
[2014-02-19 17:39:05.914] DEBUG: Invalid transaction attachment:
{"message":""}
[2014-02-19 17:40:16.537] DEBUG: Invalid transaction attachment:
{"message":""}
[2014-02-19 17:41:01.844] DEBUG: Invalid transaction attachment:
{"message":""}

cryptolawyer
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile
February 19, 2014, 04:46:22 PM
 #35432

For those not following the AT topic that might still be interested:

http://ciyam.org/nxt/

It is still a work in progress but at least you can see that progress is being made (I know that in Nxt land progress is generally measured in days rather than weeks or months).

We have already come up with some interesting ideas beyond the two current use cases such as a "Term Deposit" AT that would earn you NXT by leasing your forging power for x blocks then return the initial balance + forging interest to you and I think James will probably blow everyone's mind with some of his ideas.

The more I look at the flexibility of the Nxt design the more I think it really is the "next" thing. I just hope that TF can be proven to have no attack vector (beyond a 90% stake ownership one).


Fantastic!

I'll reiterate my lawyer's-view request to think about other attributes of ownership that can be separated from an asset and dealt with independently in addition to forging rights. For example: the ability to separate and transfer voting rights in the event a voting system is implemented, the ability to give a third party a blocking right over your disposition of an asset, such that you can't transfer it without the third party's consent, or the ability to permit and control copies of digital assets (i.e. copyright principles).

Much of IP and real property law is taught and practiced by reference to the concept of a "bundle of rights," whereby ownership of an asset is actually an amalgamation of distinct rights in and to the asset, each of which can be separated and used independently in more sophisticated economic and contractual relationships. And the vast majority of pure contractual relationships in modern finance involve contracting parties agreeing to treat non-IP and real property assets similarly (securitizations and other structured finance transactions rely on a bewildering variety of fine-grained divisions of rights and obligations vis-a-vis financial assets).

Enabling even a small subset of these concepts at the protocol level (or in clever AT and/or multi-signature approaches) would likely open a floodgate of innovative reallocation of trust to the blockchain among real-world economic actors.
msin
Legendary
*
Offline Offline

Activity: 1218
Merit: 1001


View Profile
February 19, 2014, 04:47:51 PM
 #35433

Can someone send me links to any secure online Nxt wallets available?  Working with a couple exchanges to add Nxt and want to make it easy for their end users.  Thanks.
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 19, 2014, 04:48:11 PM
 #35434

What happens if somebody else sends his private key to that very node? Will it start forging for that account, too? Will is stop forging for the first account? And last but not least, how many accounts can a node forge for?
There is no limit, it will forge for all those accounts. To prevent overloading the node with random bogus secret phrases, those have to match existing accounts, which have had at least one incoming or outgoing transaction.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
l8orre
Legendary
*
Offline Offline

Activity: 1080
Merit: 1002


View Profile
February 19, 2014, 04:49:22 PM
 #35435

I checked this signature, it says "Signature made Sat 15 Feb 2014 12:30:29 AM CST"
but the post is made before that. did I miss something?
Something is wrong in your time or timezone settings. I checked the signature of the post you quoted again, and it is from Fri 14 Feb, same as my original post. All EU and US timezones were still in Friday at that time, the hour and minute match so it is a timezone issue.




Hello JL -

is there an api call that returns all api calls, or is it possible to access the javadoc @ https://nxt.airdns.org:7875/doc/ to get a list of all api calls? I am a bit panicky on missing out on important things, e.g. as with the vote thingy, which I only just picked up en passant


Thanks for the good work!

##  
        self.FUTURE = """
                            
                            
                            Added: 02172104
                            
                            http://holms.cloudapp.net:6874/nxt?requestType=getPollIds
                            http://holms.cloudapp.net:6874/nxt?requestType=getPoll&poll=9012989318636877714
                            
                            Added back:
                            
                            getTrades
                                    
        
        
#        
#        
#      
#?requestType=createPoll&secretPhrase=123&name=Best+singer&description=Choose+the+best+singer!&option0=Madonna&option1=Elvis+Presley&option2=Justin+Bieber&minNumberOfOptions=1&maxNumberOfOptions=1&optionsAreBinary=true&fee=1&deadline=1440
#
#?requestType=castVote&secretPhrase=123&poll=28765873427562395&vote2=1&fee=1&deadline=1440
#Reply
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 04:49:34 PM
 #35436

For those not following the AT topic that might still be interested:

http://ciyam.org/nxt/

It is still a work in progress but at least you can see that progress is being made (I know that in Nxt land progress is generally measured in days rather than weeks or months).

We have already come up with some interesting ideas beyond the two current use cases such as a "Term Deposit" AT that would earn you NXT by leasing your forging power for x blocks then return the initial balance + forging interest to you and I think James will probably blow everyone's mind with some of his ideas.

The more I look at the flexibility of the Nxt design the more I think it really is the "next" thing. I just hope that TF can be proven to have no attack vector (beyond a 90% stake ownership one).


Fantastic!

I'll reiterate my lawyer's-view request to think about other attributes of ownership that can be separated from an asset and dealt with independently in addition to forging rights. For example: the ability to separate and transfer voting rights in the event a voting system is implemented, the ability to give a third party a blocking right over your disposition of an asset, such that you can't transfer it without the third party's consent, or the ability to permit and control copies of digital assets (i.e. copyright principles).

Much of IP and real property law is taught and practiced by reference to the concept of a "bundle of rights," whereby ownership of an asset is actually an amalgamation of distinct rights in and to the asset, each of which can be separated and used independently in more sophisticated economic and contractual relationships. And the vast majority of pure contractual relationships in modern finance involve contracting parties agreeing to treat non-IP and real property assets similarly (securitizations and other structured finance transactions rely on a bewildering variety of fine-grained divisions of rights and obligations vis-a-vis financial assets).

Enabling even a small subset of these concepts at the protocol level (or in clever AT and/or multi-signature approaches) would likely open a floodgate of innovative reallocation of trust to the blockchain among real-world economic actors.

Great ideas. Smiley

It should not be considered core functionality but it's easily implemented by AE and AT.

I like that and would even contribute as a developer if you are interested.
pinarello
Full Member
***
Offline Offline

Activity: 266
Merit: 100


NXT is the future


View Profile
February 19, 2014, 04:49:58 PM
 #35437

Can someone send me links to any secure online Nxt wallets available?  Working with a couple exchanges to add Nxt and want to make it easy for their end users.  Thanks.

please define secure Grin in online.

maybe: https://wallet.mynxt.info/

ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 04:52:50 PM
 #35438

Can someone send me links to any secure online Nxt wallets available?  Working with a couple exchanges to add Nxt and want to make it easy for their end users.  Thanks.

Don't trust online wallets.

Just implement your own wallet app and make it opensource to let other contribute and audit the code base.
evanxxx
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
February 19, 2014, 04:53:20 PM
 #35439

I checked this signature, it says "Signature made Sat 15 Feb 2014 12:30:29 AM CST"
but the post is made before that. did I miss something?
Something is wrong in your time or timezone settings. I checked the signature of the post you quoted again, and it is from Fri 14 Feb, same as my original post. All EU and US timezones were still in Friday at that time, the hour and minute match so it is a timezone issue.

I just checked the signature of release 0.7.6 and confirmed that it is a timezone issue, thank you.
pinarello
Full Member
***
Offline Offline

Activity: 266
Merit: 100


NXT is the future


View Profile
February 19, 2014, 04:54:06 PM
 #35440

following errors in 7.6, but running


Code:
       at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.643] DEBUG: Invalid transaction attachment:
{"alias":"greenenergymarket","uri":""}
[2014-02-19 17:46:00.643] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 6871
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.646] DEBUG: Invalid transaction attachment:
{"message":"d5664d4c6a788a6c639da093f952c1c87669aecbff05695fa62784251d639ddcc8cd
12a576de592ad929f3e035af881372b9a42e3a6310193fc486d51b408ecbadc79aa5260db0d55ad3
eda0db9acce23a1588881e9c141419e9baba43dde842"}
[2014-02-19 17:46:00.647] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Arbitrary messages not yet enabled at he
ight 6872
        at nxt.Transaction$Type$Messaging$1.validateAttachment(Transaction.java:
755)
        at nxt.Transaction$Type$Messaging$1.loadAttachment(Transaction.java:743)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.650] DEBUG: Invalid transaction attachment:
{"alias":"NRSrelease","uri":"http:\/\/download.nxtcrypto.org\/nxt-client-0.7.6.z
ip"}
[2014-02-19 17:46:00.650] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 6872
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.653] DEBUG: Invalid transaction attachment:
{"alias":"NRSversion","uri":"0.7.6 c219d6a13c870ea7f454fe1e91efe6c6098bed767156a
a8921aad0bebe9fe79a"}
[2014-02-19 17:46:00.653] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 6873
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.216] DEBUG: Invalid transaction attachment:
{"alias":"distributedenergymarket","uri":""}
[2014-02-19 17:46:07.216] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8270
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.219] DEBUG: Invalid transaction attachment:
{"alias":"hkland","uri":""}
[2014-02-19 17:46:07.220] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8271
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.222] DEBUG: Invalid transaction attachment:
{"alias":"nxtgreenenergymarket","uri":""}
[2014-02-19 17:46:07.222] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8271
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.225] DEBUG: Invalid transaction attachment:
{"alias":"NXTCraft","uri":""}
[2014-02-19 17:46:07.226] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8272
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.229] DEBUG: Invalid transaction attachment:
{"alias":"NXTScape","uri":""}
[2014-02-19 17:46:07.230] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8272
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.233] DEBUG: Invalid transaction attachment:
{"alias":"greenenergymarket","uri":""}
[2014-02-19 17:46:07.233] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8273
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.236] DEBUG: Invalid transaction attachment:
{"message":"d5664d4c6a788a6c639da093f952c1c87669aecbff05695fa62784251d639ddcc8cd
12a576de592ad929f3e035af881372b9a42e3a6310193fc486d51b408ecbadc79aa5260db0d55ad3
eda0db9acce23a1588881e9c141419e9baba43dde842"}
[2014-02-19 17:46:07.236] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Arbitrary messages not yet enabled at he
ight 8274
        at nxt.Transaction$Type$Messaging$1.validateAttachment(Transaction.java:
755)
        at nxt.Transaction$Type$Messaging$1.loadAttachment(Transaction.java:743)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.239] DEBUG: Invalid transaction attachment:
{"alias":"NRSrelease","uri":"http:\/\/download.nxtcrypto.org\/nxt-client-0.7.6.z
ip"}
[2014-02-19 17:46:07.239] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8274
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.242] DEBUG: Invalid transaction attachment:
{"alias":"NRSversion","uri":"0.7.6 c219d6a13c870ea7f454fe1e91efe6c6098bed767156a
a8921aad0bebe9fe79a"}
[2014-02-19 17:46:07.242] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8275
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:49:57.457] Checksum passed at block 30000

Pages: « 1 ... 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 [1772] 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 ... 2565 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!