If it weren't for the references in Hebrews 5, 6 & 7, most of us would not give much attention to Melchizedek. We'd just be glad it wasn't our turn to read scripture when his name came up. There are two Old Testament passages that mention the ancient priest-king. Psalm 110 first mentions his perpetual priesthood--whatever that means. Genesis 14 offers a brief interaction between Melchizedek, Abram and the king of Sodom. From this story, chances are, you may come away with more questions than answers about who he was.
We do know what his name meant. Melchizedek means "king of righteousness." In this encounter we get a glimpse of the righteousness he upheld. He blessed Abram and gave God praise for Abram's important victory. Now, what do we know of the king of Sodom? For our reflection today, we only need to recall Sodom's reputation.
Both kings have approached Abram after his defeat of an opposing king. Both have something to offer.
Melchizedek offers a blessing. Sodom's king offers a, seemingly, okay deal. But Abram can already tell it may come with unwanted consequences. Abram doesn't accept the king's offer, but he does give one tenth of everything to Melchizedek. Abram could have left with more riches by taking the king's offer. He chose, however, to offer to God a literal tithe.
Abram's choice reminds me of what Jesus chose in his desert temptation. The choice was between two kingdoms. The enemy's kingdom came with a quick promise--a kind of sweet deal. God's kingdom came through suffering. But Jesus knew choosing God's kingdom was the only way he would be able to give God glory. Abram knew the same thing.
Do we? We all have choices to make in life. Often, we don't always recognize the kingdom consequences of our choices. The ease of better deals can seem appealing--too good to be true.
Abram recognized Melchizedek's service to God. He offered the enigmatic priest something of himself in return. May God give us faith and the righteousness necessary to offer God our best in service to God's kingdom. Stay blessed...john |
No comments:
Post a Comment